This repository has been archived by the owner on Oct 12, 2023. It is now read-only.
ARM mode with publishsettings fails with non-friendly message #1614
Labels
Comments
@ahmetalpbalkan Will look at improving the error message, or perhaps making the certificate cmdlets unabailable in ARM mode. You need to have an OrgID account to authenticate - this is an AAD restriction. Tis blog post has details on how to create an org id account for your subscription if you're currently using AAD credentials: |
@markcowl sounds perfect, can we have this URL in the error message? I already know the solution. @squillace @johngossman |
@ahmetalpbalkan, @johngossman |
@ahmetalpbalkan - The corresponding PR to improve the error message is here |
|
Fixed. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I set
azure config mode arm
and I runazure account --help
and it shows that I can actually use .publishsettings file and I usedazure account download
then I usedazure account import
then I set the active subscription correctly.However when I run a command in authenticated mode. It fails in an ugly way with the following error message:
I can't use a corporate account (because the account isn't) and I'm clueless about how can I possibly authenticate. As a user, please tell me I'm using a wrong method to authenticate; not the Authorization header is invalid.
I know this stuff is still in preview but I just wanted to make sure you guys are aware of the situation. @guangyang
The text was updated successfully, but these errors were encountered: