Six Microsoft Product Terms changes that took effect on 1 September 2025 — Copilot Chat entering the Core Online Services list, Visual Studio moving under the MCA, Windows 10 ESU through CSP, and more. What each one changes, and what to do about it.
Six changes landed in the Microsoft Product Terms on 1 September 2025. None of them is dramatic on its own. Together they move compliance scope, contract vehicle and purchase route all at once, which is exactly the combination that catches licensing teams out at the next true-up.
What changed. Microsoft 365 Copilot Chat has been added to the Core Online Services data-at-rest list, together with EU Data Act clauses.
Effective. 1 September 2025.
Impact. Higher compliance obligations for regulated sectors, and a strong likelihood of scrutiny under EU rules.
Action. Review how Copilot handles data and align it with your industry-specific compliance policies.
Source. Microsoft Product Terms, September 2025.
What changed. Visual Studio licensing has moved under the Microsoft Customer Agreement.
Effective. 1 September 2025.
Impact. Visual Studio entitlements must now be managed under the new contract terms rather than the previous vehicle.
Action. Validate your coverage under the MCA and update licence assignment workflows accordingly.
Source. Microsoft Product Terms, September 2025.
What changed. Windows 10 ESUs are now purchasable through CSP.
Effective. 1 September 2025.
Impact. Easier access to legacy support, particularly for CSP-managed environments.
Action. Finalise your ESU purchasing plan. Check first whether Windows 365 or an Azure VM makes a better cost case for the machines involved — for some fleets the migration is cheaper than the extension.
Source. Certero Insider, August 2025.
What changed. The Teams API terms have been updated to comply with EU security regulations.
Effective. 1 September 2025.
Impact. Developers and integrators may face stricter data handling or authentication requirements.
Action. Review the new API terms and developer guidance, then assess your existing integrations against them.
Source. Microsoft Product Terms, September 2025.
What changed. New bundles have launched covering Defender, Purview and combined suites.
Effective. 1 September 2025.
Impact. Better value at SMB scale, but the bundles are limited to a maximum of 300 seats.
Action. Check eligibility, and make sure deployments respect the 300-user cap. Growth past that ceiling is a re-licensing event, not a top-up.
Source. Microsoft Product Terms, September 2025.
What changed. Windows 365 is now available in GCC and GCC High, and a disaster recovery add-on has been introduced for Frontline Dedicated mode.
Effective. 1 September 2025.
Impact. Adoption becomes easier for US public sector organisations, and there is a new DR option for frontline use cases.
Action. Evaluate the fit for government workloads and assess the cost case for the DR add-on.
Source. Microsoft Product Terms, September 2025.
Every “action” above ends in the same place: you need to know what you have deployed, what you are entitled to, and where the two disagree — before the contract change bites rather than after.
CerteroX SAM holds that in one place. The Microsoft Licence Statement imports directly, alongside volume licence, retail, OEM and FPP transactions, agreements, maintenance and subscription expiry dates. Device CALs, user CALs, named user and external connectors are modelled properly, as are SQL Server and Windows Server core and processor licensing with cluster and virtualisation awareness. The effective licence position — purchased, used, available, required, variance and exposure — is computed continuously, so a change in Product Terms becomes a number you can look at rather than a project you have to schedule.
Two of this month’s changes are worth watching in that view specifically. The Visual Studio move to the MCA changes which agreement your entitlements hang off, which is the sort of change that quietly orphans a licence record. And Copilot Chat entering the Core Online Services list means AI usage is now inside your compliance scope whether or not anyone has formally adopted it — which makes knowing who is actually using it a governance question, not a curiosity.
Other posts covering the same ground.
A 2020-cycle read on CIO priorities — talent, devolved decision-making, culture, data, automation and new technology — and what each one meant for ITAM and SAM teams. Revisited with what the tooling can actually do now.
The licensing and vendor news that mattered in August 2025: Microsoft product terms and price rises, Oracle Java soft audits, the Adobe subscription case, VMware versus Siemens, and the EU Digital Networks Act.
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.
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.