You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on documentation, it seems that a desiredState with an excludedScopes like:
"excludedScopes": [
"/subscriptions/*"
]
would allow subscription owners to define and assign their own policies, while still inheriting definitions and assignments from the MG tree in which the subscription resides.
Can someone confirm that's the way it works? And the a wildcard scope like that above would exclude all subscriptions?
Note - I'm not saying this would be a good approach, but my subscription owners seem to want to add policies ad hoc.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Based on documentation, it seems that a desiredState with an excludedScopes like:
"excludedScopes": [
"/subscriptions/*"
]
would allow subscription owners to define and assign their own policies, while still inheriting definitions and assignments from the MG tree in which the subscription resides.
Can someone confirm that's the way it works? And the a wildcard scope like that above would exclude all subscriptions?
Note - I'm not saying this would be a good approach, but my subscription owners seem to want to add policies ad hoc.
Thanks
Beta Was this translation helpful? Give feedback.
All reactions