Podcast Summary: Moving From EA to MCA? Watch Out for These Gotchas

The Directions on Microsoft Briefing Podcast – December 16, 2025
Host: Mary Jo Foley (Editor in Chief, Directions on Microsoft)
Guest: Dean Bedwell (Microsoft Licensing Expert and Negotiator)

Main Theme

This episode provides an in-depth comparison between Microsoft’s traditional Enterprise Agreement (EA) and the newer Microsoft Customer Agreement (MCA), focusing on the key differences, potential pitfalls (“gotchas”), and important legal and negotiation strategies for enterprise customers. Host Mary Jo Foley interviews Dean Bedwell, who draws on extensive experience working both at Microsoft and as a licensing consultant, to help organizations navigate the transition from EA to MCA.

Key Discussion Points and Insights

1. How MCA Differs Structurally from EA

• EA Contract Stack is multi-layered:
  • Includes MBSA (Microsoft Business and Services Agreement), old MBA (if legacy), enrollments, product selection, program signature, amendments, and various referenced documents (Product Terms, Service Level Agreements, Data Protection Addenda, etc.).
  • Typically exceeds 30 pages – “not including price sheets or amendments.”
    (02:01–03:20)
• MCA:
  • Streamlined and modernized; only 10 pages, digital and “evergreen” (does not require regular resigning).
  • Modular: Only the relevant terms for services used must be accepted.
  • Automatic updating as new services are added.
  • Single, unified management in Azure Portal/M365 Admin Center.
  • Lower barrier: No minimum purchase requirements; supports direct, partner-led, and self-service procurement. (03:40–05:10)

2. Microsoft’s Position on MCA Advantages

• Digital, evergreen, and modular
• Streamlined purchasing, billing, and unified management
• No minimum purchase requirements

“Customers only need to accept terms relevant to the services they use. So as new products are added, the agreement updates automatically.”
—Dean Bedwell (03:14)

3. The “Gotchas” – MCA Pitfalls and Customer Risks

Dean Bedwell shares an extensive list of issues that enterprises must scrutinize before moving to MCA.
(05:42–10:00)

• No Standard Term Length:
  • MCA has no fixed term (EA is 3 years); leads to “various end dates for the exact same product,” complicating budget planning.
• Loss of Key Products & Discounts:
  • “Software Assurance” offerings and “from SA” SKUs (used for discounted upgrades from perpetual licenses) may be missing, leading to loss of eligibility and significant price increases.
• No Price Levels:
  • Tiered volume discounts (“price levels”) were retired (as of Nov 1, 2025), causing up to 12% or more price hikes.
• No True-Up Mechanism:
  • Unlike EA, MCA customers must renegotiate for each add, losing batch economies.
• Harder to Negotiate Concessions:
  • Fewer levers to bargain with Microsoft.
• MCA Supersedes All Other Contracts:
  • Even if you adopted MCA for a single service, it becomes your master agreement.
• Draconian License Verification:
  • Backdating is allowed; Microsoft can impose penalties retroactively if non-compliance is found (removal of previous audit protection provisions).
• Legal and Process Changes:
  • Order of contract precedence has shifted (e.g., Data Protection Addendum now primary).
  • Data Protection Addendum and other referenced documents updated regularly, often favoring Microsoft.
  • Billing changes (auto-billing), cancellation fees, warranty updates.
  • Use rights and applicable law state defaulted to Washington.
  • Companies must engage legal teams for review and negotiation.

“The one-year moratorium for audit has been removed…They could apply retroactively not just moving forward.”
—Dean Bedwell (08:40)

4. Increased Costs: Loss of “From SA” Discount & Price Leveling

(12:22–13:35)

• “From SA” SKUs previously gave a 15% discount for customers moving from Software Assurance to full cloud subscriptions—now gone in MCA, leading to a “17% increase” for the same products.
• Combined with loss of volume price levels, organizations may face significant, immediate price hikes.

“You’ll be buying a full user subscription license, which…is actually a 17% increase in the cost that you’re going to pay.”
—Dean Bedwell (12:52)

5. Draconian License Verification

(13:35–15:24)

• Retrospective (“backdating”) penalties will now apply if non-compliance is found, versus the forward-only method in EAs.
• Example: Over-allocating Windows Server could cost 125% penalty for all months since non-compliant usage, not just discovery month.

“Now Microsoft not only will charge you the 125% penalty for that difference, but they can backdate it to as long as it’s been in existence…Ouch.”
—Dean Bedwell (14:24)

6. Legal Considerations and Negotiation Complexity

(15:47–17:50)

• Legal terms (warranties, liabilities) are negotiated alongside business and financial terms—nothing stands alone.
• Changes in legal language (including limitation of liability) can directly impact discount levels.
• Calls for a robust legal review and comprehensive negotiation strategy.

“First step is get legal to review your MCA and then build a negotiation outline…have your lawyers review that legal part.”
—Dean Bedwell (17:30)

7. Difficulty in Negotiation and Reduced Concessions

(18:04–19:23)

• Concessions (“exceptions to standard terms or pricing”) will be harder to get.
• Small customers on MCA via Cloud Solution Providers may have little-to-no room to negotiate.
• Direct-buyers—unless very large—will see “take it or leave it” offers; less human account management, more AI assistance.
• Microsoft’s goal: Standard contracts, think of it as “Microsoft software as a utility.”

“If this was a text this would all be in capitals and bolded. Absolutely. Yes.”
—Dean Bedwell (18:04)

“It may be a take it or leave it negotiation…like a hydro bill monthly. But you don’t negotiate your rate, you just pay.”
—Dean Bedwell (18:12)

Notable Quotes & Memorable Moments

• On what to do about the new reality:

  “Preparation for renewal is paramount…By failing to prepare, you’re preparing to fail.”
  —Dean Bedwell (19:29)

Key Timestamps for Important Segments

• Overview of EA vs. MCA structure: 02:01–03:40
• Potential Advantages of MCA (per Microsoft): 03:52–05:12
• List of “gotchas” and contract risks: 05:42–10:00
• Impact of loss of “from SA” SKU/discounts: 12:22–13:35
• License verification and backdating penalties: 13:35–15:24
• Negotiating legal/business changes: 15:47–17:50
• Difficulty in securing concessions: 18:04–19:23
• Final strategy advice: 19:29–20:14

Final Advice and Takeaways

• Preparation is Key:
  Enterprises must carefully prepare for renewals, involve legal counsel, and coordinate business, legal, and financial requests before negotiating with Microsoft.
• Expect Fewer Concessions:
  The move to an MCA-centric world means less flexibility, fewer discounts, more standardized terms, and greater risk in compliance or legal missteps.
• Negotiation Requires Holistic Approach:
  Interrelated legal and financial terms require all teams aligned ahead of time.

Useful For:

• IT procurement specialists, legal teams, and anyone responsible for Microsoft enterprise licensing/contract renewals.
• Organizations planning to move, or being moved, from EA to MCA.

For more coverage and tools, visit Directions on Microsoft.