Review Azure EA and MCA commitment scope
On this page
For Azure Enterprise Agreement (EA) or Microsoft Customer Agreement (MCA) commitments, use the broadest scope that matches your financial ownership rules. Before changing it, verify the enrollment or billing profile, eligible consumers, and utilization. Treat cost and usage views as separate context, then investigate eligibility before making a scope change.
Why this is worth a look
This workflow is limited to EA and MCA commitments. Scope selects where reservation or savings plan benefits apply, while the resource must still be eligible. Resource group and subscription scopes limit the selected area. Management group scope requires subscriptions to be in both the management group hierarchy and the same enrollment or billing profile as the purchase. Shared scope covers eligible subscriptions in the EA enrollment or MCA billing profile, including Microsoft Entra tenants in that context. Azure processes resource group, subscription, management group, and shared scopes in that order.
Run this check
CHECKLISTA portal-based, read-only review for mapping EA or MCA commitment scope, billing context, eligible consumers, utilization, and related cost or usage views.
Execution surface: Azure portal. This checklist only reads reservation or savings plan details, utilization, and cost or usage views; stop before any scope or configuration change.
Applicability: EA and MCA commitments only. Do not use this workflow for CSP, individual pay-as-you-go, or Microsoft Partner Agreement arrangements.
Permissions: use a Reservation reader or equivalent reservation access for reservations, and the required savings-plan viewing or billing access for savings plans. Commitment-management permission is separate from subscription permission.
Scope: review the applicable EA enrollment or MCA billing profile, subscriptions, resource groups, management groups, and Microsoft Entra directories. Time window and units: point-in-time scope details; use the available utilization and cost or usage view periods and their reported units.
[ ] For an EA or MCA commitment, identify the applicable EA enrollment or MCA billing profile.
[ ] Open Reservations that you can access, select each reservation, and record the available identifying, commitment, scope, selected subscription or resource group, and directory details.
[ ] For savings plans, go to Cost Management + Billing, select the applicable Billing scope or Billing profile, then Products + services > Savings plans. Record the available identifying, commitment, scope, selected subscription or resource group, and directory details.
[ ] List the subscriptions and resource groups intended to consume each benefit.
[ ] For management group scope, confirm each intended subscription is in both the hierarchy and the same enrollment or billing profile as the purchase.
[ ] For shared scope, identify eligible subscriptions and Microsoft Entra tenants in the applicable EA enrollment or MCA billing profile.
[ ] Review available utilization views and record unused benefit using the view's reported period and units.
[ ] Review available cost and usage views or exports as a separate source of context. Do not treat them alone as proof that specific usage is eligible outside the commitment.
[ ] Account for Azure's processing order: resource group, subscription, management group, then shared scope.
[ ] Document the proposed scope, ownership reason, expected consumers, and intentionally excluded subscriptions for the billing owner. Stop before changing configuration.How to confirm it
- 01
Confirm the supported billing context
Use this procedure only for Azure Enterprise Agreement or Microsoft Customer Agreement commitments. For each commitment, identify the applicable EA enrollment or MCA billing profile. Stop and use arrangement-specific guidance for CSP, individual pay-as-you-go, or Microsoft Partner Agreement commitments.
- 02
Record accessible commitment details
For reservations, open Reservations you can access and select each reservation. For savings plans, use Cost Management + Billing, the applicable Billing scope or Billing profile, and Products + services > Savings plans. Record the available identifying, commitment, scope, selected resource, and directory details.
- 03
Map intended consumers
List the subscriptions and resource groups that should consume each benefit. For management group scope, verify both hierarchy membership and membership in the same enrollment or billing profile as the purchase. For shared scope, identify eligible subscriptions and Microsoft Entra tenants in the EA enrollment or MCA billing profile.
- 04
Review utilization and cost views
Review the available utilization view and record unused benefit using its reported period and units. Review cost and usage views or exports separately for context, but do not treat them alone as proof that specific usage is eligible outside the commitment. Scope still applies only to eligible resources.
- 05
Prepare a controlled decision
Document the proposed scope, ownership reason, expected consumers, and intentionally excluded subscriptions for the billing owner. Azure processes resource group, subscription, management group, and shared scopes in that order. Stop before changing configuration.
Before making changes
Assume the commitment is an Azure Enterprise Agreement or Microsoft Customer Agreement commitment, you have read access to the relevant commitment and billing views, and the listed subscriptions, resource groups, management groups, and directories are being reviewed in the applicable billing context. This is a point-in-time portal review, not a billing calculation. Savings-plan rescoping does not change its term. Reservation operations have their own rules, so review the applicable reservation operation before changing scope. Scope does not make an ineligible resource eligible.