Question 210
A management group named mg-legacy still contains subscription sub-lab and child management group mg-archive. Governance has approved retiring mg-legacy; both child scopes must remain managed under mg-current without deleting their subscriptions or resources. An attempted deletion of mg-legacy is blocked. What is the required sequence?
Explanation
Correct Answer
Azure cannot delete a management group while child subscriptions or management groups remain. Authorized administrators must move those child scopes to their approved parents, account for inherited governance and hierarchy permissions, verify the target group is empty, and only then delete mg-legacy. This preserves the child resources and tests deletion prerequisites, not initiative assignment.
Incorrect Answers
Deleting a management group with children is blocked; the platform does not silently delete subscriptions or relocate their VMs as a consequence of a management-group delete. Moving the children first is required.
Removing policy assignments changes governance, not the hierarchy. The remaining child management group and subscription still prevent deleting mg-legacy even if its policies have all been unassigned.
The display name is not the same as management-group identity or child membership. Renaming does not move sub-lab or mg-archive or meet the empty-group precondition for deletion.