Full narration of the briefing. Click a section heading to jump the player to that moment.
In the high stakes world of mergers and acquisitions, Microsoft licensing is often treated as a minor line item. However, this is precisely where millions of dollars are either quietly saved or unexpectedly lost before the deal even closes. When companies merge, they do not just combine headcounts. They combine complex legal obligations that Microsoft manages with extreme precision.
Understanding the mechanics of these agreements is the difference between a smooth transition and a financial shock. We are going to walk through the five critical points you must address during the diligence phase. For each point, we will look at the mechanic, the reason it exists, a concrete example, and the specific counter move you can take. Point number one.
Assignability and consent. Most leaders assume that when they buy a company, they automatically acquire the rights to use the software that company has already paid for. In reality, Microsoft Enterprise Agreements are not freely assignable. The mechanic here is a standard clause in the Enterprise Agreement.
It states that any change of control or a carve out requires Microsoft's written consent. This is a legal requirement that overrides the general acquisition process. Microsoft treats this consent as a commercial event rather than a routine administrative task. They use this moment to review your entire licensing estate and potentially renegotiate terms that were previously settled.
Consider a scenario where Company A acquires Company B. After the deal closes, Microsoft discovers the unapproved transfer and pauses license updates or support until a new agreement is signed, often at much higher prices. The counter move is simple but timing is everything. You must raise the assignment language during the diligence phase.
Make the written consent a condition for closing and start the conversation with Microsoft before the documents are signed. Point number two. Two agreements, two anniversaries, and two price levels. After an acquisition, it is very common for the buyer and the seller to both hold their own separate Enterprise Agreements.
The mechanic is that these two agreements likely have different true up dates and different price levels based on their historical volume. Managing these in parallel creates significant administrative overhead and risk. The risk here is that consolidating these agreements too early can reset the entire estate to a worse price level. Microsoft may not allow you to carry the higher discount of the smaller company into the combined larger agreement.
For example, if the buyer is at price level D and the acquired company is at level A, a hasty consolidation might force all new purchases to the lower discount level A, increasing your costs significantly over three years. Your counter move is to model co terming against running the agreements in parallel. Do not assume consolidation is better. Wait until the next major renewal or true up to determine which path provides the best long term price protection.
Point number three. The transition services trap. This is a common operational hurdle during the period between the deal closing and the final separation of the two IT environments. The mechanic is that the licenses owned by the seller are generally tied to the seller's legal entity.
During a transition services agreement, these licenses cannot be used by the buyer's employees without explicit permission. Microsoft enforces this because the buyer is a separate legal person. Without a specific grant, using the seller's licenses constitutes a breach of the agreement, even if the seller is providing the service. Imagine the buyer's team taking over a department, but they cannot legally use the existing Office 365 environment because the contract does not cover third party users.
You might end up paying for the same seats twice. The counter move is to get an explicit, time boxed license grant written into the transaction documents. Alternatively, you must budget to fully license the buyer's staff from day one to avoid compliance gaps. Point number four.
Divestiture and committed quantities. This applies when you are selling a part of your business. Many organizations forget that Microsoft agreements are built on floors, not ceilings. The mechanic is that your committed quantities are a contractual floor.
You cannot true down or reduce your seat count in the middle of a three year term, regardless of how many employees leave the company. Microsoft bills based on the high water mark of the previous year. If you divest a division of one thousand people, those seats will still appear on your bill until the entire agreement comes up for renewal. If you sell a business unit halfway through a three year term, you may be stuck paying millions for licenses that no one is using.
This can create a significant unexpected drag on the deal's final valuation. The counter move is to negotiate a divestiture true down or a specific split of rights before the deal closes. You want the ability to reduce your commitment immediately upon the completion of the sale. Point number five.
The estate is your leverage. While M&A creates risks, it also creates the single largest opportunity to improve your standing with Microsoft. Your combined estate is now a much bigger prize. The mechanic is that a larger combined estate represents a major commitment that Microsoft desperately wants to secure.
This volume gives you the power to request concessions that would be impossible for a smaller entity. Microsoft is incentivized to see you consolidate because it simplifies their billing and locks you into their ecosystem. They will often trade significant flexibility in exchange for that long term commitment. For example, you can trade the consolidation they want for a permanent price level lock or a clean reset of your entire licensing terms.
This ensures your costs remain predictable even as your organization continues to grow. The counter move is to prepare a credible alternative. If you can show that you are willing to run the agreements in parallel or move certain workloads elsewhere, the trade for consolidation becomes a real negotiation rather than a demand. Navigating these five points requires a proactive approach.
M&A is a time of immense change, but licensing should not be one of the surprises that keeps you up at night. Proper diligence pays for itself many times over. If you take only one thing away from this briefing, let it be this. Get the assignment, the consent, and the transition license language written directly into your transaction documents before they are signed.
Addressing these technical licensing details early ensures that the value of your merger is preserved. Thank you for your time, and I hope this helps you navigate your next deal with confidence.
Redress Compliance works on contingency: our fee is 25 percent of what we save you. Nothing saved, nothing paid. Independent, buyer side only, never vendor funded.
Talk to a Microsoft negotiator