Microsoft Cloud Agreements and Subscriptions. Four commercial vehicles, each with different term, flexibility, and renewal mechanics.

Microsoft sells cloud subscriptions to enterprise customers through four primary agreement vehicles, each with different commercial mechanics, different commitment requirements, and different exit paths.

• Enterprise Agreement (EA). The legacy multi year volume licensing vehicle. Requires a minimum 500 user enterprise level commitment with three year term, true up at end of year, and a Microsoft direct sales motion.
• Microsoft Customer Agreement for Enterprise (MCA E). The strategic replacement, with cleaner contract language, no minimum size, and Azure consumption commit through MACC.
• Cloud Solution Provider (CSP). Operates through Microsoft partners with the New Commerce Experience (NCE) terms. Annual lock, no mid term cancellations except in a narrow seven day window, monthly available at a premium.
• Microsoft Online Services Subscription Agreement (MOSA). The legacy direct subscription vehicle, mostly retired.

The choice between these vehicles is the single biggest contract structure decision a Microsoft customer makes, and it shapes pricing, term flexibility, partner involvement, and renewal mechanics for the entire Microsoft estate.

This paper sets out the four vehicles, the EA to MCA E transition mechanics that Microsoft has been driving customers through since 2022, the CSP NCE flexibility loss, the audit posture across each, and the eleven move buyer side playbook. Read the related Microsoft services practice, the CSP versus Enterprise Agreement for M365, and the Microsoft Enterprise Agreement 2026 guide.

The four Microsoft commercial vehicles compared

The EA to MCA E transition

Microsoft has been driving customers to migrate from the Enterprise Agreement to the Microsoft Customer Agreement for Enterprise since the MCA E launch in 2021. Most enterprise EAs renewing in 2024 to 2026 are being proposed as MCA E renewals. The mechanical changes:

• Simpler contract structure. Online terms, no Master Business Agreement, fewer amendments.
• Flexible term length. One, three, or five year, instead of the rigid three year EA.
• Azure MACC built in. Microsoft Azure Consumption Commitment as the standard Azure commitment vehicle.
• Real time provisioning. No more annual true up; usage flows in the month it happens.
• Subscription Renewal. Microsoft will auto renew under MCA E unless the customer opts out within the notification window.

The commercial differences are subtle but material. The EA discount mechanism (Level A through D based on enterprise size) maps imperfectly to MCA E commercial structure. Multi year price holds that customers had under EA need explicit negotiation under MCA E. The buyer side rule is to never accept an MCA E proposal that does not preserve every commercial protection the EA had, plus the MCA E flexibility additions on top.

Microsoft 365 and Dynamics 365 subscription mechanics

Under any of the four agreement vehicles, Microsoft 365 and Dynamics 365 are sold per user per month. The actual list prices are vehicle agnostic, but the negotiated discount band varies:

• EA: Level A through D enterprise discount tiers plus negotiated discount. M365 E3 typically lands at $30 to $36 per user per month against the $36 list. M365 E5 at $50 to $57 against the $57 list.
• MCA E: Similar negotiated discount band, with the additional benefit of multi year price protection that EA cannot match.
• CSP NCE: Partner controlled discount, typically 5 to 15 percent below MCA E direct on annual commits. Monthly carries a 20 percent premium versus annual.
• MOSA: No volume discount mechanism. Mostly retired for enterprise customers.

Term length economics

The term length decision is critical to the buyer side outcome:

• One year MCA E. Maximum flexibility, no price protection beyond the year. Useful for customers in major business change (M and A, divestiture, restructuring).
• Three year MCA E. The default for enterprise customers. Negotiated discount typically beats one year by 3 to 7 percentage points, with price protection across the term.
• Five year MCA E. Used by Microsoft to lock in the deepest discounts. Customer must be confident in the user count and product mix five years out. Frequently the wrong choice for high growth or high churn organizations.
• CSP annual. Useful for the variable portion of the user base (contractors, project staff, populations subject to reorganization).
• CSP monthly. The premium is real (20 percent) but the flexibility is also real. Use for genuinely variable populations only.

CSP NCE and the flexibility loss

The New Commerce Experience (NCE) replaced the older CSP licensing model in 2022 and removed most of the mid term cancellation flexibility customers had relied on. Under NCE:

• An annual commit can be canceled only in a seven day window at the start of the term.
• A three year commit has no cancellation right.
• Monthly subscriptions are available but at a 20 percent premium versus annual.

The CSP NCE option still wins for customers running through preferred partners for value added services, but the flexibility loss has shifted many enterprise customers back toward MCA E direct. Read the related CSP versus EA for M365.

Renewal mechanics under each vehicle

Renewal posture differs materially across the four vehicles:

• EA renewal: Microsoft proposes renewal nine months before term end. True up at year three before renewal sets the size. Customers can transition to MCA E at renewal.
• MCA E renewal: Auto renews under Subscription Renewal unless customer opts out in the notification window (typically 60 days before term end). Customers can renegotiate term length and commit at renewal.
• CSP NCE renewal: Auto renews at the same term length unless the customer opts out in the seven day window at term end. The partner controls the renewal commercial conversation.

Flexibility mechanics: seat additions, removals, product swaps

The single most important flexibility consideration is the ability to scale users down at renewal. Microsoft Cloud agreements vary materially on this:

• EA: Add at any time during the term (subject to true up). Cannot reduce until renewal.
• MCA E: Same as EA on additions. Removals are time bound; once committed, the seat count cannot reduce mid term.
• CSP NCE annual: Cannot add or remove except in the seven day window or through new SKU purchases.
• CSP NCE monthly: Add or remove month over month, at a 20 percent premium.

The audit posture across vehicles

Microsoft does not formally audit cloud subscription usage the way it audits perpetual license deployments. The data is in the customer's tenant. The audit risk is in two places. First, M365 license assignment integrity (assigning licenses to users who do not exist, dual licensing through hybrid deployments). Second, Azure consumption that exceeds the contracted commit, triggering overage at standard list rates. Read the related Microsoft audits and license compliance playbook.

The eleven move buyer side cloud agreements playbook

1. Inventory the current Microsoft cloud footprint. M365, D365, Power Platform, Azure, Windows 365, Project, Visio, every subscription line.
2. Map current agreement vehicles. EA, MCA E, CSP (which partners), MOSA legacy.
3. Model the EA to MCA E transition impact. Discount preservation, price protection, term flexibility, Azure MACC integration.
4. Right size the user base before renewal. Audit M365 license assignments, remove inactive users, identify reassignable seats.
5. Segment users by stability. Stable core (multi year MCA E), variable (annual CSP), highly variable (monthly CSP at premium).
6. Negotiate the price protection clauses on MCA E. Annual rate increase cap, multi year price holds on negotiated SKUs.
7. Negotiate CSP partner margin and value adds. If running CSP, understand the partner economics and what value adds justify the model.
8. Hold the competitive frame. Google Workspace plus Vertex AI as M365 alternative. AWS as Azure alternative. The frame matters even if migration is unlikely.
9. Negotiate the Subscription Renewal opt out mechanics. Calendar reminders at least 90 days before notification windows close.
10. Audit the Azure commit against actual consumption. Right size MACC at MCA E renewal.
11. Run the conversation through Vendor Shield. Microsoft cloud agreements interact with SA, Copilot, Power Platform, and Azure. Read the related Vendor Shield, the renewal program, and the benchmarking practice.

How we engage on Microsoft cloud agreements

• Cloud agreements scoping. Six week buyer side review of agreement vehicle inventory, EA to MCA E transition impact analysis, user mix segmentation, and term length recommendations. Outputs a numbered move list with dollar values against each.
• Cloud agreements negotiation. Twelve to twenty week negotiation engagement covering the vehicle transition, discount preservation, price protection, term length, and renewal mechanics.
• CSP partner evaluation. Independent assessment of CSP partner options, margins, value added services, and the right portfolio split between MCA E direct and CSP.
• Cross vendor benchmarking. The benchmarking practice compares MCA E pricing, EA renewal mechanics, and CSP partner economics against comparable customers.
• Vendor Shield. Always on multi vendor engagement covering Microsoft cloud agreements alongside the Software Assurance, Azure commit, and competitive alternative conversations.
• Run the assessment. The software spend assessment sizes the Microsoft cloud footprint before negotiations begin.