AzurePowerShellCredential fails to generate token due to deprecation message in Az 12.1.0

[jalkire]

• Package Name: @azure/identity
• Package Version: 4.3.0
• Operating system: Windows
• nodejs
  • version: 18.20.4

Describe the bug
Az PowerShell 12.1.0 introduced a deprecation warning about an output change of Get-AzAccessToken to securestring. This message causes the Get-AzAccessToken command in azurePowerShellCredential to fail.

To Reproduce
Steps to reproduce the behavior:

1. Ensure that you have installed Az 12.1.0
2. Attempt to use AzurePowerShellCredential to get a token. Minimal repro example:

const { AzurePowerShellCredential } = require('@azure/identity');

async function getToken() {
    const credential = new AzurePowerShellCredential();
    const scope = 'https://management.azure.com/.default';
    try {
        const accessToken = await credential.getToken(scope);
        console.log('Successfully retrieved token');
    } catch (error) {
        console.error('Error getting access token:', error);
    }
}

getToken();

3. Receive error:

Error getting access token: CredentialUnavailableError: Error: Unable to parse the output of PowerShell. Received output: WARNING: Upcoming breaking changes in the cmdlet 'Get-AzAccessToken' :
The Token property of the output type will be changed from String to SecureString. Add the [-AsSecureString] switch to avoid the impact of this upcoming breaking change.

• The change is expected to take effect in Az version : '13.0.0'
• The change is expected to take effect in Az.Accounts version : '4.0.0'
  Note : Go to https://aka.ms/azps-changewarnings for steps to suppress this breaking change warning, and other information on breaking changes in Azure PowerShell.

Expected behavior
No error. Token acquired successfully.

Additional context
A workaround is to disable the deprecation warning, but @azure/identity will still need to be updated to expect a SecureString before Az 13.0.0 is released.

[github-actions]

@KarishmaGhiya @maorleger

[github-actions]

Thank you for your feedback. Tagging and routing to the team member best able to assist.

[xirzec]

Thank you for the detailed report @jalkire

[KarishmaGhiya]

Currently going the check if other languages too are affected by this. And going to come up with the plan.