Microsoft EA affiliates and subsidiaries are governed by the affiliate-inclusion schedule, the affiliate definition language, and the change-of-control clause. The affiliate definition typically uses a "50% direct or indirect ownership" threshold, which controls which legal entities can consume licences under the parent EA. The affiliate-inclusion schedule names the specific entities expected to consume; entities omitted from the schedule are not licensed even if they meet the ownership threshold definition. The change-of-control clause governs what happens to the EA when ownership of the contracting entity shifts. The three mechanics interact: M&A activity, divestitures, joint-venture formations, and even internal restructuring all touch one or more of these clauses. The buyer-side discipline is to maintain a current affiliate-inclusion schedule, negotiate the change-of-control terms before they are needed, and use the affiliate definition as a leverage point in renewal cycles. The 2026 amplifier is the EA tier-collapse: the affiliate aggregation determines the volume that lands in the tier-collapse grid, so the affiliate-inclusion schedule directly affects the discount-tier outcome. The companion EA negotiation pillar covers the broader contractual context.
The starting position on EA affiliate mechanics: most large-enterprise licensing teams know there is an affiliate-inclusion schedule and a change-of-control clause in the EA, but the contractual specifics are rarely actively managed. The schedule is built at original EA execution and then carried forward through renewals as a static exhibit, sometimes for ten or fifteen years across multiple renewal cycles. Material organisational changes — acquisitions, divestitures, restructurings, joint ventures, geographic expansion — frequently happen without corresponding updates to the affiliate-inclusion schedule. The result is a licensing position that is structurally misaligned with the actual legal-entity structure of the organisation. Active management of the Microsoft EA affiliates framework is one of the simplest sources of negotiation leverage and compliance hygiene in the licensing portfolio.
Microsoft EA affiliates: the definition language
The affiliate definition in the EA Master Agreement establishes who can consume licences. The standard definition language is roughly: "Affiliate" means any legal entity that controls, is controlled by, or is under common control with the Enrolled Affiliate, where "control" means direct or indirect ownership of at least 50% of the equity or voting interests in the entity.
- The 50% threshold. The standard threshold is 50%; some negotiated agreements lower it to 30% or 40% for organisations with significant minority-investment structures. Lowering the threshold expands the universe of eligible affiliates and is a buyer-side leverage objective in master-agreement negotiation.
- Direct and indirect ownership. The definition typically captures indirect ownership through intermediate holding entities. A 100%-owned sub-of-a-sub is still an affiliate. The "common control" language captures sister entities under a shared parent.
- The control standard. Control is generally equity-based, but some definitions add voting-rights or board-control language. The variant matters in venture-backed and private-equity structures where equity and voting can diverge.
- The duration of affiliate status. An entity is an affiliate for as long as it meets the control standard. If ownership drops below 50%, the entity ceases to be an affiliate and its consumption is no longer authorised under the EA. The transition is rarely operational — it requires explicit notice to Microsoft and a re-papering of the consumption position.
- The relationship to the Enrolled Affiliate. The Enrolled Affiliate is the specific legal entity that signs the EA enrolment. Affiliates are entities related to the Enrolled Affiliate under the definition. The Enrolled Affiliate is contractually responsible for affiliate compliance with the EA terms.
Microsoft EA affiliates: the inclusion schedule
The affiliate-inclusion schedule is a deal-document exhibit naming the specific entities that consume licences under the EA. The schedule is operationally as important as the definition itself.
| Schedule attribute | What it controls | Buyer-side discipline |
|---|---|---|
| Named legal entities | Identifies which entities are authorised to consume under the EA | Maintain a current schedule; add new entities promptly |
| Per-entity headcount estimate | Drives the per-entity Reserved-User commitment | Use realistic estimates; avoid both over- and under-commitment |
| Per-entity geography | Tracks geographic scope and tax-residency for invoicing | Confirm geography matches the actual operational reality |
| Per-entity SKU consumption | Documents the SKU mix each entity is expected to use | Update when entities materially shift SKU mix (e.g., F1/F3 expansion) |
| Schedule update cadence | Frequency at which the schedule is refreshed with Microsoft | Quarterly review minimum; refresh at every anniversary |
| Schedule exclusions | Entities deliberately excluded from EA coverage | Document exclusion rationale; verify alternative licensing instrument |
A common failure mode: the affiliate-inclusion schedule names a parent entity and lists "and its subsidiaries" without enumerating the specific subsidiaries. Microsoft account teams will accept this language at execution but treat it as ambiguous when audit findings arise. Explicit enumeration removes the ambiguity. The enumeration also feeds the consolidated-volume calculation that determines the discount tier, so under-enumeration costs discount value at every anniversary.
Microsoft EA affiliates and the change-of-control clause
The change-of-control clause governs what happens to the EA when the ownership of the Enrolled Affiliate changes. The clause has material implications for M&A activity and for divestitures.
Stock acquisitions typically continue the EA with the acquirer
If the Enrolled Affiliate is acquired in a stock transaction, the EA generally continues in force under the new ownership. The acquirer steps into the Enrolled Affiliate's contractual position. Microsoft's consent is sometimes required and sometimes not, depending on the specific clause language. Where consent is required, it is "not unreasonably withheld" — but Microsoft has historically used the consent moment as a re-pricing leverage point. The M&A playbook covers the broader transaction-structure interaction.
Asset acquisitions typically do NOT carry the EA forward
If the transaction is structured as an asset acquisition rather than a stock acquisition, the EA does not automatically transfer. The buyer of the assets has to stand up its own licensing position for the acquired operations. This is sometimes the desired structure (acquirer wants its own EA terms) and sometimes a hidden cost in the asset-deal structure. The license transfer mechanics article covers the assignment posture in detail.
Divested affiliates exit the EA on divestiture closing
When an affiliate is divested (sold to a buyer outside the parent's control structure), the divested entity ceases to be an affiliate under the definition and exits the EA. The divested entity then needs its own licensing position (TSA bridge, new EA, new MCA-E, or CSP). See the EA-splitting playbook for the carve-out mechanics.
Joint ventures are affiliates only if the control standard is met
A 50/50 joint venture is typically not an affiliate under the standard definition (neither party "controls" the JV in the equity-50%-or-more sense). JV operations consuming Microsoft software need their own licensing instrument. A 51/49 JV controlled by one parent may be included as that parent's affiliate. The specific structure matters.
Internal restructuring (entity collapse, entity creation) requires schedule updates
Internal restructurings — merging two subsidiaries into one, spinning out a business unit into a new entity, re-domiciling an entity to a different jurisdiction — all require updates to the affiliate-inclusion schedule. Failure to update creates ambiguity that surfaces at audit time. Maintain a synchronisation cadence between the corporate secretary's entity register and the EA affiliate schedule.
EA affiliate-inclusion schedule unchanged since 2017? The unenumerated entities are costing discount value at every anniversary.
30-minute scoping call. Affiliate-schedule rebuild and renewal-cycle re-aggregation are standard advisory work.
Microsoft EA affiliates as renewal-cycle leverage
Active affiliate-schedule management generates leverage at three moments in the renewal cycle.
- T-12 affiliate review. Twelve months before EA renewal, the affiliate schedule should be reviewed against the corporate entity register. Material discrepancies (entities added since prior renewal, entities removed, entities re-domiciled) should be reconciled before the renewal modelling begins. Reference the EA renewal checklist tool for the T-12 through T-3 cadence.
- T-9 affiliate-driven volume aggregation. The reconciled affiliate schedule drives the consolidated-volume calculation that determines the discount tier at renewal. In the post-2026 tier-collapse pricing structure, the volume aggregation has materially higher leverage than under the prior A/B/C/D tier structure because the tier bands are narrower.
- T-6 affiliate-definition language negotiation. The affiliate-definition language itself is negotiable in the EA Master Agreement. Lowering the threshold from 50% to 40% expands the affiliate universe; adding voting-rights or board-control language captures venture-backed and PE-backed structures; specifying joint-venture treatment removes ambiguity. The renewal cycle is the moment to negotiate these refinements; mid-term amendments are structurally harder.
2026 amplifiers shaping affiliate management
Three 2026 dynamics reshape the affiliate-management priority list this cycle.
- EA tier-collapse aggregation impact. The post-2026 tier-collapse pricing structure narrows the volume bands. Affiliate-driven volume aggregation has higher leverage on the discount-tier outcome than under prior tier structures. The affiliate schedule is the underlying data set; rebuild it before the next renewal. Reference the EA tier collapse pillar.
- Copilot affiliate-licensing alignment. Copilot for M365 commitments and Copilot Studio capacity reservations frequently sit at the Enrolled Affiliate level rather than the affiliate-entity level. Where Copilot adoption is uneven across affiliates, the commitment exposure is concentrated at the parent. The affiliate schedule should be cross-referenced with the Copilot adoption ramp to identify stranded-commitment risk. See the Agent 365 framework.
- MACC affiliate scope. MACC commitments are generally scoped to the Enrolled Affiliate, but Azure consumption may be spread across multiple affiliates. The affiliate-schedule reconciliation should confirm that MACC scope aligns with actual consumption — affiliates consuming Azure outside the MACC scope are not earning growth-discount credit on that consumption. See the MACC negotiation pillar.
The affiliate-inclusion schedule is one of the few EA artefacts that the buyer-side controls almost entirely. Microsoft's account team rarely requests schedule updates and rarely pushes back on schedule changes. Buyer-side updates that add entities — particularly entities consuming Azure or Copilot — flow through to the consolidated-volume calculation and the tier outcome at renewal. Buyer-side updates that remove entities (divestitures, JV exits, dormant entities) reduce the parent's contracted-volume basis and may affect Unified Support tier calculation. The schedule update is therefore both a compliance discipline and a commercial leverage variable. Reconcile it at every anniversary, not just at renewal.
The Microsoft Negotiations briefing
Monthly. EA affiliate management, M&A licensing integration, renewal-cycle leverage, 2026 inflection-point intelligence. One-click unsubscribe.
Independent since 2016. Not affiliated with Microsoft Corporation.
Where to take the affiliate-management discipline next
EA affiliate management pairs with the broader M&A and renewal-cycle framework. The M&A integration playbook covers the broader programme context; the license transfer guide covers the assignment mechanics; the consolidation playbook covers post-close affiliate-amendment mechanics; the divestiture playbook covers affiliate-exit; the EA negotiation pillar covers the broader renewal-cycle context; the EA strategy service is the productised renewal-cycle engagement; the contract advisory service is the productised affiliate-schedule and amendment engagement; the EA renewal checklist tool is the cadence guide. For organisations managing material entity-structure change, the scoping call is the direct engagement channel; the free EA assessment is the broader entry channel.