az login: Invalid profile error for non-AzureStack cloud

[egodigitus]

Describe the bug

Command Name
az login

Errors:

Invalid profile is used for cloud 'AzureCloud'. To configure the cloud profile, run `az cloud set --name AzureCloud --profile <profile>(e.g. 2019-03-01-hybrid)`. For more information about using Azure CLI with Azure Stack, see https://docs.microsoft.com/azure-stack/user/azure-stack-version-profiles-azurecli2

To Reproduce:

Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

• Put any pre-requisite steps here...
• az login --service-principal -u {} -p {} -t {}

Expected Behavior

login as a service-principal works

Environment Summary

Linux-4.4.0-17763-Microsoft-x86_64-with-debian-bullseye-sid
Python 3.6.10
Installer: DEB

azure-cli 2.21.0

Additional Context

The fix from #15550 works:
If I set az cloud set --name AzureCloud --profile 2020-09-01-hybrid the login works as expected.
The response body of both (the failed and the successful one) calls contain "managedByTenants":[],

I do not connect to an Azure Stack instance

[jiasli]

This is caused by an ongoing ARM service incident. Please see #17509.

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc armleads-azure.

Issue Details

---

Describe the bug

Command Name
az login

Errors:

Invalid profile is used for cloud 'AzureCloud'. To configure the cloud profile, run `az cloud set --name AzureCloud --profile <profile>(e.g. 2019-03-01-hybrid)`. For more information about using Azure CLI with Azure Stack, see https://docs.microsoft.com/azure-stack/user/azure-stack-version-profiles-azurecli2

To Reproduce:

Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

• Put any pre-requisite steps here...
• az login --service-principal -u {} -p {} -t {}

Expected Behavior

login as a service-principal works

Environment Summary

Linux-4.4.0-17763-Microsoft-x86_64-with-debian-bullseye-sid
Python 3.6.10
Installer: DEB

azure-cli 2.21.0

Additional Context

The fix from #15550 works:
If I set az cloud set --name AzureCloud --profile 2020-09-01-hybrid the login works as expected.
The response body of both (the failed and the successful one) calls contain "managedByTenants":[],

I do not connect to an Azure Stack instance

Author:	egodigitus
Assignees:	-
Labels:	ARM, Service Attention
Milestone:	-

[egodigitus]

Thanks for the quick response.
A workaround without the patch #17509 is to use the hybrid profile:
az cloud set --name AzureCloud --profile 2020-09-01-hybrid
az login

[jiasli]

egodigitus, setting --profile 2020-09-01-hybrid will cause other failures (like for az aks) because 2020-09-01-hybrid has a reduced command set compared to latest.

[Forcebyte]

shouldn't there be an incident communication from Microsoft in situations like this?

Not trying to be needy or anything; but it appears to be affecting three orgs I communicate with regularly

[J0F3]

Jiashuo Li (@jiasli) I wondering the same as Patrick (@Forcebyte). Why is there no official communication in the service health dashboard or somewhere that there is a problem with the ARM service. So that it is clear that we not to have to search on our side which the "az login" suddenly does not work anymore resp. that we, customers, can actually not do much to fix it.

[zyadamec]

I humbly request this be more than an "Advisory" In Azure Dev Ops, and no status in azure as a whole. This is not a simple inconvenience