Fix issue with context name clashing for accounts with no subscriptions in a tenant #7665
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.
Description
Fix for #7453
Contexts that were created for an account with no subscriptions in a tenant would be given a
Defaultname since they had no subscription to create the name from, and thisDefaultname would clash with the existingDefaultcontext with no properties that is created initially, so the new context would be thrown out and the empty context would be returned.The fix in the common code will create a name in the format
{{TENANT_ID}} - {{ACCOUNT_ID}}in this scenario, which will avoid the clashingDefaultnames of the contexts.Checklist
CONTRIBUTING.mdplatyPSmodule