Why Affiliate Coverage Creates Both Risk and Opportunity
Enterprise Agreements are signed by a single legal entity but are designed to extend coverage across corporate groups. The mechanism is the "Affiliate" definition — which determines which subsidiaries, holding companies, and related entities can use software licenced under the EA without separate agreements.
Most organisations assume their EA covers "all of the group." In practice, the EA Affiliate definition has specific thresholds, exclusions, and mechanics that mean coverage is narrower than assumed. The gap between what organisations believe is covered and what the EA actually covers is a leading source of compliance exposure in Microsoft audits — and a negotiating opportunity if you understand the structure before the audit team does.
The same definition also creates opportunity. If your corporate structure is changing — through acquisition, divestiture, or reorganisation — understanding the affiliate mechanics allows you to time transactions to maximise EA coverage, minimise true-up costs, and structure the transition before Microsoft's account team identifies the change and uses it as leverage.
This guide covers the EA affiliate definition, the 50% ownership threshold, what is excluded, how affiliate changes are handled mid-term, and the negotiation amendments that provide meaningful protection for complex corporate structures.
Key stat: Affiliates and subsidiary coverage gaps are the second most common finding in Microsoft audit engagements, after virtualisation counting errors. In approximately 34% of audits involving enterprise organisations with multiple legal entities, at least one entity is using EA-covered software without technically qualifying as an Affiliate.
The EA Affiliate Definition
The EA defines an Affiliate as any legal entity in which the Enrolling Affiliate (the organisation signing the EA) owns or controls more than 50% of the voting securities or equity interests — directly or indirectly. This applies in both directions: entities controlled by the enrolling organisation, and entities that control the enrolling organisation.
The 50% threshold is a bright line. A 49%-owned joint venture does not qualify as an Affiliate. A 51%-owned subsidiary does. This matters operationally because joint ventures, minority investments, and partnerships — which increasingly characterise enterprise corporate structures — exist in a coverage gap.
Equally important: the affiliate relationship must exist at the time of use. An entity acquired mid-term does not become an Affiliate until the acquisition closes and the ownership threshold is met. Software usage by the target in the gap period between signing and closing is technically unlicensed under the EA (though in practice Microsoft's audit response depends on how the situation is disclosed and managed).
| Entity Type | EA Affiliate Status | Notes |
|---|---|---|
| Wholly owned subsidiary (100%) | Yes — Affiliate | Covered automatically; should be included in true-up count |
| Majority-controlled subsidiary (51%+) | Yes — Affiliate | Covered; minority shareholders' employees are also covered if entity qualifies |
| 50/50 joint venture | No — not an Affiliate | Neither partner controls >50%; requires separate licensing |
| Minority investment (under 50%) | No — not an Affiliate | Investee entity is independent; its employees are not covered |
| Parent company (owns >50% of EA signer) | Yes — Affiliate | Coverage is bidirectional; parent is an Affiliate |
| Sister company (common parent owns >50% of both) | Yes — Affiliate | Indirect control via common parent qualifies both entities |
| Portfolio company (PE fund holds >50%) | Situation-specific | Depends on whether EA signer is the same PE fund or a portfolio entity; fund structure matters |
| Acquired entity (acquisition closed during EA term) | Yes — from close date only | Pre-close usage is technically unlicensed; Day 1 compliance gap risk |
| Divested entity (sold during EA term) | No — from close date | Loses Affiliate status at close; must transition to independent licensing |
The Day 1 Compliance Gap in Acquisitions
The most commercially significant affiliate gap arises in acquisitions. The target company is running Microsoft software under its own agreements (or, commonly, under ad hoc purchasing) at the time of signing. From Day 1 of close, it becomes an Affiliate and its software usage is notionally covered by the acquirer's EA — but only for products that are in the EA's product list and at the enrolled product count.
The compliance exposure surfaces at true-up. The acquirer's EA true-up must now include all users across all Affiliates, including the newly acquired entity. If the acquired entity has 500 M365 E3 users that were not in the acquirer's EA count, those 500 seats must be added at the EA annual true-up — and if the true-up is annual, the acquirer may be reporting a full-year shortfall on a mid-year acquisition.
The M&A licensing due diligence process should include an inventory of the target's Microsoft licensing position before close. The acquirer needs to know: what Microsoft products the target uses, at what counts, under what agreements, and with what Software Assurance status. This inventory drives the true-up planning and determines whether the target entity should be added to the EA immediately at close or maintained separately through a transition period.
Day 1 gap warning: The window between acquisition signing and close can be weeks or months. If the target is using EA-covered products during this period, it does so outside any coverage (its own agreement may have been terminated or is in wind-down; the acquirer's EA coverage does not begin until close). This gap is a known audit trigger. Document the timeline and disclose the acquisition to Microsoft's licensing team proactively at close — managing the discovery is better than being audited for it.
Divestiture: Losing Affiliate Status
When an entity is divested, it loses Affiliate status from the close date. From that point, its employees are not covered by the remaining parent's EA. If the entity continues to use Microsoft software post-close — which it will, given operational continuity — it needs independent licensing arrangements before or immediately at close.
The practical challenge: Microsoft 365 and Azure subscriptions cannot simply be "split" at close. Users in the divested entity are provisioned in the same Microsoft 365 tenant and Azure subscriptions as the parent. Separation requires a tenant-to-tenant migration (for M365) and subscription reassignment (for Azure) — both of which take months and require licensing coverage during the transition period.
The typical approach is a transitional licence agreement: the divested entity continues to use the parent's infrastructure for a defined transition period (commonly 6–18 months) under a separate commercial arrangement. This arrangement must be negotiated as part of the transaction — it is not automatic. The EA does not provide for this natively; it must be addressed through an amendment or a separate stand-alone agreement with Microsoft.
Enrolling the Right Entities: The Affiliate Listing Problem
Most EAs do not contain an explicit list of covered Affiliates. Coverage is determined by the ownership test at the time of use, not by a schedule of named entities. This creates an administrative challenge: during an audit, Microsoft can ask the organisation to demonstrate that all users covered by the EA are employees of qualifying Affiliates. Without records of the ownership structure at the relevant dates, this can be difficult to evidence.
Best practice: maintain a corporate structure chart documenting ownership percentages for all entities, with effective dates, as part of the licensing governance framework. This chart serves as evidence in audit and as the source of truth for EA user count reporting. It should be updated whenever the corporate structure changes — acquisitions, disposals, reorganisations, or changes in minority holdings that cross the 50% threshold.
Some EA amendments include an explicit Affiliate schedule — a list of named entities that are confirmed to be covered. This has advantages (clarity, audit defensibility) and disadvantages (it must be maintained, and omitting an entity from the list could inadvertently limit coverage). The choice between explicit schedule vs. definition-based coverage should be made deliberate at EA renewal rather than defaulted.
Complex Structures: Private Equity and Holding Companies
Private equity structures create particular complexity. The EA is typically signed by the operating entity (Portfolio Company A), not by the PE fund. The fund may hold controlling stakes in multiple portfolio companies. Under the affiliate definition, Portfolio Company B (another portfolio company of the same fund) is potentially an Affiliate of Portfolio Company A — if the fund holds more than 50% of both and controls both.
This has been a source of significant commercial pressure. Microsoft's position (and the contractual interpretation in many EA amendments) is that where a common parent controls multiple portfolio companies, those portfolio companies are Affiliates of each other. This is commercially significant for two reasons: it means employees of Portfolio Company B are technically covered by Portfolio Company A's EA (which the EA signer did not intend and did not licence for), and it means the EA user count should notionally include all employees across all fund portfolio companies.
The correct approach for PE-owned businesses is to address this directly at EA signing: negotiate an affiliate definition that explicitly limits coverage to the named portfolio company and its direct subsidiaries, excluding other fund portfolio companies. This requires an amendment to the standard EA affiliate definition. Without this amendment, the default definition may sweep in entities the buyer did not intend — and create compliance exposure or unexpected volume-tier obligations.
PE fund advisory: If your organisation is PE-owned, your EA should contain an explicit amendment limiting affiliate coverage to your operating group. The standard definition's reference to indirect control via a common parent creates ambiguity that Microsoft can exploit at renewal or audit. This is a one-time amendment negotiation that provides long-term clarity.
True-Up Mechanics for Affiliates
The EA annual true-up covers all qualifying Affiliates. When reporting true-up data to your Microsoft account team, the user count must reflect all active users of each covered product across all Affiliate entities — not just the signing entity.
The common failure mode: the IT team running the true-up collects user count data from the primary tenant (the signing entity) and misses subsidiary tenants or separate Active Directory domains used by Affiliates. This results in under-reporting — which is a compliance gap that Microsoft can identify during audit by comparing the reported count against Azure AD and VLSC data across all associated tenants.
For organisations with multiple M365 tenants across Affiliates, the true-up process requires data collection from each tenant separately. A governance process for subsidiary tenant management — with defined reporting responsibilities — prevents the ad hoc data collection that creates under-reporting risk.
The flip side: if a subsidiary has its own EA or separate licence purchases, those products must not be double-counted in the parent EA true-up. The EA consolidation decision — whether to run separate EAs or a single consolidated agreement — has direct implications for the true-up process complexity.
Negotiation Amendments for Affiliate Provisions
The EA's standard affiliate definition is Microsoft's default. It is negotiable. The amendments that provide meaningful protection for organisations with complex corporate structures are as follows.
1. Explicit Affiliate Scope Limitation
An amendment that explicitly defines which entities are covered — by name or by reference to a schedule — eliminates ambiguity about scope. For PE-owned businesses, this amendment should carve out fund portfolio companies explicitly. For organisations with minority investments, it should clarify that investee companies are excluded regardless of economic relationship.
2. Acquisition Grace Period
A negotiated provision that allows a specified grace period (typically 90–180 days) after an acquisition close before the acquired entity's users must be added to the EA true-up count. This prevents a Day 1 compliance gap from triggering an immediate true-up obligation and gives the IT team time to complete the M365 tenant integration or transition planning. Some EAs include a standard 90-day grace period; many do not. Request it explicitly at renewal.
3. Divestiture Transition Licence Rights
An amendment that provides the right for a divested entity to continue using EA-licensed products for a defined transition period (6–18 months) following close, under commercially reasonable terms. Without this amendment, the divested entity loses coverage at close and must immediately source independent licensing — operationally impossible in most scenarios.
4. Prospective Affiliate Addition Process
A defined process for adding new Affiliates to the EA — including the mechanism, pricing, and timing for adding a newly acquired entity's users. Some EAs specify that new Affiliates can be added at the annual true-up at current EA pricing (protecting the buyer from mid-term add-on purchases at higher prices). Others require a formal amendment. The former is significantly more favourable commercially.
5. Affiliate Count Reduction Provisions
A provision allowing the count to decrease at annual true-up when an Affiliate ceases to qualify (through divestiture or loss of the ownership threshold). Without this, the EA's overall committed count may become inflated as the organisation changes over time. Count reduction provisions — combined with a clear divestiture transition mechanism — provide flexibility across the EA term.
| Amendment Type | Who Needs It | Negotiation Difficulty | Commercial Value |
|---|---|---|---|
| Explicit affiliate scope limitation | PE-owned businesses, holding companies with minority investments | Moderate | High — prevents scope creep and audit exposure |
| Acquisition grace period (90–180 days) | Any organisation with an active acquisition strategy | Low-moderate | High — prevents Day 1 compliance gap |
| Divestiture transition licence rights | Organisations planning divestitures or portfolio restructuring | Moderate-high | High — essential for smooth divestiture transactions |
| Prospective affiliate addition at current EA pricing | Active acquirers adding new entities during the EA term | Moderate | Medium-high — prevents mid-term pricing premium |
| Count reduction at divestiture | Organisations that may divest business units | Moderate | Medium — prevents over-commitment after divestiture |
Multinational EA Affiliate Complexity
For multinational organisations, the affiliate definition intersects with the geographic scope of the EA. A standard EA covers the signing entity and qualifying Affiliates regardless of country. However, some products — particularly those with data residency requirements, GCC variants, or country-specific Product Terms — may have restrictions on cross-border use or may require separate enrolments by country or region.
The practical implication: a UK EA signer with a US subsidiary qualifies the US subsidiary as an Affiliate, but the US entity's M365 usage may be governed by US-specific Product Terms and data residency provisions that differ from the UK EA terms. This is manageable but requires deliberate attention at EA signing to ensure the product list and terms reflect the geographic deployment reality.
Common Affiliate Licensing Mistakes
1. Assuming all group entities are covered. The 50% ownership test excludes joint ventures, minority investments, and portfolio companies of common parents unless specifically addressed. Audit your corporate structure against the EA affiliate definition before the auditors do.
2. Not planning for Day 1 compliance at acquisition close. The pre-close period creates a genuine licensing gap. Disclose acquisitions to Microsoft at close and manage the true-up proactively rather than leaving the gap undisclosed.
3. Forgetting subsidiary tenants in true-up reporting. True-up data must cover all qualifying Affiliates, not just the primary tenant. Establish a multi-tenant true-up data collection process with assigned responsibility at each subsidiary.
4. Not negotiating affiliate amendments at EA signing. The default EA affiliate definition is negotiable. PE-owned businesses, organisations with active M&A pipelines, and multinational groups should negotiate affiliate provisions at renewal — not when a transaction is already in flight.
5. Treating the EA as covering all commercial entities you work with. Contractors, service providers, and external partners who use your Microsoft environment are not Affiliates. They are external users governed by different Product Terms rules — and their licensing is a separate question from affiliate coverage.
Frequently Asked Questions
Does the EA cover a 50/50 joint venture?
No. A 50/50 joint venture does not meet the "more than 50%" ownership threshold. Neither partner controls the entity and it is not an Affiliate of either parent. The joint venture requires independent licensing unless a specific amendment is negotiated at the parent's EA renewal to extend coverage to the joint venture entity.
When does an acquired entity become an Affiliate?
From the close date of the acquisition, assuming the ownership threshold (more than 50%) is met. Usage before close is not covered by the acquirer's EA. If no grace period amendment has been negotiated, the acquired entity's users must be included in the next true-up following close — which can mean reporting a full-year shortfall on a mid-year acquisition depending on the EA's anniversary date.
Can I negotiate to exclude a subsidiary from EA coverage?
Yes. An amendment can explicitly carve out named entities or categories of entity from Affiliate coverage. This is useful when a subsidiary has its own separate EA or is planned for divestiture and should maintain independent licensing rather than being folded into the parent's agreement.
Are contractors covered under the EA affiliate definition?
No. Contractors, consultants, and service providers are not Affiliates regardless of their engagement relationship. Their use of EA-licensed software is governed by the Product Terms' provisions for authorised users — which generally allow third-party access for your benefit on your own devices but restrict full independent use without separate licensing.