Microsoft's standard change of control clause promises nothing more than a good faith conversation when your license count moves more than 10 percent, and that conversation happens after you have already lost your leverage
The EA's acquisition and divestiture language commits Microsoft to process, not remedy, and the MACC sits outside it entirely, so a divested business unit can leave your estate while the unspent commit balance stays on your invoice. Every negotiated protection here has to be written into the Enrollment amendment and the order form before signature, because mid-term relief on a commit of $250K to $100M+ per year is discretionary and Microsoft's own account teams describe it as something they can 'sometimes' do. Fix the words in the paper you are signing this quarter, not the paper you wish you had signed three years ago.
Prepared by Redress Compliance · September 3, 2026 · Microsoft advisory. EA and MCA-E renewal and restructuring engagements, 2024 to 2026.
Executive summary
The 10 percent clause is a scheduling device, not a right, and buyers who rely on it discover that at the worst possible moment.
Standard EA text says that when licenses covered by an Enrollment move more than 10 percent because of an acquisition, divestiture or merger.
Microsoft will work in good faith to accommodate the changed circumstances, which means Microsoft decides the accommodation and prices it against a customer who has already announced the deal.
Your real change of control exposure is the Azure commit, not the license terms, and it is measured in the full unspent balance of a $250K to $100M+ multi-year MACC.
If the divested unit was consuming 30 percent of your Azure spend, the commit does not shrink by 30 percent; the shortfall is invoiced as a single line at term end priced off the EA discount sheet unless a pause or reduction clause was written into the original order form.
Only two transfer events are permitted by default, and everything else needs Microsoft consent that is rarely granted.
The EA allows assignment as part of a divestiture of an Affiliate or division, or a merger involving the Customer or an Affiliate.
Any other movement of licenses, including internal reorganizations that do not change ownership, is invalid without written approval and a pre-transfer License Transfer Form filed before, not after, closing.
Two clauses can unwind an estate you thought was safe: termination on loss of affiliation and cross-default across Enrollments.
Microsoft may terminate a former Affiliate's Enrollment once it stops meeting the more than 50 percent control test, and a breach at one entity that affects other Enrollments can trigger termination of the master agreement and every Enrollment under it.
So both need caps and cure windows in the amendment.
What the standard clauses actually say and where each one lives
The most common mistake in Microsoft restructuring negotiations is redlining the wrong piece of paper.
Buyers spend their legal budget on the Enrollment, which is where the famous 10 percent acquisition and divestiture language sits, while the two clauses that actually decide whether a corporate change costs you money live somewhere else entirely: the Affiliate definition in the MBSA, which is evergreen and therefore survives every renewal you negotiate.
And the MACC terms in the Azure order form, which most legal teams never see because they are treated as commercial paperwork.
Microsoft's default Affiliate test is ownership of more than 50 percent of voting securities or the power to direct management and policies.
That single number determines whether a joint venture, a carve-out held at 49 percent, or an entity in a TSA period is inside your estate or outside it, and no amount of Enrollment drafting fixes a definition written one document up the stack.
| Clause | Document | Default effect | Buyer redline | Negotiability |
|---|---|---|---|---|
| Affiliate definition (>50% control) | MBSA (evergreen) | JVs, minority holdings and carve-outs fall outside the estate | Add named entities and a "under common control or designated in writing" limb | Moderate; easiest at MBSA signature or renewal |
| Permitted transfer events | Enrollment | Only divestiture and merger transfer without consent; all else needs Microsoft approval, rarely given | Add internal reorganization and holding company insertion as permitted events | Moderate |
| License Transfer Form | Enrollment process | Notice must precede transfer or the transfer is invalid | Convert to post-closing notice within 60 days | Low to moderate |
| Loss-of-affiliation termination | Enrollment | Microsoft may terminate the departing Affiliate's Enrollment | Right to novate to a standalone Enrollment at held pricing for 12 to 24 months | Moderate; this is the seller's biggest exposure |
| Cross-default across Enrollments | Enrollment | One entity's breach can unwind every Enrollment | Cap remedy to the affected Enrollment only | High; Microsoft concedes this regularly |
| MACC balance on divestiture | Azure order form | Unspent commit stays payable regardless of who leaves | Proportional reduction and pause on an M&A event | Low unless raised pre-signature |
Read the negotiability column as a sequencing instruction.
The two clauses Microsoft gives up most readily (cross-default caps and Affiliate definition expansion) are the ones buyers rarely table, while the MACC line, the only row where the exposure is denominated in real dollars.
Is the one row almost nobody redlines because it arrives in a document the deal team classifies as an order, not a contract.
The practical consequence: your redline package has to travel across four documents simultaneously, and the MBSA amendment has to be signed at the same moment as the Enrollment, not afterward.
Under MCA-E the problem worsens, because only the signing entity holds enforcement rights, so a divested affiliate has no privity to enforce anything you negotiated on its behalf.
Why 'good faith' is worth zero and what replaces it
"Microsoft will work with the Enrolled Affiliate in good faith to determine how to accommodate its changed circumstances" is a commitment to hold a meeting. It sets no timeline, no formula, no ceiling on what Microsoft can demand in exchange, and no consequence if the conversation goes nowhere.
Worse, the trigger is the moment your leverage is gone: you announce the divestiture, the 10 percent threshold is crossed.
And only then do you sit down with an account team that now knows exactly how much of your estate is stranded and exactly how little competitive optionality a company mid-carve-out has.
In our restructuring engagements the recurring pattern is that Microsoft's answer to the good faith conversation is a renewal, and the price of relief is a longer term or a bigger commit.
Replace the process promise with arithmetic.
The substitute language should state that on a divestiture, merger or reorganization affecting more than 10 percent of licensed users, the Enrolled Affiliate may reduce committed quantities and the MACC by a percentage no greater than the divested share of headcount, revenue or measured consumption.
On 60 days written notice, effective the next anniversary, with no change to unit pricing, discount tier or price hold on the retained estate.
That last clause is the one Microsoft will fight hardest and the one buyers most often forget.
The standard counter is not refusal; it is agreement to the reduction followed by re-tiering the smaller base into a lower discount band, so a 20 percent volume reduction produces a 6 to 9 percent unit price increase and net savings of roughly half what the finance model assumed.
Hold the band by reference to the pre-divestiture quantity for the remainder of the term, and pair it with the price hold language that survives volume movement.
Two timing realities govern this. First, none of it is available mid-term at a price you would accept, because relief on a commit running from $250K to $100M+ per year is discretionary and Microsoft's own field language is that they can "sometimes" help.
Second, everything you win lives in the CTM amendment, which expires with the three-year Enrollment. Treat the divestiture formula as a term you re-table at every renewal, not a permanent win, and diary it 12 months before expiry.
Move from EA to MCA without losing your terms
How to move from a Microsoft EA to the MCA without losing discounts or terms: the transition traps, the price protections to keep, and the timing.
Get the white paper →The MACC is the real change of control clause and nobody negotiates it
Every legal team on the buyer side redlines the license grant. They fight over the affiliate definition in the MBSA, they argue about the >50% control test, they insist on notice periods for the termination on loss of affiliation provision.
All of that is worth doing, and none of it is where the money now sits. Microsoft has quietly relocated change of control risk from the grant, where buyers push, to the consumption commitment, where they do not.
The Azure commitment (MACC) is a separate financial instrument riding alongside the Enrollment, and the EA's acquisition and divestiture language does not reach it.
You can execute a clean license transfer, satisfy every procedural requirement in the License Transfer Form, and still owe the full unspent balance on a commitment the divested business was consuming against.
Understand the asymmetry precisely. When you divest a business unit, that unit's Azure consumption stops flowing through your subscription on day one of separation. Your commitment does not adjust.
If a $30M three year MACC was underwritten on an estate where the divested division represented 35% of run rate, you have just created roughly $10M of exposure that has to be absorbed by the remaining business or paid as shortfall. And shortfall is not settled at your negotiated consumption rates.
It is settled against the committed total, which means you are paying the discounted price sheet value of capacity you will never provision. That is a bill for nothing, and it arrives at true up or term end when you have zero negotiating position left.
Ask your account team what happens in that scenario and you will get a version of the same answer we hear on nearly every restructuring engagement: we can sometimes work with you on that. Sometimes. Not shall. The word is doing exactly the work Microsoft intends it to do.
Restructuring relief on a commit is a discretionary concession granted by a field sales organization measured on commitment attainment, and the person deciding whether to grant it is the same person whose quota shrinks when they do.
Treating that as a contractual protection is not risk management, it is hope. The buyer who thinks the good faith clause covers it has confused a promise to talk with a promise to pay.
The corrective language is well established and costs nothing at signature. A pause clause suspending commit accrual for a defined window (90 to 180 days) following a divestiture or carve out. Annual carry forward of unused commit so a bad year does not become a terminal shortfall.
Term forgiveness on defined hardship grounds. An acceleration right converting unspent commit to reserved instances or a savings plan at term end rather than forfeiting it. A currency lock at signing for multi entity groups.
Quarterly commit progress visibility written into the order form so you see the gap forming twelve months out instead of six weeks out. Microsoft signs these when they are tabled early against a live commitment decision.
The same language becomes unobtainable the moment you are in breach, because at that point Microsoft is negotiating against a liability it already holds.
Which defines the leverage window exactly: the moment before any transaction is announced. Once a divestiture is public, Microsoft's account team knows your consumption base is about to fall, knows the shortfall math better than your procurement team does, and knows you cannot walk.
Before the announcement, you are a customer contemplating a commitment increase and Microsoft wants the paper signed. That is when a pause clause is a rounding error in the negotiation. Six months later it is a $10M concession request.
The same words, two entirely different prices, and the only variable that changed is what Microsoft knows.
This is a coordination failure more than a contracting failure. Corporate development runs transactions under NDA and does not brief licensing. Licensing signs three year commitments without visibility into the pipeline.
Neither team is wrong on its own terms, and the gap between them is worth millions.
The remedy is procedural: any commitment above roughly $5M annually gets restructuring protections drafted in as standard, whether or not a deal is contemplated, on the assumption that something will happen inside a 36 month term.
Treat it the way you treat the rest of the EA redline set: insurance you buy while it is cheap. Deal teams and licensing teams have to be connected before the press release, not after it.
Buying in: adding acquired entities without repricing the base
The inbound side has better economics and worse discipline. When you acquire, Microsoft sees new estate arriving and reads it as a repricing event. Your position is that an acquisition is an affiliate accession under an existing agreement, not a new deal.
Get that written down: a pre agreed accession mechanism letting acquired entities join the Enrollment at your current price sheet and discount level for the remainder of the term, with no reopening of the base.
Pair it with a true up grace period of 90 to 180 days so you are not counting seats in an estate you have not finished inventorying, and cap any tier movement so that crossing a volume threshold moves you down in price, never up in commitment.
Microsoft will counter three ways, in this order. First, a separate Enrollment for the acquired entity at current list, which strands the new estate outside your discount and quietly resets price protection.
Second, a co-terminous term shortened to force an early consolidated renewal, which is really a request to renegotiate your whole base a year ahead of schedule. Third, an uplift on the combined base justified as a new tier or a new price band.
All three are declinable, and declining them is easier if your renewal uplift cap is already sitting in the amendment.
| Microsoft counter | What it actually costs | Buyer position to hold |
|---|---|---|
| New Enrollment at current list | Acquired estate outside your discount, price protection reset | Accession at existing price sheet, remainder of term |
| Shortened co-terminous term | Early renewal of the full base, 12+ months ahead | Acquired entity co-terms to your existing end date, no term change |
| Uplift on combined base | Discount erosion on seats you already owned | Volume tier moves down only, never up |
| Immediate true-up on acquired seats | Payment before inventory is complete | 90 to 180 day grace, true-up at next anniversary |
The row that matters most is the shortened term.
Microsoft frames it as administrative tidiness (one end date, one renewal, simpler for everyone), and it is the single most expensive concession in the table because it hands back your remaining price protection and reopens a base you already negotiated.
In our experience across restructuring engagements, buyers who concede co-termination lose more value on the existing estate than on the acquired one.
The tell that you are being repriced rather than accommodated: Microsoft's proposal touches seats you already owned. Accession language should be strictly additive. If the redline changes anything about the base, it is a renewal wearing a different name.
Selling out: divestiture, TSA periods, and the licenses that cannot follow
The sell side is where the standard paper turns hostile. The moment a subsidiary stops meeting the more than 50 percent control test in the MBSA affiliate definition, the Enrolled Affiliate has an obligation to notify Microsoft and Microsoft acquires the right to terminate that Enrollment.
Read that sequence carefully: your disclosure triggers their option.
Nothing in the agreement obliges Microsoft to let the divested business keep running on your paper for a single day past close, and the fallback is whatever early termination rights the Enrollment happens to carry, which is usually nothing worth having.
What Microsoft does next is entirely predictable, because it is the commercially rational move: the account team routes the carved-out entity to a new EA or MCA-E at list, with no inherited discount tier, no price hold, and a fresh three year commitment.
On a 3,000 seat carve-out running E5, the delta between your negotiated per user rate and a standalone list rate is routinely 25 to 40 percent in our engagements, and the buyer will push that cost back at you in the purchase agreement.
The redline is a written transition services right in the Enrollment amendment, not in the TSA with the buyer.
Target 12 to 24 months during which the divested entity is deemed an Affiliate for licensing purposes and continues to consume under your Enrollment at your negotiated rates, with Microsoft's termination right suspended for that window.
Microsoft will counter with 6 months and a requirement that the entity sign its own agreement at month one. Twelve is achievable when the divestiture is already public and the incoming buyer is a Microsoft prospect; 18 to 24 is achievable when you are simultaneously signing a renewal.
Pair it with the pre-transfer License Transfer Form obligation (transfers are void without it, filed before close, not after) and with the uninstall and render-unusable obligation, which means anything not formally assigned has to come off the divested estate on day one.
Cap the cross-default so a carve-out's breach cannot unwind your remaining Enrollments; that language belongs in the same amendment set covered in our Microsoft EA and MCA-E redline playbook.
Under MCA-E the problem is structurally worse: only the signing entity has enforcement rights, so a divested affiliate has no privity and no standing to enforce anything you negotiated.
If you are on MCA-E, the transition right has to be enforceable by you on the divested entity's behalf, in writing, before signature.
What we see across restructuring engagements
Buyers invoking the EA acquisition and divestiture clause after deal announcement are typically offered a credit toward future spend, not a reduction in commit.
Unspent commit is billed at term end regardless of the divested consumption that was never going to materialize.
Five patterns repeat across restructuring work with enough regularity to plan around.
First, the 10 percent clause gets invoked after announcement, when the buyer has already told the market the business is leaving, and Microsoft responds with a credit applied to future spend rather than a reduction to the current commit.
That is not relief, that is a lock-in extension dressed as accommodation. Second, MACC shortfalls surface at term end as a single reconciliation line, with no interim warning, because quarterly commit visibility was never written into the order form.
Third, corporate change amendments negotiated in the last cycle quietly disappear at renewal, because they are CTM terms tied to a three year Enrollment term and the renewal paper does not carry them forward unless someone re-tables them.
Fourth, joint ventures fail the more than 50 percent voting securities test and need an MBSA amendment, which nobody discovers until the JV tries to provision. Fifth, transfers get voided for a missing License Transfer Form, months after close, usually during an audit.
The common thread is timing, not language. Every one of these patterns is a protection that existed as a negotiable term at signature and became a discretionary favor after the corporate event was public.
Microsoft's leverage is not in the clause wording, it is in the fact that you are asking for something after you have announced you cannot walk away. Invoke the change of control conversation before the deal is public, or better, pre-negotiate the formula so there is nothing to discuss.
Practically: build a clause register at signature listing every negotiated corporate change term, its CTM location, and its expiry date, and calendar it 12 months before renewal alongside your renewal uplift cap work. Amendments you do not re-table are amendments you no longer have.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
Your first five moves
- Pull the MBSA and the CTM before you touch the renewal quote, and confirm in writing whether any acquisition, divestiture, affiliate definition, or cross-default language survived the last renewal, because negotiated amendments expire with the three-year Enrollment term and most estates discover the protections lapsed only when a deal is already signed.
- Model the shortfall against your live MACC at 20 to 40 percent consumption loss, since that is the range we typically see when a business unit carrying its own Azure footprint exits mid-term; on a $10M annual commit that is $2M to $4M of unspent balance you still owe, and that number is the entire basis for the conversation.
- Table the formula-based reduction right and the MACC pause clause as one redline package, not two separate asks, so Microsoft cannot concede the license-count adjustment (cheap for them) and quietly leave the commit untouched; demand the reduction be arithmetic (proportional to the divested entity's trailing twelve-month consumption) rather than "good faith," and pair it with the broader Enrollment redline set so it reads as standard practice.
- Cap cross-default to the affected Enrollment with a 30 to 60 day cure period, because the standard form lets Microsoft terminate the agreement and every Enrollment under it when a breach "affects other Enrollments," which hands a single divested affiliate's compliance error the power to unwind the entire estate.
- Lock the TSA and accession mechanism before any transaction enters diligence, specifying a minimum 12-month transition service window, named acquired entities added at existing per-unit pricing, and a pre-agreed License Transfer Form path, alongside your price hold protection so additions do not reprice the base.
Frequently asked questions
Does the Microsoft EA 10 percent change clause let me reduce my license count after a divestiture?
No. The clause states that if the number of licenses covered by an Enrollment changes by more than 10 percent due to an acquisition, divestiture or merger, Microsoft will work with you in good faith to accommodate the changed circumstances. That is a commitment to a conversation, not to a reduction.
In practice Microsoft controls the outcome and typically offers a credit toward future spend rather than a cut to committed quantities, which is why the clause should be replaced with a defined formula before signature.
Can I transfer Microsoft licenses to a company that buys one of my business units?
Only if the transaction is a divestiture of an Affiliate or a division of an Affiliate, or a merger involving you or an Affiliate. Those are the two default-permitted transfer events in the EA.
Any other transfer requires Microsoft's explicit written consent, which is rarely granted, and you must file a License Transfer Form with Microsoft before the transfer closes. On transfer you must uninstall, discontinue use and render your copies unusable.
Where is the Microsoft Affiliate definition and what is the ownership threshold?
The Affiliate definition sits in the MBSA, the evergreen umbrella agreement, not in the Enrollment. The standard test is ownership of more than 50 percent of the voting securities in an entity, or the power to direct the management and policies of an entity.
Joint ventures and minority-held entities routinely fail this test and require a specific MBSA amendment to be covered, which is a negotiation you have to run upstream of the Enrollment.
What happens to my Azure MACC if I divest a business that was consuming Azure?
Nothing, unless you wrote a clause for it. Microsoft treats the MACC as a fixed contractual commitment for the term, and if cumulative eligible consumption at term end falls below cumulative commit, the shortfall can be invoiced as a single line calculated at your EA discount price sheet.
Mid-term relief only happens under documented M&A, divestiture or material business event clauses that were written into the original order form. Ask for a pause clause, annual carry forward and term forgiveness on hardship grounds at signature.
Is the change of control position worse under MCA-E than under an EA?
Structurally, yes. Under the MCA only the original signing entity has enforcement rights even where products are provisioned to affiliates, so a divested entity has no privity to enforce anything against Microsoft.
MCA transfer rights are also narrower and event-gated, permitting transfer of fully paid perpetual licenses only in specific circumstances such as a merger or divestiture.
Multinationals with distinct regional compliance teams should assume less protection and negotiate accession and exit mechanics explicitly.
Can Microsoft terminate my whole agreement because one entity breached?
The standard cross-default language allows it. If a breach affects other Enrollments and cannot be resolved between Microsoft and the Customer within a reasonable period, Microsoft may terminate the agreement and all Enrollments under it.
This is an accepted redline target: cap termination to the affected Enrollment only, define 'reasonable period' as a specific cure window of 30 to 60 days, and require written notice to a named legal contact.
Do negotiated change of control terms carry over at renewal?
No. Negotiated corporate change language lives in the customer terms and modifications amendment attached to the Enrollment, and the Enterprise Enrollment term is typically three years. Those amendments expire with the term and must be re-tabled and re-agreed at every renewal.
Treat the retention of prior negotiated language as a distinct renewal ask, not an assumption, and check the MBSA separately because it is evergreen and may carry different wording.
