Microsoft's August 2025 Product Terms changes: Extended Term standardised across programmes, Exchange and Skype for Business Server Subscription Editions, the Exchange and Windows 10 ESU programmes, and the Dynamics 365 F&O enforcement dates.
This was published in August 2025 as a point-in-time summary of that month’s Microsoft Product Terms changes. Every enforcement and expiry date it flags has since passed. It is kept here as a record of what changed and when, not as current guidance — check the Product Terms site for the position today.
Product Terms changes introduced Extended Term licensing across programmes, new Exchange and Skype for Business Server Subscription Editions, an Azure AI Foundry grounding clause, Unattended Bot support for Windows 365, and expanded Defender for Experts licensing paths.
Dynamics 365 F&O licence enforcement was set to begin on 1 November 2025, with warnings from September.
Extended Security Updates (ESU) for Exchange 2016 and 2019 became available from 1 August 2025 to support migrations to Subscription Edition, ending 14 April 2026.
Windows 10 ESU options launched in September, with coverage differing by deployment channel.
Subscription Editions (SE) for Exchange and Skype for Business Server reached general availability; standalone on-premises server products saw a 10% increase as of 1 July 2025.
Extended Term standardised across programmes. Online Services now include a 30-day grace period after expiration. Services may auto-extend month to month, charged at the current monthly rate plus 3%, unless the customer opts out. Once auto-extension is disabled, reactivation is not possible, but data remains available for 90 days. This benefit was previously available only under an Enterprise Agreement; it now applies cross-programme.
New Subscription Editions. Exchange Server and Skype for Business Server Subscription Editions are now listed and require Software Assurance or equivalent cloud subscription rights.
Exchange 2016 and 2019 ESU programme. A limited six-month Extended Security Update programme began on 1 August 2025 for Exchange 2016 CU23 and Exchange 2019 CU14 and CU15 customers, ending 14 April 2026. ESUs were delivered privately through account teams. The programme exists to cover the migration window to Subscription Edition, not to extend the product.
Windows 10 ESU availability. From 1 September 2025 via Volume Licensing:
Azure changes. A new “grounding with Bing Search” clause was added to the Azure AI Foundry Agent Service. Real-time web data use is billed as first-party consumption.
Windows 365 Unattended Bot licensing. Now included under the Microsoft 365 Product Terms as an option.
Microsoft Defender for Experts. Added to the EES, EA and EAS prerequisite tables, and now licensable via Azure Service.
CAL and ML Equivalency Table updated. Revised to reflect the new Subscription Edition licences and to map equivalencies between on-premises and online services.
From 1 September 2025, licensing warnings began appearing for unlicensed Dynamics 365 Finance and Operations users. From 1 November 2025, unlicensed users were blocked outright.
The action this called for was an assignment review: confirm which users hold which licence type, and reconcile that against what they actually do in the application before the block takes effect rather than after.
None of the above is complicated in isolation. The difficulty is that the changes land in different places: a grace period in the Online Services terms, an equivalency table for CALs, an enforcement date inside a single application, a price change on standalone server products, and a six-month security programme that only matters if you are mid-migration.
The organisations that handle a month like this well are the ones already holding a current position — what is deployed, what is entitled, who is using it, and which agreements come up for renewal next. That position is the thing an update is applied to. Without it, each change becomes a separate investigation.
CerteroX SAM maintains that position continuously rather than reconstructing it: Microsoft Licence Statement import, volume, retail, OEM and FPP transaction capture, device CALs, user CALs, named user and external connectors, and SQL Server and Windows Server core and processor licensing with cluster and virtualisation awareness. Subscription flags carry expiry dates, and end-of-life and end-of-support tracking flags what is about to fall out of cover.
Other posts covering the same ground.
An Oracle Unlimited Licence Agreement is only unlimited within its clauses. What certification actually asks of you, where toxic consumption creeps in, and why the measurement work has to start at the beginning of the term rather than the last six months.
Renew, rescope or exit — an Oracle ULA gives you three routes and a narrow window to choose between them. The questions to settle first, and a six-point health check to see how ready you actually are.
Java 17 was free under the No-Fee Terms and Conditions only up to Update 12. From 17.0.13 it moved to the Oracle Technology Network licence — and any production use pulls you into a subscription priced on your whole workforce.
Everything argued above is checkable. Name the publisher, the billing account or the platform you would argue with, and the session is built around it — the reasoning attached, not a summary slide.
No gated download at the end of it.