Background
The client is a French professional services firm headquartered in Paris, with approximately 800 employees distributed across offices in France and Belgium. The firm provides consulting and auditing services to mid-market and large enterprise clients across multiple industries. As a professional services firm, the workforce is almost entirely composed of knowledge workers — consultants, auditors, analysts, and support staff — whose daily productivity depends on Microsoft 365 (email, Office applications, Teams for collaboration), and to a lesser extent on Azure for hosting a small number of internal applications and test environments.
The firm's Microsoft licensing history followed a typical mid-market trajectory. It had started with a Microsoft Products and Services Agreement (MPSA) for ad hoc purchases, then graduated to a Microsoft Enterprise Agreement (EA) when the user count crossed the 500-seat threshold. The EA had provided the firm with volume discounts, predictable annual payments, and a structured three-year contract cycle. With the current EA term ending, the firm faced a strategic decision: renew the EA for another three-year cycle, or adopt the Microsoft Customer Agreement (MCA) — Microsoft's newer, evergreen contract model designed to replace the EA for many customers, particularly in the mid-market.
Microsoft France was actively encouraging the firm to transition to the MCA, positioning it as more modern, flexible, and better suited to a mid-sized professional services firm that did not need the complexity of a full Enterprise Agreement. The firm's IT Director and procurement team were intrigued by the potential flexibility — no fixed three-year term, the ability to scale licences up or down monthly, and simplified administration — but they were cautious. Transitioning from a familiar contract structure to an unfamiliar one carried risks: potential loss of negotiated discounts, unpredictable cost fluctuations, and compliance gaps during the switch. They engaged Redress Compliance to perform a rigorous cost-benefit analysis, lead the transition negotiation, and ensure the move delivered genuine savings and flexibility rather than merely benefiting Microsoft.
The Challenges
EA vs. MCA Uncertainty
The MCA was relatively new territory. While Microsoft promoted it as simplified and flexible, the firm worried that abandoning the EA framework would mean losing volume discounts and fixed pricing. Microsoft's initial MCA pricing was higher per unit than the firm's EA rates — a gap that, if not addressed, would make the transition a cost increase rather than a saving.
Budget Predictability Concerns
Under the EA, the firm had predictable annual payments that finance could plan around. The MCA's consumption-driven model for cloud services could create monthly billing fluctuations — particularly concerning for Azure usage, which could spike during project peaks. The finance team needed mechanisms to keep costs predictable while gaining the MCA's flexibility.
Upsell Pressure During Transition
Microsoft used the transition as an opportunity to push Microsoft 365 E5 and expanded Azure adoption. The firm historically needed only E3 for most employees and had minimal Azure usage. There was a real risk of being oversold cloud services during the contract change — buying more than the firm needed under the guise of modernisation.
Benefit Carryover and Compliance
The existing EA included training vouchers, support benefits, and specific licensing entitlements. It was unclear whether these would carry over to the MCA or be lost in the transition. Additionally, the firm needed a careful licence-by-licence mapping to ensure no compliance gaps or service interruptions during the contract switch.
The fundamental tension was between flexibility and financial risk. The EA offered predictability and volume discounts but locked the firm into a rigid three-year cycle. The MCA offered agility and evergreen terms but, without negotiation, would come at higher per-unit pricing and unpredictable costs. The firm needed an adviser who understood both models deeply — and who could negotiate the MCA terms to deliver the financial benefits of the EA with the operational flexibility of the new model. This was precisely the role Redress Compliance was engaged to fill.
How Redress Compliance Helped
MCA vs. EA Cost-Benefit Analysis
Redress performed a comprehensive component-by-component comparison of renewing the EA versus transitioning to the MCA. The analysis covered every element: M365 user licences (800 seats), Azure consumption (a few virtual machines and test environments), support entitlements, and ancillary benefits. At standard MCA list pricing, the transition would have been more expensive than the EA — the MCA does not automatically include the volume discounting that EA negotiations typically yield. However, Redress identified that Microsoft France was offering incentives for early MCA adoption: the firm's EA-level per-user pricing could be maintained for a specified period, and Microsoft was prepared to provide a one-time Azure credit to facilitate the transition. Redress modelled scenarios showing that, with targeted negotiation, the firm could achieve 15–20% savings in year one under the MCA compared to the EA — combining discount carryovers, licence optimisation, and Azure cost management. This analysis gave the IT Director and CFO the confidence that the MCA could deliver genuine financial benefits, not just vendor-friendly flexibility.
Negotiating EA-Equivalent Terms Within the MCA
Redress led the negotiation with Microsoft France to secure MCA terms that matched or exceeded the EA's financial protections. The critical win was securing "EA-equivalent" pricing on Microsoft 365 licences: Microsoft agreed to lock the firm's per-user pricing at the same rate they had under the EA for a two-year period — effectively providing EA-level volume discounts within the MCA's evergreen framework. This meant the firm gained the MCA's operational flexibility (no three-year lock-in, ability to scale licences monthly) without paying the premium that MCA list pricing would normally impose. Redress also negotiated quarterly cost review meetings with the Microsoft account team — a governance mechanism where Microsoft would proactively monitor the firm's spend, flag any Azure consumption trending above forecasts, and help the finance team maintain budget predictability. Additionally, Redress secured an explicit contractual right to scale down services without penalty — if the firm deployed Azure licences for a project and the project concluded, those licences could be removed immediately with the monthly bill adjusting accordingly. While scale-down is inherently possible in the MCA model, putting it in writing provided the procurement team with documented assurance.
Licence Mix Optimisation and Azure Cost Management
Alongside the contract restructure, Redress optimised the firm's purchasing decisions to maximise savings from day one. For M365, Redress recommended maintaining E3 for the vast majority of users and leveraging the MCA's à la carte flexibility to purchase targeted E5 Security add-on packs for a team of approximately 50 security-sensitive users (security analysts, IT administrators, compliance officers). The E5 Security add-on — which provides Defender for Endpoint, Azure AD Premium P2, and advanced compliance tools — costs significantly less than a full E5 licence, yet delivers exactly the advanced security features these users needed. This approach avoided the blanket E5 upsell Microsoft had proposed while ensuring the security team had enterprise-grade protection. For Azure, Redress cleaned up idle resources before the transition (stopped VMs, orphaned storage, unused IP addresses) to ensure the firm did not carry waste into the new billing model. For always-on workloads (the firm's core internal applications), Redress implemented Azure Reserved Instances — committing to one-year reservations at approximately 20% below pay-as-you-go rates. The Azure credit Microsoft provided as part of the MCA transition incentive was applied strategically to offset the initial Reserved Instance purchases. These optimisations ensured that, from the moment the MCA went live, the firm was running a leaner, more cost-effective Microsoft estate.
Smooth Transition, Support Carryover, and Team Enablement
Redress oversaw the end-to-end transition to ensure no service interruption, compliance gap, or benefit loss. Every existing licence was documented and re-provisioned under the MCA tenant with zero downtime. For support benefits, Redress negotiated a solution: Microsoft agreed to provide the firm with an equivalent Premier Support package for one year at no additional charge, preserving the support hours and priority access the firm had enjoyed under the EA. This prevented the loss of a valuable benefit that the firm's IT team relied upon for critical issue resolution. Redress also provided hands-on training for the firm's IT and procurement teams on the Microsoft Commerce Portal — the self-service interface used to add, remove, and manage licences under the MCA. This empowerment was strategically important: the MCA's flexibility is only valuable if the customer's team knows how to use it. By the time the MCA went live, the firm's IT asset manager could add licences for new hires, remove them for departures, and track consumption in real time — eliminating the annual true-up exercise that had been a recurring administrative burden under the EA. Redress remained engaged for several months post-transition, verifying that invoices matched expectations and resolving any billing discrepancies in the quarterly cost review meetings.
Outcome and Impact
| Metric | Under Previous EA | Under MCA (Year One) |
|---|---|---|
| Total Microsoft annual cost | 100% (baseline) | 82% — 18% reduction achieved |
| M365 per-user pricing | EA volume discount rate | Same rate locked for 2 years under MCA |
| Security licensing | Microsoft proposed blanket E5 for all 800 users | E3 + E5 Security add-on for ~50 users — fraction of cost |
| Azure cost management | Pay-as-you-go; some idle resources | Reserved Instances (~20% saving); idle resources cleaned up |
| Contract flexibility | 3-year fixed term; annual true-up | Evergreen; monthly scale up/down; no true-up |
| Premier Support | Included in EA at negotiated rate | One year free; equivalent terms preserved |
| Administrative overhead | Annual true-up process; renewal negotiations every 3 years | Real-time portal management; quarterly cost reviews; no renewal pressure |
The 18% cost reduction in year one exceeded the initial 15–20% target range. The savings came from three sources: the licence mix optimisation (E3 base with targeted E5 Security add-ons instead of blanket E5), the Azure improvements (Reserved Instances and resource cleanup), and the negotiated EA-equivalent pricing that prevented the cost premium the MCA would normally impose. For an 800-person firm, the savings translated into tens of thousands of euros that were redirected to other IT investments — the firm used a portion to pilot a new project management platform that had been deprioritised due to budget constraints.
The flexibility gained proved its value almost immediately. When the firm experienced a slowdown in one practice area and reduced headcount by approximately 5%, the monthly Microsoft bill shrank correspondingly — under the old EA, those licences would have remained paid until the term expired. Conversely, when the firm staffed a short-term project with contract consultants, it provisioned temporary M365 licences for several months and then removed them when the engagement concluded, paying only for the months of actual usage. This pay-for-what-you-use agility was a fundamental improvement over the EA's rigid annual commitment model.
The budget predictability concern was resolved through the combination of locked per-user pricing (eliminating month-to-month rate fluctuations), Azure Reserved Instances (converting variable cloud costs into predictable commitments), and the quarterly cost review meetings with Microsoft (providing an early-warning mechanism for any consumption drift). The finance team gained both flexibility and predictability — a combination that had seemed mutually exclusive before the engagement.
The administrative simplification was an unexpected but welcome benefit. Eliminating the annual true-up exercise — where the firm had previously spent weeks reconciling licence counts and negotiating with Microsoft over discrepancies — freed the IT asset manager to focus on optimising usage rather than contractual administration. The Commerce Portal provided real-time visibility into licence assignments and costs, and any adjustments (adding a new hire, removing a departing employee) were reflected on the next monthly invoice, pro-rated automatically.
"Switching to Microsoft's new agreement felt like a leap into the unknown — but Redress Compliance was our safety net and guide. We ended up saving about 18% compared to our old deal, which is fantastic for our firm, and we gained a level of flexibility we never had before. Now, we're not locked into anything — we can dial our Microsoft services up or down as needed. Redress made sure we didn't lose our volume discounts in the process, which was key. Managing our Microsoft licences has gone from a yearly headache to a non-issue. We see what we use, we pay for what we use — no more surprise true-up bills or arguing over renewal quotes." — IT Director, French Professional Services Firm
Key Lessons for Mid-Market Organisations Considering EA-to-MCA Transition
🎯 EA-to-MCA Transition Takeaways
- Do not accept MCA list pricing without negotiation: The MCA does not automatically include EA-level volume discounts. If you transition at standard MCA rates, you will likely pay more than under your current EA. Negotiate EA-equivalent pricing lock-ins for a defined period as a condition of the transition — Microsoft is often willing to offer this to secure early MCA adopters.
- Use the transition to optimise your licence mix: Moving from EA to MCA is a natural opportunity to right-size. Replace blanket E5 deployments with E3 base licences plus targeted add-on packs (E5 Security, E5 Compliance) for users who genuinely need advanced features. The MCA's à la carte flexibility makes this approach structurally easier than under an EA.
- Clean up Azure before transitioning billing: Eliminate idle resources, right-size over-provisioned VMs, and implement Reserved Instances for always-on workloads before moving to MCA billing. Every euro of waste you carry into the new model will continue to drain budget. Start with a clean baseline.
- Negotiate quarterly cost governance: The MCA's consumption-driven model can create budget unpredictability, especially for Azure. Negotiate quarterly cost review meetings with Microsoft as part of the agreement — a governance mechanism where the account team proactively monitors spend and alerts you to consumption trends before they become surprises.
- Secure Premier Support carryover: EA contracts often include support benefits (Premier or Unified Support hours, training vouchers). These do not automatically transfer to the MCA. Negotiate explicit carryover or an equivalent support package at no additional cost as part of the transition terms.
- Map every licence before the switch: Perform a licence-by-licence inventory and re-provisioning plan before the MCA goes live. Any licence missed in the mapping creates a compliance gap or service interruption. Treat the transition as a mini-migration with formal documentation and testing.
- Train your team on the Commerce Portal: The MCA's flexibility is only valuable if your IT and procurement teams know how to use the self-service management tools. Invest in hands-on training on the Microsoft Commerce Portal — adding/removing licences, tracking consumption, managing billing — so your team can operate autonomously in the new model.
- Engage independent advisers for the transition: Microsoft is incentivised to move customers to MCA because it simplifies their own operations. Independent advisers ensure the transition benefits the customer, not just the vendor — by negotiating pricing parity, optimising the licence mix, securing benefit carryovers, and providing oversight during the switch.