Question 180
An operations manager asks to move a resource group itself, with all its contents, into a different Azure subscription as a single resource. What is the supported Azure Resource Manager approach?
Explanation
Correct Answer
Azure Resource Manager does not support moving a resource-group container itself into another subscription as an atomic object. Instead, an administrator can move supported resources from the original group into an existing or newly created target group in the destination subscription, subject to same-tenant, service, identity, lock, and dependency constraints. Resource IDs change where the subscription or group segment changes, and source group settings such as tags and RBAC assignments are not simply carried over. Plan and verify those details before executing the move.
Incorrect Answers
Resource-group containers do not have a universal cross-subscription move operation equivalent to moving eligible resources. The contents must be validated and moved to a destination group through the supported resource move workflow. Ignoring move restrictions and dependencies risks failures and broken references after the attempted management change.
Azure RBAC Reader changes management visibility but does not move resources or resource groups. Cross-subscription changes require explicit resource-move operations and checks, not simply assigning a role. Create the target group, verify tenant and provider support, and move the eligible contained resources through the supported workflow.
Changing a group name cannot relocate it between subscriptions, and Azure resource groups cannot be directly renamed. The subscription is part of the hierarchical resource identifier. To change ownership of supported resources, select a target group in the destination subscription and perform a validated resource move.