Savings plan scopes
Setting the scope for a savings plan selects where the benefits apply.
You have the following options to scope a savings plan, depending on your needs:
Scope options
- Single resource group scope - Applies the savings plan benefit to eligible resources in the selected resource group only.
- Single subscription scope - Applies the savings plan benefit to eligible resources in the selected subscription.
- Management group - Applies the savings plan benefit to eligible resources within all subscriptions contained in both the management group and billing scope.
- Shared scope - Applies the savings plan benefit to eligible resources within subscriptions that are in the billing context. If a subscription was moved to different billing context, the benefit will no longer be applied to this subscription and will continue to apply to other subscriptions in the billing context.
- For Enterprise Agreement customers, the billing context is the enrollment. The savings plan shared scope would include multiple Microsoft Entra tenants in an enrollment.
- For Microsoft Customer Agreement customers, the billing scope is the billing profile. Usage from all billing subscriptions under the billing profile, is eligible to receive benefits for a Shared scoped savings plan.
Scope processing order
While applying savings plan benefits to your usage, Azure processes savings plans in the following order:
- Savings plans with a single resource group scope.
- Savings plans with a single subscription scope.
- Savings plans scoped to a management group.
- Savings plans with a shared scope.
You can always update the scope after you buy a savings plan. To do so, go to the savings plan, select Configuration, and rescope the savings plan. Rescoping a savings plan isn't a commercial transaction, so your savings plan term isn't changed. For more information about updating the scope, see Update the scope after you purchase a savings plan.
Next steps
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for