Clarify AzureCLICredential invalid Subscription error #23976
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
chlowell
requested review from
jhendrixMSFT,
RickWinter and
a team
as code owners
chlowell
requested review from
maorleger,
christothes,
pvaneck,
billwert,
ahsonkhan,
KarishmaGhiya and
minhanh-phan
jhendrixMSFT
approved these changes
Jan 17, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The set of characters we allow for a subscription name is drawn from general Azure guidelines because subscription name requirements aren't well documented. We disallow some characters that are valid in a subscription name, such as
(). Rather than allow valid characters that may be unsafe to interpolate into a command line, this PR clarifies the error message and recommends customers work around a validation error by using the subscription's ID (a UUID) instead of its name.