AWS
Microsoft Azure
Google Cloud
Key takeaways
1
Azure supports shared, management group, subscription, and resource group scopes.
2
Shared scope gives the commitment the broadest pool of eligible usage.
3
Narrower scopes improve ownership control but can reduce utilization flexibility.
4
You can change scope later, subject to billing structure and permissions.
Most teams pick a Savings Plan scope once, at purchase, and never touch it again even as subscriptions merge, workloads migrate, and usage patterns shift underneath the commitment. The scope you choose decides which resources can actually use the discount you’re paying for, so getting it wrong quietly erodes utilization for months.
Here’s how the four scopes differ, and how to pick one that won’t fight your architecture six months from now.
Choose management group scope when a set of related subscriptions should share the benefit without extending coverage to the entire billing account.
Choose subscription scope when one subscription needs clear financial ownership and has stable eligible usage.
Choose resource group scope when you need the tightest project-level isolation.
As a practical starting point, evaluate the broadest scope that still works with your governance and chargeback model.
Here’s how the four scopes differ, and how to pick one that won’t fight your architecture six months from now.
The short answer
Choose shared scope when several subscriptions under the same eligible billing scope should collectively use the commitment.Choose management group scope when a set of related subscriptions should share the benefit without extending coverage to the entire billing account.
Choose subscription scope when one subscription needs clear financial ownership and has stable eligible usage.
Choose resource group scope when you need the tightest project-level isolation.
As a practical starting point, evaluate the broadest scope that still works with your governance and chargeback model.
Azure Savings Plan scopes compared
Microsoft currently defines four Azure Savings Plan benefit scopes.| Scope | What can use the benefit | Best fit | Main trade-off |
|---|---|---|---|
| Shared | Eligible subscriptions in an EA Enrollment or MCA Billing Profile | Multi-subscription environments | More allocation work |
| Management group | Eligible subscriptions in the selected management group and billing scope | Business units with several subscriptions | More governance complexity |
| Subscription | One subscription | Clear subscription ownership | Smaller eligible usage pool |
| Resource group | One resource group | Application or project isolation | Greatest utilization sensitivity |
1. Shared scope
Shared scope gives your Savings Plan the broadest eligible usage pool.For an Enterprise Agreement, the benefit can apply across eligible subscriptions in the Enrollment. For a Microsoft Customer Agreement, it can apply across subscriptions in the Billing Profile.
Microsoft also notes that shared benefits can apply across Microsoft Entra tenants within that billing scope.
This is useful when usage moves between subscriptions.
For the underlying commitment model, read our Azure Savings Plans guide.
Practical example
Suppose four subscriptions regularly generate:Production: $25/hour
Data: $18/hour
Internal tools: $9/hour
Development: variable usage
If the combined stable eligible usage comfortably exceeds $40/hour, a shared $40/hour commitment has several subscriptions available to consume it.
If Production usage falls while Data usage grows, the commitment can still find eligible usage elsewhere within scope.
If Production usage falls while Data usage grows, the commitment can still find eligible usage elsewhere within scope.
Practical callout:
A broader scope gives more workloads a chance to consume the commitment. It does not make an oversized commitment safe.
2. Subscription scope
Subscription scope limits the Savings Plan benefit to eligible usage in one subscription.It can work well when:
one business unit owns the subscription
budgets are managed separately
direct chargeback matters
usage is predictable
workloads are unlikely to move
The trade-off is a smaller usage pool.
If a subscription has a $20/hour commitment but generates only $14/hour of eligible usage during an hour, usage from another subscription cannot consume the unused $6.
A simple planning metric is:
If a subscription has a $20/hour commitment but generates only $14/hour of eligible usage during an hour, usage from another subscription cannot consume the unused $6.
A simple planning metric is:
Scope utilization = Commitment consumed ÷ Commitment purchased × 100
This is a planning heuristic, not a Microsoft purchasing formula.
The benefit applies to eligible resources in subscriptions that belong to both the selected management group and the applicable Enrollment or Billing Profile.
This can be useful when an enterprise groups subscriptions by:
3. Management group scope
Management group scope sits between shared and subscription scope.The benefit applies to eligible resources in subscriptions that belong to both the selected management group and the applicable Enrollment or Billing Profile.
This can be useful when an enterprise groups subscriptions by:
business unit
product line
geography
engineering organization
For example, five Engineering subscriptions could share one Savings Plan without allowing Finance or Marketing subscriptions to use it. If all subscriptions are moved out of the selected management group, Azure automatically changes the Savings Plan scope to shared.
Microsoft’s current Savings Plan purchase recommendation guidance explains how recommendations are surfaced across different scopes.
Only eligible resources inside the selected resource group can consume the benefit.
This can make sense when a single application or project requires strict cost isolation.
However, it is more sensitive to infrastructure changes. If the workload moves to another resource group, the original scope may no longer match where the usage occurs.
Use this scope when project-level ownership is more important than maximizing the available usage pool.
For database-specific commitments, read our Azure Database Savings Plans guide.
The available options also depend on your billing agreement, billing boundary, and permissions. Microsoft supports Savings Plan management across eligible Enterprise Agreement, Microsoft Customer Agreement, and Microsoft Partner Agreement scenarios.
A management group scope must also overlap with the applicable Enrollment or Billing Profile.
Permissions matter when changing scope. A billing administrator can fully manage Savings Plans, while a nonbilling administrator changing from shared to single scope can select only a subscription they own within the same billing account or profile as the Savings Plan.
Review Microsoft’s Savings Plan management guidance before assuming every scope will be selectable.
Microsoft’s current Savings Plan purchase recommendation guidance explains how recommendations are surfaced across different scopes.
4. Resource group scope
Resource group scope gives you the smallest eligible usage pool.Only eligible resources inside the selected resource group can consume the benefit.
This can make sense when a single application or project requires strict cost isolation.
However, it is more sensitive to infrastructure changes. If the workload moves to another resource group, the original scope may no longer match where the usage occurs.
Use this scope when project-level ownership is more important than maximizing the available usage pool.
For database-specific commitments, read our Azure Database Savings Plans guide.
Scope eligibility and permissions
Scope selection depends on more than your Azure resource hierarchy.The available options also depend on your billing agreement, billing boundary, and permissions. Microsoft supports Savings Plan management across eligible Enterprise Agreement, Microsoft Customer Agreement, and Microsoft Partner Agreement scenarios.
A management group scope must also overlap with the applicable Enrollment or Billing Profile.
Permissions matter when changing scope. A billing administrator can fully manage Savings Plans, while a nonbilling administrator changing from shared to single scope can select only a subscription they own within the same billing account or profile as the Savings Plan.
Review Microsoft’s Savings Plan management guidance before assuming every scope will be selectable.
How Azure applies multiple Savings Plans
When multiple Savings Plans could cover the same usage, Azure processes scopes from narrowest to broadest:
1
Resource group
2
Subscription
3
Management group
4
Shared
Microsoft documents this order in its Savings Plan scope guidance.
Savings Plan commitments also work hour by hour.
Eligible usage consumes the commitment during that hour. Once the commitment is exhausted, additional eligible usage is billed at applicable pay-as-you-go rates.
Azure also uses a sliding 48-hour benefit allocation window. Usage that arrives late can cause recent charges and utilization figures to change while Azure continues applying the benefit.
Microsoft explains this behavior in its Savings Plan discount application documentation.
Look at hourly eligible usage and identify the portion that remains stable over time.
Savings Plan commitments also work hour by hour.
Eligible usage consumes the commitment during that hour. Once the commitment is exhausted, additional eligible usage is billed at applicable pay-as-you-go rates.
Azure also uses a sliding 48-hour benefit allocation window. Usage that arrives late can cause recent charges and utilization figures to change while Azure continues applying the benefit.
Microsoft explains this behavior in its Savings Plan discount application documentation.
How to choose the right scope
Step 1: Map your billing structure
Identify the Enrollment or Billing Profile, management groups, subscriptions, and resource groups containing eligible usage.Step 2: Measure hourly usage
Do not make the decision from monthly spend alone.Look at hourly eligible usage and identify the portion that remains stable over time.
Step 3: Evaluate shared scope
If several subscriptions share financial ownership and reporting can handle allocation, shared scope gives the commitment a larger pool of eligible usage.Step 4: Narrow only when needed
Use management group, subscription, or resource group scope when governance or financial ownership justifies limiting where the benefit can apply.Step 5: Stress-test the commitment
Model what happens if:usage falls 25%
a subscription is retired
workloads move between subscriptions
a product is migrated
architecture changes
Step 6: Review Azure recommendations
Azure offers Savings Plan recommendations through several paths.Azure Advisor provides subscription-scope recommendations using a 30-day lookback.
The Azure portal can surface recommendations for shared, management group, subscription, and resource group scopes.
The Savings Plan Benefit Recommendations API supports shared, management group, and single-scope recommendations with 7-, 30-, and 60-day lookback periods.
For the current recommendation behavior, see Microsoft’s Savings Plan recommendation guidance and the Benefit Recommendations API reference.
After buying a Savings Plan or Reservation, give Azure’s recommendation systems time to reflect the purchase before acting on another recommendation.
Step 7: Monitor after purchase
Review utilization and scope as workloads change.Because Azure can continue adjusting recent Savings Plan benefit allocation within its 48-hour window, avoid treating very recent utilization data as final.
Can you change scope later?
Yes.Microsoft allows you to change Savings Plan scope after purchase.
Rescoping does not restart the term or create a new commercial transaction. It also does not let you change the existing hourly commitment, term length, or billing frequency.
Azure Savings Plans also cannot simply be canceled or exchanged after purchase.
That distinction matters:
Rescoping can correct where the benefit applies. It cannot remove the underlying financial commitment.
Microsoft explains these limitations in its Savings Plan management documentation.
Scope and chargeback
Scope and financial ownership do not always need to match.A subscription-scoped plan can make attribution straightforward.
A shared plan can give more eligible resources access to the commitment, while Azure Cost Management’s amortized-cost data can support internal showback and chargeback.
Microsoft’s Savings Plan chargeback guidance explains how consumption can be analyzed for internal allocation.
A practical workflow is:
1
Open Cost Analysis and switch to Amortized Cost.
2
Filter for Savings Plan-related cost and usage.
3
Group the data by subscription, resource group, resource, or tag.
This supports internal allocation analysis, but Azure does not automatically perform your organization’s chargeback process.
The practical FinOps question is:
Should the commitment follow your infrastructure boundaries or your financial ownership boundaries?
If reporting can solve the allocation problem, broader scope can provide more flexibility.
If strict business-unit isolation is required, a narrower scope may make more sense.
If you are comparing commitment types, see our Azure Reservations vs Savings Plans guide and Azure Reservations guide.
The practical FinOps question is:
Should the commitment follow your infrastructure boundaries or your financial ownership boundaries?
If reporting can solve the allocation problem, broader scope can provide more flexibility.
If strict business-unit isolation is required, a narrower scope may make more sense.
If you are comparing commitment types, see our Azure Reservations vs Savings Plans guide and Azure Reservations guide.
Azure Savings Plan scope checklist
Before purchasing or rescoping:Billing structure mapped
Billing agreement and permissions checked
Eligible subscriptions identified
Stable hourly usage measured
Chargeback requirements documented
Shared scope evaluated
25% usage decline modeled
Planned migrations considered
Azure recommendations reviewed
Existing Savings Plan utilization checked
Commitment owner assigned
How Usage.ai Fits Your Strategy
Choosing the right Azure Savings Plan scope is only part of the commitment decision. Teams also need to separate stable eligible usage from variable demand, account for existing commitments, and monitor utilization as workloads move between subscriptions, resource groups, and management groups.With Flex Insured Commitments, teams can access the upto 65% savings Microsoft publishes for eligible Azure Savings Plan for compute usage, while reducing long-term commitment risk.
If eligible usage drops and part of a qualifying Flex Commitment goes unused, cashback protection can cover the qualifying unused commitment exposure according to the Flex Commitment program terms. Cashback may be provided as cash or credits, depending on the applicable arrangement.
We manage approved Flex Commitments at the billing layer without changing your Azure infrastructure, Savings Plan scope, or how your workloads run. Our fee is based on realized savings, so if we do not generate savings, you do not pay a savings based fee.
Learn more in our Flex Insured Commitments guide.
Disclosure
We are a cloud cost optimization and commitment-management company. Azure Savings Plans are Microsoft products. Microsoft controls Azure pricing, eligibility, discounts, and billing mechanics. Our Flex Commitments are a separate Usage.ai service and are subject to current eligibility and program terms.
We are a cloud cost optimization and commitment-management company. Azure Savings Plans are Microsoft products. Microsoft controls Azure pricing, eligibility, discounts, and billing mechanics. Our Flex Commitments are a separate Usage.ai service and are subject to current eligibility and program terms.
Frequently asked questions
What are the four Azure Savings Plan scopes?
Azure supports shared, management group, subscription, and resource group scopes. The selected scope determines which eligible resources can consume the Savings Plan benefit.
Which Azure Savings Plan scope is best?
There is no universal best option. Shared scope gives you the broadest eligible usage pool, while narrower scopes offer more financial or organizational isolation.
Does unused Azure Savings Plan commitment roll over?
No. Savings Plans work hourly. Unused hourly commitment does not roll into the next hour.
Can I change Azure Savings Plan scope after purchase?
Yes. Microsoft allows scope changes without restarting the Savings Plan term. However, rescoping does not change the existing hourly commitment, term length, or billing frequency.
Does Azure Advisor recommend every Savings Plan scope?
No. Azure Advisor currently provides subscription-scope recommendations. The Azure portal can surface broader scope recommendations, while the Benefit Recommendations API supports shared, management group, and single-scope recommendation requests.
Share
Facebook
X
LinkedIn
Reddit
