Tenant switching

[07JP27]

Hi team,

I have joined multiple tenants. When I try to run a prompty file in VS Code, the default tenant is selected automatically.
However, the Azure OpenAI model I am trying to use is deployed in another tenant, so I cannot authenticate with AAD.

Is there any way to switch tenants when running a prompt or a workaround for this issue?

[sethjuarez]

Great question - the extension relies on the underlying system settings when it comes to identity. My go to approach is to use the az login approach to sign in to the right places. Let me know what you think.

[07JP27]

I also confirmed that vscode.authentication.getSession() is used in the prompty extension's code.

Creating and using the CLI is a good idea to realize this issue, and it allows execution in other IDEs or shells.
If you still keep the VS Code extension, you can emit the CLI command behind the GUI action.

The CLI command I hope:

prompty login --tenant xxxxxxxxxxxxxx (-> Browser poping up)
prompty create --file xxxxx.prompty
prompty run --file xxxxx.prompty
prompty generate --lang-chain --file xxxxx.prompty
prompty generate --semantic-kernel --file xxxxx.prompty
prompty generate --prompt-flow --file xxxxx.prompty

[sethjuarez]

Interesting idea!! I will label this as a feature request.

[pelikhan]

vscode 1.93 added support for choosing accounts when getting a session

[DavidBurela]

I am stuck at this point now. I did my auth login for prompty, but it is not using my correct tenant.
I've tried authenticating with az login but Prompty still tries to run against the wrong tenant.

[sethjuarez]

Ugh - I am sorry! In general the AOAI prompty executor uses the currently logged in tenant if the key is not specified. Usually something like:

az login

sould fix the issue. You can also switch the tenant using:

az login --tenant <tenant_id>

Hopefully this works.