The doc's say
An array of strings that specifies the scopes that the custom role is available for assignment. Currently cannot be set to the root scope ("/") or a management group scope. For more information, see AssignableScopes and Organize your resources with Azure management groups.
However on the Assignable Scopes page this shows
Role is available for assignment in all scopes "/"
So which one is correct?
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@kilasuit Thanks for reporting this. We are looking into this and will get back to you shortly.
@rolyon can you explain this? Is it only assignable to the root for built-in scopes, or is there another sort of discrepancy going on?
Hi @kilasuit
Built-in roles have AssignableScopes set to the root scope ("/"). However, if you are creating your own custom role, you can't set AssignableScopes to the root scope ("/"). You must set to one or more subscriptions or resource groups.
thanks
We will now proceed to close this thread. If you have further questions feel free to tag us in the comments and we will gladly continue the discussion.
Most helpful comment
Hi @kilasuit
Built-in roles have AssignableScopes set to the root scope ("/"). However, if you are creating your own custom role, you can't set AssignableScopes to the root scope ("/"). You must set to one or more subscriptions or resource groups.
thanks