Home/Audit Defense/Audit After Divestiture
Audit and Compliance

When the audit follows the divestiture.

Divestitures, spinoffs, and carve outs create license exposure on both sides of the transaction. The parent retains entitlements sized for the combined enterprise that may no longer match the consolidated estate after the carve out. The divested entity inherits license obligations that may not transfer cleanly under the original agreements. Microsoft commercial leadership watches public divestiture announcements with the same diligence as acquisitions and the follow on audit notice can arrive on either side, often inside the twelve months following close. The buyer side defense begins before the deal closes, with structured separation analysis that maps the entitlement split and the post close obligations on both sides, and across the practice this pre close discipline has been load bearing in the 79% average audit exposure reduction.

Contact Us See the full audit defense practice →
The situation

Divestiture creates two sided exposure.

A divestiture creates exposure on both sides of the transaction simultaneously. The parent retains its EA with entitlements that may now overstate the consolidated estate. The divested entity needs Microsoft entitlements that may or may not have been negotiated as part of the deal terms. Transition services agreements often extend Microsoft access to the divested entity for a defined period, creating a transitional licensing posture that can either be carefully structured or quietly non compliant depending on how the deal was papered.

Two sided exposure · 01
Both parties at risk

Where the exposure lands on each side

Exposure can land on either or both sides of the transaction. The parent typically faces overpayment risk where its existing entitlements no longer match consolidated demand and Microsoft is unwilling to true down or restructure mid term. The divested entity typically faces under licensing risk where transferred entitlements do not cover the standalone operating model or where transition services agreement coverage expires before the new entity has stood up its own contracts.

  • Parent overpayment. Existing entitlements oversize the consolidated estate.
  • Parent true down resistance. Microsoft typically rejects mid term true down requests.
  • Divested under licensing. Standalone entity carries entitlements that do not cover its full estate.
  • TSA expiration. Transition services coverage ends before new entity contracts are in place.
  • Affiliate scope shrinkage. Acquired entities now outside parent's affiliate definition.
Why this matters · 02
Both sides targeted

Microsoft tracks both sides

Microsoft commercial leadership tracks both sides of a divestiture. The parent is typically a continuing customer with an active commercial relationship and is read as a renewal candidate where the contracted entitlements no longer match consumed demand. The divested entity is read as a new account opportunity where the existing license posture is uncertain. Audit notices can arrive on either side and are materially more likely than baseline in the year following close.

  • Parent path. Existing relationship read as renewal lever.
  • Divested path. New account opportunity with uncertain license posture.
  • Targeting window. Twelve months following close is elevated probability.
  • Joint vulnerability. Both sides should run independent post close scans.
The mechanic

How the entitlements actually split.

License entitlements do not split automatically with a divestiture. The split is governed by the deal terms, by Microsoft's consent under change of control or assignment provisions, and by whatever new agreement structures are stood up for the divested entity. Reading the mechanic carefully is what allows both sides to operate cleanly across the transition.

Mechanic 01

Deal terms and license split

The divestiture purchase agreement typically addresses license treatment in a schedule. Software licenses transferred to the divested entity, licenses retained by the parent, licenses subject to transition services agreement coverage. Reading the schedule carefully is the starting point. Schedules that were drafted without Microsoft consultation can carry assumptions that Microsoft will not honor. The practice reads the schedule in detail before the buyer side accepts any post close commercial position.

Mechanic 02

Microsoft consent

Most Microsoft volume licensing agreements require Microsoft consent for license assignment to a non affiliate. Where the divestiture transfers entitlements to an entity that will not be an affiliate of the parent post close, Microsoft consent is typically required and is often granted only under a new contracting structure for the divested entity. Reading the assignment language and engaging Microsoft commercial early in the process produces the cleanest outcome.

Mechanic 03

TSA coverage

Transition services agreements often extend the parent's Microsoft entitlements to cover the divested entity for a defined transition window. The coverage requires structuring that respects Microsoft's licensing terms on affiliated use. Where the TSA structure was not vetted against Microsoft terms, post close use can constitute unlicensed access. The practice reviews TSA structure as a standard step in the divestiture license analysis.

Parent true down

Why the parent rarely shrinks

Microsoft typically resists mid term true down requests. The parent's EA was negotiated for a defined commitment level and the contract is generally read as binding on that commitment regardless of subsequent estate changes. The buyer side path to true down is not mid term contract modification but renewal restructuring. The next renewal is the moment to size the parent's commitment against the post divestiture consolidated estate. Reading the renewal opportunity early supports the structuring path.

Divested entity standup

Standing up the new entity

The divested entity needs to stand up its own Microsoft contracts inside the transition services window. The structure depends on the entity's size, intended product mix, and forward growth trajectory. A standalone EA, an MCA E commercial structure, or a CSP arrangement are the standard paths. The practice supports new entity standup as part of the divestiture engagement and the standup positioning correlates with both audit exposure and renewal leverage across the multi year horizon. See the related EA renewal framework for the new entity's first cycle.

The defense posture

Pre close planning, post close execution.

The defense posture begins before the deal closes. Pre close planning produces the entitlement split schedule, the TSA structure, the Microsoft consent strategy, and the new entity standup plan. Post close execution carries each through to formal completion. Where the pre close planning is rigorous, the post close exposure picture is materially smaller and more manageable on both sides of the transaction.

Posture 01
Pre close

Plan before the deal closes

Pre close planning includes detailed entitlement mapping, change of control and assignment reads on every active Microsoft agreement, TSA structuring against licensing terms, Microsoft commercial engagement where consent is required, and standup planning for the divested entity. Each workstream feeds into the deal documents. Pre close work produces a deal that closes cleanly from a Microsoft licensing perspective.

Pre close engagement with Microsoft commercial is sensitive. The customer is not yet ready to disclose all deal terms. The practice manages the engagement at a level that secures the necessary consents without prematurely disclosing commercial intent. The framing is structured around contractual requirements rather than commercial preview.

Posture 02
Post close

Execute the transition cleanly

Post close execution carries the pre close planning through to formal completion. New entity contracts are signed. Transferred entitlements are documented. TSA coverage is monitored against its expiration window. Parent commitment is sized for renewal restructuring. Each workstream has defined ownership and defined completion criteria.

Where an audit notice arrives during the post close window, the existing pre close documentation becomes the buyer side opening evidence. The investment in pre close rigor pays out compounded if a formal compliance review opens, because the analytical work is already complete. See the full audit defense practice framework for the engagement structure.

What we do

Divestiture license engagement.

The practice runs a structured divestiture license engagement spanning pre close planning and post close execution. The engagement covers both sides where the same client is involved or runs as a single sided engagement where only the parent or only the divested entity is the client.

Engagement format · divestiture license
Pre and post close

A workstream that spans the transition

The engagement runs from deal announcement through the transition services agreement window and into the divested entity's first renewal cycle. Both sides are managed independently where the same client is involved, with distinct working teams and distinct deliverables, integrated only at the senior partner level.

  • Entitlement mapping. Pre close split documented at metric level.
  • Change of control read. Assignment and consent requirements per agreement.
  • TSA structuring. Transition coverage vetted against Microsoft licensing terms.
  • Microsoft consent. Pre close engagement structured around contractual requirements.
  • Parent renewal sizing. Post divestiture commitment sized for renewal restructuring.
  • Divested entity standup. New contract structure selected and stood up inside TSA window.
  • Audit readiness. Documentation maintained as the defense baseline for any notice.
Common questions

Questions on post divestiture.

Three questions that recur in divestiture license situations.

Question 01

Can the parent true down at renewal

Often yes. Renewal is the natural moment to size the parent's commitment against the post divestiture consolidated estate. Microsoft accommodates true down at renewal more readily than mid term. The structuring depends on the size of the reduction, the parent's other commitments, and the broader account commercial picture. The practice runs the renewal restructuring as a connected workstream.

Question 02

What if the TSA window expires before the new entity is contracted

The exposure is real and immediate. The divested entity is operating without contracted entitlements, which is a compliance gap. The practice prioritizes new entity contract standup against TSA window expiration as a critical path item. Where the timing slips, the gap is documented and remediation is structured through whatever contracting path closes most quickly, typically CSP for short term coverage with later transition to EA or MCA E.

Question 03

Do both sides need separate advisors

Often yes, particularly where the transaction is large or the entities will compete commercially post close. Even where the same advisory firm supports both sides through deal close, separate working teams and separate deliverables are necessary to preserve confidentiality and analytical independence. Post close, the two entities typically engage separately as distinct customers with distinct strategic interests.

Divestiture license playbook

Both sides of the transition, planned.

Entitlement split, change of control, TSA structuring, parent renewal, divested standup. The structured divestiture license engagement framework the practice runs across the transition.

Engage the practice

The transition needs both sides read.

Two analyst calls. We read the divestiture license picture on both sides and recommend the pre close and post close work plan that closes the transition cleanly. Full audit defense practice.

Contact Us 79% average exposure reduction · 340+ engagements