Azure Management Groups
Azure Management Groups provide a way to efficiently manage access, policies, and compliance across an enterprise through a hierarchy made up of management groups and subscriptions. Using the Azure portal, PowerShell, CLI, or the Rest API, customers are able to build a flexible structure for unified policy and access management.
Please take a few minutes to submit your idea or vote up an idea submitted by another Azure Management Group customer. All of the feedback you share in these forums are directly monitored and reviewed by the Azure Management Group engineering team.
-
Add subscription request resource group
When adding a new subscription to a directory that has resource groups enabled the new subscription wizard should ask if you want to add the subscription to an existing resource group or create a new one.
Would even be nice if as an admin you can toggle an option in teh directory to require subscriptions be added to a management group.
This just simplifys the management as currently we have to tell everyone to "remember" to do this and stuck cleaning up a mess when it is not done.
9 votesThanks Brett for the feedback. We are looking into building features that do both of those items. 1) Have the management group selection at subscription creation, 2) Custom rules that allow admins to control where subscriptions default when they are created.
-
In Management Groups - Allow to view which sub belongs to a mg
In Management Groups
- Adding a subscription to a management group.Replace dropdown with a view so you can select multiple subscriptions and also see to which MG a subscription belongs.
Also filter by MG group there and also view all subscriptions that does not belong to a MG currently.
6 votesWe are working closely with the UI design team to develop a better hierarchy selection tool. This will be a standard view that can be used across the portal. I don’t have a timeline yet that I can share.
-
Auto-Generate GUIDs for MGs
If GUIDs for MGs could be auto-generated optional this would be a great user experience as currently having to provide your own GUID isn't the best experience.
2 votes -
New-AzManagementGroupSubscription should not move a sub that already is in a ManagementGroup
Description
New-AzManagementGroupSubscription should not move a sub that already is in a ManagementGroupSteps to reproduce
New-AzManagementGroupSubscription -SubscriptionId 12345-x-x-x -GroupName MyNewMG
If sub 12345-x-x-x already exists under an MG, this should throw an error. This command makes it way to easy to break established hierarchy.Possibly there could be a parameter -FORCE that utilized current behavior.
1 vote
- Don't see your idea?