Azure Agent Unable to Find Access Token For Azure PowerShell

[bmkaiser]

Prerequisites

• Write a descriptive title.
• Make sure you are able to repro it on the latest version
• Search the existing issues.

Steps to reproduce

When using the Azure agent, it is unable to find my access token when using Connect-AzAccount. However, when I use az login with the Azure CLI, it works. I tested with both version 4.0.2 and 5.1.0 of the Az.Accounts module.

Expected behavior

I should be able to use either Connect-AzAccount or az login for creating and caching an access token.

Actual behavior

I am only able to successfully connect to the Azure agent after running az login.

Error details

ERROR: Failed to start a chat session: Access token not available.
ERROR: The 'azure' agent depends on the Azure CLI credential or Azure PowerShell credential to acquire access token. Please run 'az login' or 'Connect-AzAccount' from a command-line shell to setup account. Once you've successfully logged in, run '/refresh' to start a new conversation.

Environment data

Name                           Value
----                           -----
PSVersion                      7.5.2
PSEdition                      Core
GitCommitId                    7.5.2
OS                             Microsoft Windows 10.0.26100
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Version

1.0.0-preview.5

Visuals

[daxian-dbw]

This is weird. I cannot reproduce this issue on Windows with v1.0.0-preview.6 (no changes to the Azure agent in the preview.6 release).

I'm using Az.Accounts 4.0.2 and I didn't log in for az. The access token was retrieved from Azure PowerShell as expected.

---

[UPDATE]
I'm able to reproduce the issue on macOS.

The actually error from AzurePowerShellCredential() is "PowerShell did not return a valid response.", with the following strack trace:

  at Azure.Identity.AzurePowerShellCredential.ValidateResult(String output)
  at Azure.Identity.AzurePowerShellCredential.RequestAzurePowerShellAccessTokenAsync(Boolean async, TokenRequestContext context, CancellationToken cancellationToken)
  at Azure.Identity.AzurePowerShellCredential.GetTokenImplAsync(Boolean async, TokenRequestContext requestContext, CancellationToken cancellationToken)
  at Azure.Identity.CredentialDiagnosticScope.FailWrapAndThrow(Exception ex, String additionalMessage, Boolean isCredentialUnavailable)
  at Azure.Identity.AzurePowerShellCredential.GetTokenImplAsync(Boolean async, TokenRequestContext requestContext, CancellationToken cancellationToken)
  at Azure.Identity.AzurePowerShellCredential.GetTokenAsync(TokenRequestContext requestContext, CancellationToken cancellationToken)
  at Azure.Identity.ChainedTokenCredential.GetTokenImplAsync(Boolean async, TokenRequestContext requestContext, CancellationToken cancellationToken)

This turns out to be an issue with Azure.Identity library (Azure/azure-sdk-for-net#50578). After moving to the latest 1.14.2 of the package, it works for me on macOS.

I will create a PR to update the package version. Thank you @bmkaiser for reporting this error!

[bmkaiser]

Thanks @daxian-dbw! I'm experiencing the issue on Windows 11 24H2 using Az.Accounts version 5.1.0. However, your fix might still resolve the issue for me. I'll test again with the next release and use az login in the meantime as a workaround.

[daxian-dbw]

@bmkaiser I got confirmation from the Azure PowerShell team that it's due to a breaking change in Azure PowerShell and upgrading to Azure.Identity v1.14.2 will resolve the issue. Thank you for reporting this issue!