Microsoft 365 DPA update: what companies should check
Microsoft updated its Data Protection Addendum (DPA) on 1 November 2026 and added a clause allowing it to report apparent abuse material to authorities. Companies using Microsoft 365 and Copilot should know which version applies to them and which records need an update.

What Microsoft changed in the DPA on 1 November 2026
Microsoft published an updated Products and Services Data Protection Addendum effective 1 November 2026. Its own change log lists two points, as Dr. Datenschutz reports. The first is a new sentence in the section on disclosure of processed data. It says Microsoft may report apparent child sexual exploitation and abuse material to the National Center for Missing and Exploited Children or another authority.
The second change concerns the section on previews. The exceptions for previews now apply unless something else is stated for a given preview. Professional services in a preview or limited release meet only the requirements for supplemental professional services.
Much stays as it was in the May 2026 version. The security incident notification chain, the customer duty to report account misuse, the allocation of roles and the 2021 standard contractual clauses for third countries are unchanged. The May version had already set a 30-day notice period for subprocessors with AI functionality, plus the option to disable their use for at least six months after notice. Both rules continue to apply.
Why the new reporting clause raises questions
The disclosure section is otherwise narrow. Microsoft discloses processed data on the customer's instruction, under the DPA or where the law requires it, and it passes authority requests back to the customer. The new sentence allows a disclosure that can happen without informing the customer first.
Three points cause confusion. The wording says Microsoft may report, which is a permission and no duty spelled out in the DPA. The recipient is open, because the clause names a US organisation and adds other authorities. The clause also says nothing about how Microsoft becomes aware of such material, and it describes no detection methods, no scope per service and no thresholds.
The background is a US reporting duty for providers that have actual knowledge of such material. The clause therefore mostly makes an existing legal position visible. It still widens the disclosure routes documented in the DPA. It remains open how Microsoft backs the clause up in its product terms or documentation, and how supervisory authorities will assess it.
What to check in Microsoft 365 now
Under the DPA's limits on updates, the current version applies from renewal or new signing and then stays stable for the term. The first task is to find out which version applies to which subscription. Record this per subscription and per work order, with the renewal or signing date.
- Records of processing: assess the new disclosure power as its own recipient category and as a possible third-country transfer, and reflect it in the Art. 30 GDPR records.
- Legal basis: Art. 28(3)(a) GDPR covers disclosures required by EU or member state law. A report based on US law falls outside that wording, so the scope of the clause needs assessment, ideally with your data protection officer or counsel.
- Information duties: check whether privacy notices for staff and data subjects cover the new disclosure route.
- Incident handling: link your duty to tell Microsoft about compromised accounts with your own incident process and the Art. 33 GDPR deadline.
- Contacts: the DPA makes the customer responsible for current notification addresses, and outdated contacts put your own 72-hour reporting at risk.
Also read the clause on government requirements. Microsoft may change or withdraw a product in a jurisdiction if regulation makes operation difficult. That matters for dependency analyses and exit plans, as do the switching rules under the EU Data Act.
Settling Copilot, previews and delivery in daily work
Write an internal policy that bars previews for personal or regulated data unless someone has approved them explicitly. Because the preview exceptions now apply more clearly, a tester who switches on a preview feature could otherwise move data outside the usual protections. Name an owner who approves previews and keeps a list of those in use.
Copilot users should know that subprocessors with AI functionality come with a 30-day notice period and a right to disable them. Decide who receives these notices and who judges whether to switch the use off. For more on the data protection side of such tools, see our page on GDPR-compliant AI.
Notices count as received once Microsoft makes them available, for example through a portal or website. You need a responsible mailbox and a fixed check interval, otherwise deadlines run without anyone noticing. A short calendar entry for the person in charge is usually enough to cover this.
Documenting the review and looking at alternatives
Keep a short file with the DPA version, the date you reviewed it and the places where you found each statement. If Microsoft later adds detail in its product terms or if regulators comment, you can update the file without a full review. The next DPA version should be on your watch list.
Some companies use the review to ask how much of their knowledge work needs a US-based provider at all. Our overview of a ChatGPT alternative for companies covers other options. Holders of professional secrets under § 203 StGB, the German Criminal Code, can also look at local AI and the security page.
souveraen.ai, from clouditiv GmbH in Auerbach, runs in two modes with the same software: On Demand, hosted in Germany, or on-premise in your own network. Its model catalogue holds local models, models hosted in Germany and external EU models with zero data retention. Whether this suits you depends on your own contract and risk review.
Sources
- Microsoft 365: Vertragsprüfung nach dem DPA-Update, Dr. Datenschutz


