An organization named Meridian Vanguard configures the following Azure Management Group (MG) hierarchy:
* Tenant Root Group
* Corporate-MG
* Production-MG
* App-Sub-01 (Subscription)
* Development-MG
* Dev-Sub-01 (Subscription)
An administrator named Alice needs to reorganize the environment by moving the subscription App-Sub-01 from Production-MG to Development-MG.
Alice has the following Azure role assignments:
* Owner role on the App-Sub-01 subscription
* Reader role on both Corporate-MG and Production-MG
* Contributor role on Development-MG
What is the outcome when Alice attempts to move the subscription?
- AThe move succeeds because Alice is an Owner on the App-Sub-01 subscription, which grants full control over its parent association.
- BThe move fails because Alice lacks the required write permissions on the target management group (Development-MG).
- The move fails because Alice lacks the required write permissions on the source management group (Production-MG).Answer
- DThe move fails because changing a subscription's parent management group requires the User Access Administrator role at the Tenant Root Group level.
Answer
The move fails because Alice lacks the required write permissions on the source management group (Production-MG).
To move an Azure subscription to a new parent management group, an administrator must have write permissions at three distinct scopes: the subscription itself, the target management group, and the source management group. While Alice has Owner permissions on the subscription and Contributor permissions on the target (Development-MG), she only has Reader permissions on the source (Production-MG). Because the Reader role does not grant write permissions (specifically Microsoft.Management/managementGroups/subscriptions/write), the operation is blocked.
Step-by-Step Solution
Key Concept
Moving subscriptions between management groups requires write permissions at the source management group, the target management group, and on the subscription itself.
Estimated Time:2m 0s