Microsoft 365 EA vs CSP vs MCA buying is one of the most consequential and least understood choices in a Microsoft estate. These are the three main commercial routes to license Microsoft 365: the Enterprise Agreement, the Cloud Solution Provider program, and the Microsoft Customer Agreement. Each prices, commits, and flexes differently, and the wrong fit can lock you into rigidity or list pricing for years. Getting it right is part of our Microsoft 365 optimization work and feeds the wider digital workplace cost optimization program.
Source: Microsoft licensing and purchasing program documentation (microsoft.com), as of June 2026. Program terms, thresholds, and mechanics change often, so verify the current rules before committing.
The Enterprise Agreement
The Enterprise Agreement, or EA, is the traditional volume route for larger organizations, historically aimed at higher seat counts. It is a multi year commitment, typically three years, with annual true ups and price protection across the term.
True up and true forward
The EA works on a commit then reconcile model. You commit to a baseline, then a true up reconciles for seats added during the year. More recently, true forward mechanics mean increases can carry forward rather than being billed retroactively in some cases. The practical effect is that the EA flexes upward easily but rarely downward mid term, so over committing at signing is costly. This is why right sizing before an EA renewal matters so much, a theme we develop across license right sizing.
Where the EA fits
The EA suits large, stable organizations that value price protection across a term and can forecast a reliable baseline. Its weakness is downward flexibility: if your headcount falls, you generally keep paying the committed baseline until renewal.
The Cloud Solution Provider program
The Cloud Solution Provider program, or CSP, is the partner led route. You buy through a Microsoft partner rather than directly, and that partner handles billing, support, and often value added services. You can read the short definition in our glossary entry on cloud solution provider.
Flexibility and terms
CSP is generally more flexible on seat counts than the EA, with monthly or annual terms depending on the subscription, which makes it attractive for organizations with changing headcount. Pricing depends heavily on the partner, so the quality and independence of the partner relationship matters. Because a CSP partner often earns margin on the sale, it is worth remembering that their incentive is not always the same as yours.
Where CSP fits
CSP suits small and mid market organizations, those with variable headcount, and buyers who want a partner to manage the relationship. The trade off is that pricing and advice come through a party with a commercial interest in the sale.
The Microsoft Customer Agreement
The Microsoft Customer Agreement, or MCA, is Microsoft's simplified, evergreen purchasing agreement, available directly from Microsoft or through a partner. It is designed to replace older agreement structures with a single, perpetual agreement that does not expire on a fixed term in the way an EA does.
How it differs
The MCA removes the fixed multi year enrollment cycle and aims for a more transactional, flexible purchasing experience. It can be a route for organizations that do not meet or no longer want the EA commitment, and it is increasingly the default direction Microsoft steers buyers toward. As with any route, the terms you actually sign matter more than the label.
EA vs CSP vs MCA at a glance
| Dimension | EA | CSP | MCA |
|---|---|---|---|
| Typical buyer | Larger, stable orgs | SMB and mid market | Broad, increasingly default |
| Commitment | Multi year, usually three | Monthly or annual | Evergreen, flexible |
| Upward flex | Easy via true up | Easy | Easy |
| Downward flex mid term | Limited | More flexible | More flexible |
| Bought through | Microsoft or LSP | Partner | Microsoft or partner |
| Price protection | Across the term | Partner dependent | Varies |
Source: Microsoft purchasing program documentation (microsoft.com), as of June 2026. Treat this as directional; confirm current thresholds and mechanics before committing.
How the route shapes your leverage
The buying route is not just procurement plumbing. It determines whether you can shed seats when headcount falls, how price increases are capped, and how much room you have at renewal. An EA locked at the wrong baseline keeps you paying for seats you no longer use. A CSP relationship with a partner whose pricing is opaque can quietly cost more than a direct route. The route should be chosen alongside your tier mix, covered in when E5 is worth it and when it is not, and with an eye on bundling pressure from Microsoft and your audit and compliance position.
The buyer side view
Microsoft and its partners each have a preferred route, and it is not always the one that serves you best. An independent advisor, paid only by you and taking no vendor or partner commission, can model EA vs CSP vs MCA against your real headcount trajectory, renewal timing, and tier mix, then recommend the route that keeps your spend flexible and your leverage intact. For the contract terms themselves, always consult your own counsel.