When you buy an Azure Savings Plan, scope is the first configuration decision you make and getting it wrong locks a commitment into a narrow subscription that never fully fills while the rest of your billing account runs at pay-as-you-go rates.
There are four options: Resource Group, Subscription, Management Group, and Shared. Azure recommends Shared as the default and for multi-subscription organizations, that recommendation is correct. But understanding why, and when the other three make sense, determines whether your commitment saves money or creates waste.
This article covers how each scope works, the order Azure uses when applying multiple savings plans, the utilization risks of narrower scopes, and how to change scope after purchase without triggering a new commercial transaction.
The Four Scopes and What They Actually Cover
Resource Group is the most restrictive option. Benefits apply only to eligible resources inside a single, named resource group within one subscription. Right-sizing a commitment to one resource group is precise but fragile, if workloads move out of that group, the discount stops applying.
Subscription scope restricts benefits to all eligible resources across all resource groups within one Azure subscription. No spill-over to other subscriptions, even if they're under the same EA Enrollment or MCA Billing Profile.
Management Group scope covers eligible resources from subscriptions that are in both the specified management group and the billing account. It sits between subscription and shared, useful for business unit segmentation without pooling across the entire billing account. The significant catch: Azure Advisor does not provide native recommendations for management group scope, which means sizing this commitment requires manual aggregation of per-subscription recommendations from the Azure portal.
Shared scope applies benefits to all eligible resources across every subscription in the EA Enrollment or MCA Billing Profile, including all Microsoft Entra tenants in that enrollment. Azure describes this as the correct default for most multi-subscription organizations, and the mechanics back that up: the discount is applied wherever eligible usage exists in the billing account, automatically, every hour.
How Azure Applies Benefits When You Have Multiple Plans
If you have more than one savings plan active simultaneously or if your team has layered plans with different scopes, Azure applies them in a specific order from narrowest to broadest:
- Resource Group scope plans apply first
- Subscription scope plans
- Management Group scope plans
- Shared scope plans apply last
Within the same scope level, Azure applies three-year plans before one-year plans (to prioritize the deepest discount rates). Within the same scope and term, it applies the plan that delivers the greatest savings to eligible resources first, not first-in, first-out.
The practical implication for hybrid environments: if you have a subscription-scoped plan and a shared-scoped plan, the subscription-scoped plan covers eligible usage in that subscription first. The shared plan then covers remaining eligible usage across the rest of the billing account. Narrower scopes aren't wasteful on their own, they become wasteful when the eligible usage in the narrow scope can't fill the commitment hourly.
Explore Azure Database Savings Plans and reduce long-term database infrastructure costs → Read here
Why Shared Scope Is the Right Default for Most Organizations
Shared scope pools coverage across the entire billing account. Every hour, Azure scans all eligible compute usage across all subscriptions and applies your commitment to the combination of resources that maximizes total discount delivered. If a workload migrates from Subscription A to Subscription B next month, the shared plan continues covering it without any manual intervention.
For multi-subscription organizations, a shared-scoped plan is significantly more efficient than a set of subscription-scoped plans at the same total commitment because it pools eligible usage automatically. No coverage gets stranded in one subscription while another subscription generates eligible usage that goes undiscounted.
The hourly use-it-or-lose-it mechanic amplifies this: Azure savings plan benefits don't carry forward between hours. A shared plan covering many subscriptions is far more likely to fill the commitment every hour than a subscription-scoped plan for a subscription that may idle overnight.
Subscription Scope: When It's the Right Choice
Subscription scope makes sense in three specific situations: chargeback accountability (the FinOps model requires discount to be directly attributable to one subscription's budget, eliminating shared-plan allocation complexity), single-subscription organizations (where shared and subscription scope produce identical results), and controlled rollout (validating utilization on a narrow commitment before buying a shared plan).
The utilization risk is highest for subscriptions with variable workloads, dev/test environments, project-based subscriptions, seasonal demand patterns. For these, subscription scope is the worst fit. Hours where eligible usage in the subscription falls below the commitment are wasted; the benefit cannot spill to another subscription.
If you're managing Azure commitment strategy across multiple subscriptions and want to maintain shared scope without losing chargeback visibility, Azure Database Savings Plans scope behavior follows the same four-scope model understanding it alongside compute scope decisions gives a more complete picture of your billing account's commitment coverage.
Management Group Scope: Business Unit Segmentation
Management group scope covers eligible resources from subscriptions within a specified management group, without pooling across the entire billing account. It's the right fit for organizations that have structured Azure into management group hierarchies by business unit or product line and need benefit isolation without per-subscription utilization risk.
The key limitation: Azure Advisor has no native recommendations for management group scope. To size the commitment, aggregate per-subscription hourly commitment recommendations from the Azure portal for every subscription in the group. If all subscriptions are removed from a management group, Azure automatically rescopes the plan to Shared to prevent it from becoming stranded.
Resource Group Scope: Tightest Isolation
Resource group scope applies only to eligible resources inside a single named resource group. It's appropriate when a team needs a savings plan discount attributed directly to one resource group's cost center. Right-sizing is precise but fragile, if workloads move out of that group, the discount stops applying. Azure Advisor does not surface resource group-level recommendations; the Azure portal's purchase experience does.
Changing Scope After Purchase
You can change scope at any time after purchase. Rescoping does not restart the term, does not trigger a new commercial transaction, and does not change the hourly commitment or pricing.
To rescope: Azure portal → Cost Management + Billing → Savings Plans → select the plan → Settings → Configuration → change scope.
Billing administrators can rescope without restriction. Non-billing-admin users changing from shared to subscription scope can only select subscriptions where they are the subscription owner.
The practical starting strategy: begin with Shared scope to ensure maximum utilization from day one. If chargeback reporting requires subscription-level attribution later, Azure Cost Management's cost allocation features let you distribute the shared plan's discount to individual subscriptions for reporting purposes without changing the scope itself.
The Recommendation Gap for Management Group Scope
Azure provides savings plan recommendations through Azure Advisor (subscription scope only, 30-day look-back) and the Azure portal (shared, subscription, resource group not management group). The Savings Plan Benefit Recommendations API also omits management group scope.
One timing note: if you purchase a shared-scoped plan, Azure Advisor's subscription-level recommendations can take up to 25 days to adjust downward. Don't repurchase subscription-scoped plans based on stale Advisor recommendations immediately after buying a shared plan.
Key Takeaways
- Shared is the correct default for multi-subscription organizations on one EA or MCA. It pools coverage automatically and maximizes hourly utilization.
- Subscription scope is valid for chargeback isolation, single-subscription orgs, or phased rollout not for subscriptions with variable or seasonal demand.
- Management Group scope provides business-unit segmentation without full pooling, but requires manual commitment sizing since Azure Advisor has no native recommendations for it.
- Resource Group scope is appropriate only when a team needs a savings plan discount isolated to one group's cost center. Fragile if workloads move.
- Scope changes after purchase have no commercial impact, start broad and narrow only if chargeback requirements make it necessary.
FULL BREAKDOWN - Azure Savings Plan Scope: Subscription vs Shared vs Management Group vs Resource Group
What's your current scope setup and has chargeback reporting ever been the reason you chose subscription scope over shared? Worth comparing notes if you've worked through this decision at scale.
Top comments (0)