Microsoft Azure PowerShell

arm azure microsoft microsoft-azure-powershell powershell
3 Open Issues Need Help Last updated: Jan 8, 2026

Open Issues Need Help

View All on GitHub

AI Summary: The `Connect-AzAccount` cmdlet does not correctly update the `Environment.Name` property in the current PowerShell context when switching between different Azure environments. While the `ResourceManagerUrl` updates as expected, the environment name displayed in the context remains that of the previously connected environment, leading to a misleading state. This issue occurs when switching from a custom environment to a standard one, and vice-versa.

Complexity: 2/5
Azure PS Team bug customer-reported good first issue Tracking

Microsoft Azure PowerShell

C#
#arm#azure#microsoft#microsoft-azure-powershell#powershell
Azure PS Team bug good first issue Tracking Similar-Issue

Microsoft Azure PowerShell

C#
#arm#azure#microsoft#microsoft-azure-powershell#powershell

AI Summary: The task is to debug and fix a bug in the Azure PowerShell `Get-AzAccessToken` cmdlet. The bug causes the cmdlet to fail when retrieving an access token for the resource 'https://management.azure.com/' after using the `Connect-AzAccount -AccessToken` method, while succeeding with other authentication methods or for the resource 'https://management.core.windows.net/'. The solution likely involves investigating the `AccessTokenAuthenticator` within the `Az.Accounts` module and ensuring it correctly handles access tokens obtained via the specified method.

Complexity: 4/5
Azure PS Team feature-request good first issue Accounts Similar-Issue

Microsoft Azure PowerShell

C#
#arm#azure#microsoft#microsoft-azure-powershell#powershell