Cascade Regional Airlines has grown to operate four Azure subscriptions, one per region, and wants a single template deployment to assign the same tagging policy to all four at once rather than repeating the assignment in each subscription individually. Which deployment scope is built for applying a template's effect across multiple subscriptions in one operation?
Select an answer to reveal the explanation.
Short Explanation
Whenever the goal is "apply this to every subscription under here at once," management group scope is the tool built for that. Group the four regional subscriptions under one management group, and the assignment flows down to all of them from a single deployment.
Full Explanation
A management group deployment targets a management group that contains one or more subscriptions, and resources or policy assignments declared at that scope apply down to every subscription beneath it. This is precisely the tool for a tagging policy that needs to reach all four regional subscriptions from one deployment, rather than being assigned separately per subscription. Repeating a resource-group-scope deployment across each subscription would achieve a similar end result but requires four separate deployments and loses the single point of management a group-level assignment provides. Running a single subscription-scope deployment against only the primary subscription would apply the policy there and nowhere else; subscription scope has no mechanism to reach across into sibling subscriptions. Tenant scope is reserved for deployments that must act at the very root of the directory and is broader and rarer than what this scenario calls for; a management group already solves the multi-subscription requirement without needing tenant-wide reach. After the deployment, a reasonable check is confirming the policy assignment appears at the management group level and shows as inherited on each of the four subscriptions.