The 60-second summary

The May 2026 Microsoft Product Terms (PT) update lands inside an unusually heavy commercial cycle. Six material changes this month: Copilot Studio capacity pack consumption rules, Agent 365 territory and dual-use clarification, the formal codification of Defender for Office 365 Plan 1 bundling into Microsoft 365 E3, a footnote update reflecting the EA volume tier collapse for new EAs, three Server and Cloud Enrollment (SCE) clarifications targeting Azure Hybrid Benefit eligibility, and the formal removal of the CSP grace period from the licensing terms. None of these are surprises — all have been telegraphed by Microsoft over the past quarter — but their formal codification in the PT changes the contractual position of buyers in concrete ways. We walk each change with what it actually means at the negotiation table.

How to read the Product Terms delta each month

The Microsoft Product Terms is the live document that governs use rights, licensing metrics, and product-specific contractual terms across every commercial channel (EA, MPSA, CSP, MCA). It updates on the first of every month. Most months the delta is small — one or two cosmetic clarifications. Cycle months (May, September) carry heavier deltas because Microsoft uses them to land programme changes that need contractual codification.

The right reading method is not "read the whole PT" but "read the delta only, then check whether anything in the delta touches a SKU you actually buy or a use right you actually rely on." Microsoft publishes the delta as a change log. For procurement, the 10 minutes spent on the May delta is the highest-leverage 10 minutes of the month — it tells you what shifted contractually since you last looked.

Copilot Studio capacity pack consumption rules

The May 2026 delta clarifies how Copilot Studio capacity packs (CCCUs and pay-as-you-go) consume against agent runtime, with three specific changes:

  • Multi-agent invocation flows now consume CCCUs at each agent step rather than once per outer-flow trigger. The clarification removes ambiguity that existed in the Q1 2026 PT.
  • Authenticated user-attributed runtime is metered at a different CCCU rate than unauthenticated tenant-scoped runtime — with the May update formalising the per-message vs per-session distinction.
  • The agent pre-purchase plan (APP/ACU) is now contractually portable across tenant boundaries within the same Microsoft customer agreement, which had been ambiguous in earlier PTs.

What it means: if you bought Copilot Studio CCCUs based on the Q1 2026 PT and modelled multi-agent flows as single-consumption events, your actual consumption is going to run higher than your model predicted. Re-calibrate your CCCU forecast before your next pre-purchase plan cycle. Our CCCU economics article walks the new arithmetic.

Agent 365 territory and dual-use clarification

The PT formally clarifies that Agent 365 is a per-user licence that follows the user's primary tenant, not the user's geographic location, and that dual-use rights apply to users with both personal and work agent activity inside the tenant. Two specific implications:

  • Multi-tenant enterprises with users straddling regions now have a clean contractual position on which tenant pays the Agent 365 fee.
  • Users with both work-mode and personal-mode agent invocations are covered under a single licence rather than requiring duplicate licences.

What it means: if your Agent 365 deployment model assumed multi-licence overhead for cross-tenant or dual-use scenarios, the May PT reduces your licence count. Audit your model before your next true-up.

Negotiation note

The Agent 365 dual-use clarification is one of the rare PT changes that genuinely benefits buyers. Microsoft will not flag this to you proactively. Find it yourself, apply it, and lower your licence count where it applies.

Defender for Office 365 P1 bundled into M365 E3

The May PT contains the formal codification of MDO P1 bundling into M365 E3. The change is functionally what Microsoft has been telegraphing since February 2026, but the PT entry is what gives the bundle contractual force for new EAs and CSP subscriptions from May 1 onwards. Three specific PT mechanics:

  • The MDO P1 standalone SKU remains in the price list for non-E3 buyers and remains buyable independently.
  • For E3 buyers, the MDO P1 use right is now embedded in the E3 product entry and not removable.
  • Renewal-cycle E3 customers keeping their existing E3 entitlements through anniversaries pre-July 2026 retain the unbundled E3 (without MDO P1) until renewal — the bundle catches them at the next renewal anniversary.

What it means: the bundle is now binding for new commitments. Existing customers have one renewal cycle of breathing room before the bundle catches them.

Need this delta translated to your contract?
We run a Product Terms impact review against your live agreement and flag every change that touches what you actually buy.
Book a PT Review

EA volume tier collapse footnote

The May PT contains a single-line footnote update reflecting the EA volume tier change that took effect for new EAs from April 2026. The footnote does not introduce the change — that happened in February's PT — but it cleans up references to the deprecated Level A/B/C/D pricing in adjacent product entries.

What it means: negligible direct impact, but it confirms Microsoft considers the tier change settled contractually. Buyers arguing for tier protection at renewal should reference the prior PT, not the May PT.

Server and Cloud Enrollment (SCE) clarifications

Three SCE-related clarifications in the May PT:

  • Azure Hybrid Benefit (AHB) for Windows Server in Azure-only SCE renewals is clarified to require active Software Assurance on the underlying licences at the time of AHB usage, not just at the time of original purchase. This closes a small ambiguity that some customers used to extend AHB beyond SA lapse.
  • SQL Server Big Data Clusters are formally retired from the PT, consistent with Microsoft's prior product announcement.
  • The Visual Studio Subscription language is updated to reference the merged GitHub Enterprise + Visual Studio bundle that Microsoft announced at Build 2026.

What it means: the AHB clarification is the meaningful one. If your AHB usage was relying on legacy SA from licences whose SA has since lapsed, the May PT closes that door. Audit your AHB attribution.

CSP grace period removal

The May PT formally removes the seven-day CSP grace period that had been the unofficial buffer between subscription end-of-term and cancellation enforcement. The change codifies the policy that took effect in April 2026.

What it means: CSP subscription management tooling and processes need to assume zero grace. Renewals that miss the renewal date are cancelled, not pause-and-renewed. If your CSP partner's tooling still assumes the grace period, your renewal risk is real.

What to do with the May 2026 PT delta this month

  1. Pull the official Product Terms change log. The PT is published at microsoft.com/licensing/terms with monthly delta downloads.
  2. Cross-reference against your live SKU list. Each PT change only matters if it touches a SKU you buy. The 10-minute review filters the noise.
  3. Apply the Agent 365 dual-use clarification to your licence count. Lower the count where applicable. Microsoft will not flag this.
  4. Audit AHB attribution. The SA-active-at-usage clarification can catch you on a true-up if your AHB tracking is loose.
  5. Tighten CSP renewal tooling. Zero grace means zero room for slip.
  6. Recalibrate Copilot Studio CCCU consumption forecasts. Multi-agent flows consume differently than the Q1 2026 PT implied.

The Product Terms is the most underrated document in Microsoft licensing. Most buyers never read it. Reading the delta every month, in 10 minutes, is the single highest-information-per-unit-time activity in licensing operations.