Authentication error - InvalidAuthenticationTokenTenant with AddAzureProvisioning

[christiannagel]

Working yesterday, failing today after my travel from the US to Austria, and needing to re-authenticate with Visual Studio to get an updated license, I see this error when deploying running the application with Visual Studio using builder.AddAzureProvisioning():

Provisioning codebreakerconfig...
Error provisioning codebreakerconfig.
Azure.RequestFailedException: The access token is from the wrong issuer 'https://sts.windows.net/55a/';. It must match the tenant 'https://sts.windows.net/...173/'; associated with this subscription. Please use the authority (URL) 'https://login.windows.net/173'; to get the token. Note, if the subscription is transferred to another tenant there is no impact to the services, but information about new tenant could take time to propagate (up to an hour). If you just transferred your subscription and see this error message, please try back later.
Status: 401 (Unauthorized)
ErrorCode: InvalidAuthenticationTokenTenant

The same error happens when using the command line dotnet run.

Re-selected the account with Azure Service authentication, did a login with azd login.

Running azd up to deploy the complete solution is successful.

How can I find out why the wrong issuer is used?

[christiannagel]

I found out it's using DefaultAzureCredential (as expected) excluding Managed Id, workload identity, and PowerShell credentials. I don't know why this was running successfully before because the Visual Studio account I'm using is not the Azure account.
Fixed this by adding the Visual Studio key to Visual Studio to log out of the Visual Studio account - now the correct Azure account has been used.

[christiannagel]

Just had this issue again - loving the option to set the credentials via configuration, e.g.

{
  "Azure": {
    "CredentialSource": "AzureCli"
  }
}

This way it was immediately running.

Using 8.0.0-preview.6.24177.4/8.0.100