Microsoft has reshaped the commercial structure of its enterprise relationship more in the last 24 months than in the previous decade. The Enterprise Agreement (EA) is no longer the default for many large customers, replaced by the Microsoft Customer Agreement Enterprise (MCA Enterprise). The Microsoft Azure Consumption Commitment (MACC) has displaced legacy monetary commitments. Microsoft 365 has been restructured around AI add ons, with Copilot, Copilot Studio, and the broader AI agent surface introducing new SKUs at every layer. List price increases have been pushed through on multiple SKUs in 2025 and 2026, and the partner ecosystem (LSPs and CSPs) has been reshaped to favor direct selling on the largest accounts.
This playbook is the buyer side framework for navigating the new model. It is the same approach our advisors apply when we sit on the customer side of an EA renewal, an MCA Enterprise migration, a MACC negotiation, or a Copilot scaling decision. Pair this with our Microsoft Knowledge Hub, our Microsoft services overview, and our Microsoft EA renewal playbook.
The 2025 to 2026 model shift
Three changes define the new Microsoft commercial model. Each has its own customer impact. Together they reshape every renewal conversation.
- EA to MCA Enterprise migration.Microsoft has been moving large customers from the EA to the Microsoft Customer Agreement Enterprise. The MCA Enterprise is structurally different. Pricing flows through Microsoft directly. Terms are more cloud native. The legacy LSP role is reduced.
- MACC over monetary commitment.The legacy Azure monetary commitment has been replaced for most large customers by the Microsoft Azure Consumption Commitment, with more aggressive commitment level targets and discount mechanics tied to multi year flexibility.
- AI bundling.Microsoft 365 Copilot, Copilot Studio, Power Platform AI, Sales Copilot, and Service Copilot are reshaping the M365 SKU stack. New AI SKUs carry premium pricing. Bundling decisions affect long term commitment.
EA or MCA Enterprise: the structural choice
For large customers approaching renewal, Microsoft increasingly proposes a transition from EA to MCA Enterprise. The transition is positioned as a simplification. The customer impact is more nuanced.
EA characteristics
- Sold through Licensing Solution Providers (LSPs).
- Three year term standard, with annual true up.
- Price levels (A, B, C, D) tied to seat count.
- Established discount mechanics and predictable renewal motion.
- Software Assurance for on premises products with full benefits.
MCA Enterprise characteristics
- Sold through Microsoft directly, with optional partner roles.
- Annual or multi year terms with more flexible commitment structures.
- Cloud native commercial mechanics tied to Azure consumption.
- Pricing through Microsoft list with negotiated discounts.
- Software Assurance benefits in transition for on premises products.
Decision framework
The right choice depends on the workload mix. Customers with heavy Azure consumption, mature cloud operations, and a desire for direct Microsoft engagement benefit from MCA Enterprise. Customers with a heavy on premises Microsoft estate, a strong LSP relationship, and a preference for predictable price level mechanics benefit from staying on the EA. Many customers will run a hybrid for a period, with the EA for on premises and Microsoft 365, and an MCA Enterprise or separate MACC for Azure. We have negotiated all three configurations. None is universally correct.
Microsoft 365: the new stack
Microsoft 365 has been restructured around the AI surface. The customer's seat licensing decisions now span more layers than before.
The base stack
Microsoft 365 E3 and E5 remain the base SKUs for enterprise users. E3 covers core productivity. E5 adds advanced security, advanced compliance, advanced analytics, and Teams Phone. The E3 to E5 step up is the largest single seat decision in most M365 portfolios. We model the step up against actual usage of the E5 components and typically find the right answer is mixed (some users on E3, some on E5) rather than uniform.
Microsoft 365 Copilot
Microsoft 365 Copilot adds AI capabilities to Word, Excel, PowerPoint, Outlook, Teams, and the broader M365 surface. The seat pricing has held at 30 dollars per user per month list. The prerequisite is M365 E3 or E5 for the user. Copilot scaling decisions are commercial, not just productivity.
Three patterns of Copilot deployment have emerged. Universal deployment across the workforce, typically negotiated as part of a broader EA or MCA Enterprise renewal at deeper discount. Targeted deployment to high value roles (sales, executives, customer service), with a smaller commitment but uncertainty on expansion. Pilot only, with the customer maintaining flexibility on long term commitment. Each carries different commercial implications. See our Copilot licensing brief for deep mechanics.
Copilot Studio and the agent surface
Copilot Studio is the platform layer for building custom AI agents on the Microsoft stack. The pricing is consumption based, with message credits as the unit. The customer's commercial decision is whether to commit to a Copilot Studio capacity tier or to consume on demand. Most large enterprises are still in pilot. The first commercial commitments are emerging in 2026 renewals.
Power Platform restructure
Power Platform (Power Apps, Power Automate, Power BI, Power Pages) has been restructured several times in the last 18 months. The pay as you go model has expanded. The per app and per user licensing has been refined. AI capacity has been added. The cumulative effect is a portfolio that requires careful attention at renewal. Customers who carry over the previous configuration without re evaluating typically overpay. See our Power Platform CIO playbook.
Azure: MACC, AHB, and reservation mechanics
MACC mechanics
The Microsoft Azure Consumption Commitment is now the default discount instrument for large Azure customers. The commitment is to a multi year Azure spend in exchange for negotiated discounts and access to incentives. The first proposal anchors on commitment level. The customer's leverage is in commitment level, drawdown rules, eligible services, and true down rights.
The trap is straightforward. Microsoft sales is incentivised on commitment level. The headline discount is decoy. Buyers who anchor on discount lose. Buyers who anchor on commitment level, drawdown flexibility, eligible services, and true down rights win. We cover MACC mechanics in detail in our Azure cost optimization playbook.
Azure Hybrid Benefit
AHB remains the single largest underclaimed discount in most Microsoft estates. Customers with active Software Assurance on Windows Server or SQL Server should run AHB at near 100 percent coverage. Most customers run at 50 to 70 percent. The fix is mechanical: inventory licenses with SA, reconcile against Azure VMs and Azure SQL, apply AHB everywhere eligible, document quarterly. See our Windows Server and SQL hybrid licensing brief.
Reservation portfolio
Three year reservations cost approximately 35 percent less than one year reservations. Most customers run portfolios that are too heavily weighted to one year, leaving substantial savings on the table. The right portfolio mix depends on workload elasticity. We typically rebuild to 60 percent three year reservations, 25 percent three year savings plans, and 15 percent on demand.
The security and compliance bundle
Microsoft has consolidated its security and compliance offerings into bundles that tie heavily to E5 and to specific add ons. Defender for Cloud, Defender for Identity, Defender for Endpoint, Defender for Office 365, Sentinel, Purview, and the broader compliance portfolio create a complex licensing surface.
Three patterns work. E5 universal, where E5 covers most security needs and the customer adds incremental capabilities. E3 plus add on bundle, where E3 covers productivity and a security add on bundle covers Defender, Purview, and Sentinel separately. Hybrid, with E5 for high value users and E3 plus add ons for the broader population. The right choice depends on user segmentation. We typically run a per user value calculation to find the optimum.
Microsoft audit motion
Microsoft's audit motion has shifted in the last two years to focus heavily on cloud entitlements, AHB application, and Microsoft 365 over deployment. The Microsoft SAM Engagement (now positioned as a 'license review') is less adversarial than Oracle's audit motion but produces real findings. Three risk areas deserve attention.
AHB application
Customers who apply AHB without a current SA entitlement create exposure. The fix is to reconcile AHB application against active SA licenses quarterly and to document the chain. See our Microsoft audit defense brief.
Microsoft 365 over deployment
M365 audits frequently find users licensed at lower SKU than the features they are using (M365 Apps users running Copilot, E3 users using E5 features). The fix is to map feature usage to SKU and reconcile.
Virtual Desktop Access
Azure Virtual Desktop and Windows 365 carry their own licensing rules. Customers who deploy without RDS CALs or appropriate M365 entitlement face exposure.
Renewal sequencing
Microsoft renewals are sequenced events. The customer who treats the EA renewal as a single negotiation misses the leverage in the surrounding events. We sequence renewals as a 12 month program, not a 90 day discussion.
- Twelve months out: inventory.Document every Microsoft entitlement, every consumption pattern, every SA position. Reconcile against installed base. Identify over deployment and under deployment.
- Nine months out: alternatives.Develop credible alternatives where they exist. Google Workspace, Slack, Zoom, AWS for parts of the workload, Atlassian for collaboration tools.
- Six months out: open the negotiation.Bring the inventory, the alternatives, and the proposed structure. Anchor on commitment level, term, and contract terms. Discount is a third tier lever.
- Three months out: structure decisions.Finalise EA versus MCA Enterprise. Finalise MACC level. Finalise Copilot scaling. Finalise security bundle.
- Closing: contract terms.Price hold, audit notice, AHB language, exit ramp, Copilot ramp clauses, MACC drawdown rules.
For the broader vendor renewal calendar see our 2026 vendor renewal calendar.
Contract clauses we negotiate hardest
- Price hold.Lock list prices on key SKUs for the term. Microsoft has been raising list on M365, Power Platform, and certain Azure SKUs. Lock the rate.
- AHB language.Spell out which licenses qualify and the audit reconciliation process.
- MACC drawdown.Marketplace, partner solutions, and certain PaaS services should count toward MACC consumption.
- Copilot ramp.The right to ramp Copilot deployment over the term, not commit fully on day one.
- Audit notice.60 days notice. Defined scope. Defined remediation window.
- Exit ramp.What happens to data, reserved capacity, and discounts if the customer migrates workloads off Azure or off M365.
Pattern: the EA to MCA Enterprise transition
A global manufacturer we worked with received an MCA Enterprise proposal at the next EA renewal. The proposal carried a higher headline cost than the EA renewal, with the increase justified by Copilot deployment and Azure growth. The customer accepted the framing and was preparing to sign at a 12 percent year over year increase.
The defense had four steps. We rebuilt the inventory and identified 18 percent shelfware in the M365 estate. We separated the Azure renewal from the M365 renewal, negotiating each on its own merits. We staged Copilot at 25 percent of the workforce in year one, with growth ramps tied to demonstrated value. We negotiated AHB language, MACC drawdown rules, and a price hold on M365 and key Azure SKUs. The final outcome was a 6 percent year over year reduction relative to the prior EA, with the MCA Enterprise structure in place for future flexibility.
For more renewal patterns see our case studies library.
The CFO view
From a CFO perspective the Microsoft estate now spans three commercial structures (EA, MCA Enterprise, MACC) with overlapping discount mechanics and cumulative commitment levels. The complexity creates two financial risks. First, double commitment, where the same workload is implicitly committed under both M365 SA and a MACC. Second, opacity, where the unit economics of any specific service are difficult to extract from the bundled invoice.
The CFO playbook is to demand unit economics by service, not by bundle. Track Copilot per user per month all in. Track Azure per workload all in. Track M365 per seat by SKU. Hold the executive sponsor accountable on the unit economics, not on the absolute spend. The absolute spend will grow. The unit economics should improve.
Closing thought
Microsoft is the most strategic vendor in most enterprise estates. The 2025 to 2026 model shift has made the renewal more complex, not less. The customers who treat it as routine accept Microsoft's first proposal and concede leverage they did not need to concede. The customers who treat it as a structured procurement event run the 12 month sequence, build the alternatives, separate the negotiations, and tighten the contract terms.
Redress Compliance is independent and 100 percent buyer side. We do not partner with Microsoft. We do not resell M365 or Azure. We are not an LSP or CSP. Our advisors have negotiated EA renewals, MCA Enterprise migrations, MACC commitments, and Copilot deployments across enterprises with annual Microsoft spend from 5 million to over a billion dollars. If you are facing a Microsoft renewal, an audit, or a Copilot decision, the next step is a confidential briefing.
