Why Microsoft Licensing Due Diligence Matters in M&A
Mergers, acquisitions, and divestitures trigger seismic shifts in software licensing obligations. When two organizations combine, duplicate Microsoft 365 tenants, overlapping Azure subscriptions, and conflicting EA terms create immediate integration headaches. Worse, hidden licensing liabilities—NCE subscriptions locked into multi-year commitments, Azure overage commitments, Copilot licensing obligations—often remain invisible until after close, when they blindside acquirers with six-figure bills.
Microsoft licensing is one of the largest controllable costs in enterprise M&A. A typical acquisition of a 500-user company with 60% Microsoft saturation can surface $200K-$500K in annual licensing optimization opportunities or, conversely, unexpected costs. Yet many deals treat Microsoft licensing as an afterthought—a line item buried in IT integration, rather than a strategic financial lever.
Redress Compliance's M&A advisory service ensures you understand the complete picture: which licenses transfer, which terminate, which create ongoing obligations, and where the optimization wins live. This transforms licensing from a post-close surprise into a pre-close bargaining chip and post-close value driver.
The Microsoft M&A Licensing Landscape: EA, MCA-E, and CSP/NCE
Microsoft's three primary commercial frameworks govern licensing rights in M&A transactions:
Enterprise Agreement (EA)
An EA is a contractual commitment between your organization and Microsoft, typically covering 3 or 4 years. Licenses under an EA cannot be unilaterally transferred between entities without Microsoft's written consent. Transfer requires completion of a License Transfer Form, submitted to Microsoft's Licensing Management Portal and signed by both the buyer and seller. Standard EA discounts range from 10-20% (down from historical 15-25%), depending on volume and commitment term.
Key M&A implications:
- If the seller maintains an active EA with true-up obligations at close, the acquirer typically assumes liability unless Microsoft releases the seller from the agreement
- License counts from the seller's EA do not automatically merge with the acquirer's EA; a Transfer Form is required
- The seller's EA term may not align with the acquirer's; staggered expiration dates complicate renewal negotiations
Microsoft Customer Agreement (MCA-E)
MCA-E is Microsoft's evergreen, month-to-month commercial agreement. Unlike an EA, MCA-E has no fixed term and no true-up. This flexibility comes at a cost: MCA-E agreements do not include Software Assurance (SA), limiting downgrade rights and access to historical versions.
Key M&A implications:
- MCA-E is more flexible for post-close integration: you can add or remove licenses monthly without consent
- However, the lack of SA can trap you in newer versions; downgrade negotiations are harder
- MCA-E discounts are typically lower than EA (5-15% range); NCE monthly pricing at list; NCE annual up to 5% off
- Transferring an MCA-E is simpler than an EA, but still requires coordination with Microsoft to reassign licenses to the acquirer's tenant
CSP / New Commerce Experience (NCE)
Some organizations purchase Microsoft licenses through Cloud Solution Providers (CSP) using the New Commerce Experience (NCE) model. NCE is subscription-based: monthly at full list price, or annual with up to 5% discount. NCE subscriptions lock in for the selected period (month or year); early termination carries penalties.
Key M&A implications:
- CSP/NCE licenses are easier to consolidate than EA (no License Transfer Form), but more expensive if locked into annual contracts
- Overlapping CSP subscriptions from acquirer and seller create redundancy; consolidation saves 20-40%
- If the seller signed annual NCE contracts, the acquirer inherits those commitments and penalties for early termination
- Post-close, many acquirers consolidate CSP subscriptions into their EA for better pricing
Navigate M&A licensing complexity with expert guidance.
Our Microsoft licensing advisory specialists conduct due diligence, identify risks, and plan integration.Pre-Close Due Diligence: What to Review
A rigorous pre-close Microsoft licensing checklist captures every agreement, subscription, and commitment that will survive or be disrupted by the transaction:
1. Agreement Inventory
- All Microsoft EAs (including staggered renewal dates)
- MCA-E agreements and pricing tiers
- CSP subscriptions and NCE annual/monthly locks
- Azure commitment contracts (MACC—Microsoft Azure Consumption Commitment)
- Vendor-managed licensing (VML) arrangements
2. License Transfer Rights
- Review each EA's license transfer clause; Microsoft's consent is required
- Document how many licenses in the seller's EA can transfer; some may be subject to true-up disputes
- Identify any restricted licenses (e.g., government pricing, academic discounts, non-profit licensing) that cannot transfer
3. Tenant Architecture
- How many Microsoft 365 tenants does the seller operate? (Common trap: 2-4 separate tenants due to acquisition history)
- Domain registrations and ownership; can domains transfer, or must they be migrated?
- Active Directory integration on-premises; will it federate with the acquirer's Azure AD, or remain separate?
4. Azure Consumption & MACC
- Total annual Azure spend and consumption trends
- Any Microsoft Azure Consumption Commitments (MACC) in place? Obligations transfer to the acquirer
- Orphaned or low-utilization resources that can be decommissioned post-close
5. Copilot & AI Licensing
- Is Microsoft Copilot ($30/user/month) currently licensed and deployed?
- How many seats? Does the seller's EA include E7 (which bundles Copilot), or is Copilot a separate line item?
- GitHub Copilot licenses; are they separate or bundled with M365?
6. Software Assurance & SA Benefits
- Which licenses include SA? (EA typically includes SA; MCA-E does not)
- Active SA benefit claims (e.g., downgrade rights, legacy version access)
- SA expiration dates and renewal terms
Common M&A Scenarios and Licensing Responses
Scenario 1: Microsoft Customer Acquires Microsoft Customer
Both organizations already run M365. Typical trap: duplicate domains, overlapping O365 licensing, conflicting EAs or MCA-E agreements.
Response: Plan a 90-day mailbox migration into the acquirer's primary tenant. Close down the seller's tenant post-migration. Consolidate Azure subscriptions into the acquirer's EA. Document which licenses transfer via License Transfer Form (EA) or reassign via MCA-E. Typical savings: 25-35% through elimination of duplicate licenses.
Scenario 2: Microsoft Customer Acquires Non-Microsoft Company
The seller has no Microsoft infrastructure; all users need M365 E3/E5 after acquisition. Trap: purchasing 500 new seats of E5 when many could run on E3, or overlooking Windows Server licensing on the seller's infrastructure.
Response: Conduct a user-level audit: which roles genuinely need E5 advanced security features? Typically, 60-70% of users can operate on E3, saving $30-50/user/year. Inventory all on-premises servers; many may need Windows Server and SQL Server licensing transfers. Copilot is a post-acquisition optimization: pilot with 50-100 power users before broad rollout.
Scenario 3: Non-Microsoft Organization Acquires Microsoft Customer
The acquirer uses Google Workspace or another cloud platform; the seller is entrenched in Microsoft. Trap: supporting two parallel cloud stacks during integration, license conflicts, and stranded investment in the seller's Microsoft infrastructure.
Response: Decide early: migrate the seller to the acquirer's cloud platform (costly, time-consuming, risky) or maintain the seller's Microsoft stack as a federated environment. If federated, document the seller's EA and negotiate whether the acquirer assumes it or the seller spins it off. Typically, federated setups last 18-36 months during integration, then consolidate to the parent platform.
Scenario 4: Divestiture or Spin-Off
A division of your organization becomes independent and must establish its own Microsoft licensing. Trap: the division was licensed under your EA and has no independent agreement; it also lacks its own Azure subscription and Intune infrastructure.
Response: Establish a new MCA-E or EA for the spin-off entity pre-close. Migrate users from the parent's tenant to the spin-off's tenant. Create separate Azure subscriptions and Intune policies. Negotiate with Microsoft to release the spin-off from the parent's true-up liability. Typical timeline: 60-90 days pre-close to establish clean infrastructure.
License Transfer Rules: EA vs MCA-E
EA Transfers
Transferring licenses under an EA requires Microsoft's written approval via the License Transfer Form. Here's the process:
- The seller (current EA holder) initiates the License Transfer Form in the Microsoft Licensing Management Portal
- The form specifies: which licenses transfer, the acquirer's organization, the effective date
- Microsoft reviews and approves; this typically takes 10-14 days
- The acquirer assumes those licenses under its own EA, or a new EA is established
- The seller's true-up liability (if any) is typically resolved at the time of transfer
Important: Not all licenses may be eligible to transfer. Government pricing, academic discounts, and non-profit licensing have restricted transfer terms. Verify transferability with Microsoft before close.
MCA-E Transfers
MCA-E is more flexible. Licenses can be reassigned or consolidated more quickly, typically within 5-7 days. However, MCA-E lacks Software Assurance, so downgrade rights are limited. Pricing is also typically higher than EA.
Azure Committed Spend (MACC) in M&A
Azure Consumption Commitments (MACC) obligate the customer to spend a minimum amount monthly or annually on Azure. If the seller has an active MACC (e.g., $100K/year commitment), the acquirer typically inherits this obligation post-close.
Key considerations:
- Benefit Recognition: If the seller's Azure consumption exceeds the MACC, the acquirer can benefit from the commitment (lower effective hourly rate). If consumption falls short, the acquirer pays the difference.
- Post-Close Consolidation: The acquirer may consolidate the seller's Azure consumption into its own subscription and MACC, potentially reducing the effective commitment cost
- Decommissioning: Identifying and shutting down unused Azure resources in the seller's subscription can reduce ongoing commitment liability
- Renegotiation: If the combined acquirer + seller Azure consumption is higher than either party's current MACC, you may have leverage to negotiate a higher commitment at better pricing
Post-Close Integration: The 90-Day Plan
Microsoft licensing integration typically follows a 90-day stabilization window post-close:
Days 1-30: Freeze & Inventory
- Establish a single source of truth for all Microsoft license positions (EA, MCA-E, Azure, CSP)
- Do not make any licensing changes or new purchases without approval
- Identify which licenses are transferring, which are being consolidated, which are being retired
- Create new Azure subscriptions and Intune environments for the seller's users (if tenant consolidation is planned)
Days 31-60: Migration & Consolidation
- Begin mailbox migrations from the seller's tenant to the acquirer's (if consolidating)
- Migrate Azure resources and consolidate subscriptions
- Consolidate CSP subscriptions into the acquirer's EA
- Finalize License Transfer Forms and submit to Microsoft
- Decommission unused Azure resources and orphaned licenses
Days 61-90: Optimization & Handoff
- Complete all tenant and infrastructure migrations
- Validate that license counts match headcount; audit for excess licenses
- Negotiate any remaining MACC or EA adjustments with Microsoft
- Finalize the "as-built" Microsoft licensing position for renewal planning
- Hand off to the combined organization's IT and procurement teams
M&A Licensing Due Diligence Checklist
Download our comprehensive checklist to audit Microsoft licensing in any M&A transaction. Covers EA/MCA-E assessment, tenant architecture, Azure commitments, Copilot licensing, and 90-day integration planning.
Common Traps That Cost Acquirers Millions
Trap 1: Overlooking NCE Annual Contracts
The seller signed 200 seats of M365 E3 on an annual NCE contract at full list price. Upon acquisition, the acquirer discovers these licenses are locked until renewal, and early termination incurs a 50% penalty. Result: $120K in sunk costs for 12 months. Prevention: audit all CSP/NCE subscriptions for contract lock-in and termination penalties.
Trap 2: Failing to Close Seller's Tenant
Post-acquisition, the acquirer migrates all users from the seller's M365 tenant to its own, but fails to deactivate the seller's tenant. For 18 months, both tenants remain active, and the seller's EA continues to incur true-up. Result: $50K in unnecessary licensing spend. Prevention: set a 90-day hard deadline for tenant decommissioning and track EA true-up reconciliation.
Trap 3: Underestimating Azure Overage Costs
The seller has a $50K annual Azure MACC but consumes $80K. The acquirer assumes the $50K commitment but discovers the seller owes $30K in overage charges at close. Additionally, the seller's Azure subscription contains dormant dev/test environments costing $5K/month. Result: $100K+ in unexpected costs. Prevention: audit Azure consumption 60 days before close and identify decommissioning targets.
Trap 4: Copilot Licensing Surprise
The seller's EA includes 100 seats of M365 E5 (which includes Copilot at no extra charge), but the seller also purchased 50 standalone Copilot licenses at $30/user/month separately. Upon acquisition, the acquirer realizes 50 Copilot licenses are redundant. Result: $18K/year in wasted spend. Prevention: cross-reference all Copilot licenses against E5/E7 SKU inventory.
Trap 5: Inadequate Due Diligence on Government / Academic Pricing
The seller holds licenses under government or non-profit pricing that cannot transfer to the acquirer. Upon close, these licenses must be cancelled and repurchased at commercial rates, increasing cost by 30-40%. Result: $200K+ in additional licensing expense. Prevention: verify transferability of all licenses with Microsoft pre-close.
How Redress Compliance Can Help
Redress Compliance's Microsoft M&A advisory service covers the entire lifecycle:
- Pre-Close Due Diligence: We audit the seller's or acquirer's Microsoft licensing posture, identify hidden costs, assess EA/MCA-E terms, and flag transfer risks
- License Transfer Planning: We manage the License Transfer Form process, coordinate with Microsoft, and ensure clean transitions
- Integration Planning: We design the 90-day post-close roadmap: tenant consolidation, Azure migration, CSP optimization
- Negotiation Support: Our Microsoft EA negotiation specialists can support price negotiations on combined EA terms or MACC consolidation
- Post-Close Optimization: We help identify optimization opportunities: unlicensed users, excess E5 seats, orphaned Azure resources, shelfware
On average, our M&A advisory engagements identify $150K-$500K in cost avoidance or optimization per transaction. We've guided 50+ Microsoft-intensive M&A deals from due diligence through integration.
Conclusion: Get Licensing Right in M&A
Microsoft licensing due diligence is not optional in M&A. It's a financial control lever that transforms licensing from a post-close liability into a pre-close and post-close value driver. Organizations that conduct rigorous pre-close licensing reviews and execute disciplined 90-day integration plans realize 20-35% savings and avoid eight-figure integration disasters.
Ready to navigate Microsoft licensing in your next M&A transaction? Our Microsoft EA advisory specialists can guide you from due diligence through close and integration. Get in touch to discuss your transaction.