Mind the Gap: Six Microsoft Protections UK Schools Lack

The 60-second Briefing

• Microsoft's AI Safety and Privacy Standard for Schools, negotiated with the American Federation of Teachers (AFT), takes effect in US school districts today, November 1 2026, with no renewal or opt-in required.
• UK schools using Microsoft 365 Education tenants already have Enterprise Data Protection, which includes the commitment that tenant prompts and responses are not used to train foundation models.
• The AFT standard adds six layers on top: an AI companion product ban, stronger contractual remedies, a published contract, third-party audits, plain-language transparency to families, and explicit human-oversight requirements.
• The contract is published for other providers to adopt. OpenAI and Anthropic have reportedly discussed similar standards with the AFT.
• No UK sector body has yet raised the AFT Standard as a UK renewal baseline. The gap is procedural, and one sector conversation would close it.

Microsoft's AI Safety and Privacy Standard for Schools takes effect in the United States today. For every US school district and US independent school already holding a Microsoft contract, the terms become contractually binding without renewal, opt-in, or additional negotiation. UK schools are not part of it.

UK school leaders already have AI protections in their Microsoft contracts through Enterprise Data Protection. The sharper question is what the AFT standard adds on top of that baseline, and whether UK sector bodies should be asking Microsoft for parity before the next renewal.

Let me walk through what EDP already gives UK schools, what the AFT Standard adds on top, and what UK sector bodies should do about the remaining gap.

What UK schools already have through EDP

Microsoft 365 Copilot, when used inside a licensed Education tenant with authenticated Entra sign-in, is covered by Enterprise Data Protection as a contractual term under the Microsoft Products and Services Data Protection Addendum. The baseline includes six substantive guarantees.

Prompts, responses, and data accessed through Microsoft Graph are not used to train foundation models. Microsoft acts as a data processor rather than a controller. Data is isolated between tenants. Customer data will not be used except as instructed. Encryption is applied at rest and in transit. GDPR and the EU Data Boundary apply where relevant.

Jisc's update on this in late 2024 confirmed that these protections apply to UK institutional accounts. For a school running Copilot with staff and pupils signed in through Entra, the baseline question of "is our data being used to train the model" is already answered contractually, and the answer is no.

That is a decent starting position. The AFT-Microsoft Standard shows what a more complete version looks like.

What the AFT Standard adds on top

Six specific layers that go beyond what EDP currently commits to.

The first is an explicit prohibition on AI companion products inside the covered contracts. Microsoft will not deploy, inside the schools stack, products built to create emotional attachment or sustained engagement for its own sake. EDP does not stop Microsoft from building that category of product and selling it into the schools market. The AFT contract does. Given KCSIE 2026's explicit naming of AI companion risks as a safeguarding concern, this is the most substantively important of the six add-ons.

The second is stronger contractual remedies. US school districts under the AFT Standard can end agreements and seek damages for violations of the specific terms. The remedies under the standard DPA are weaker and more constrained. For a bursar signing off a three-year Microsoft licence commitment, the practical ability to walk away or recover damages for breach is a different commercial position from the standard contract.

The third is a published contract. The terms of the AFT-Microsoft Standard are public. The standard Microsoft Education contract is confidential. A published benchmark gives every school procurement body a reference point to negotiate against, and gives market pressure on other providers to adopt the same language.

The fourth is third-party audits with published results. EDP commits Microsoft to a range of compliance frameworks (ISO 27018, GDPR, EU Data Boundary) and publishes some audit output. The AFT Standard commits to audits with results published to the schools themselves, in a form the sector can read and compare across providers.

The fifth is explicit plain-language transparency to families and educators about how AI tools work, what data they collect, and which safeguards apply. EDP operates mostly between Microsoft and the institution. The AFT Standard pushes transparency down to the pupil and parent level.

The sixth is explicit human-oversight requirements on important decisions. EDP touches on this through admin controls and permissions. The AFT Standard spells out that humans must be involved in important decisions as a contractual commitment, not just an administrative possibility.

How the AFT Standard came about

The negotiation did not come from Washington. It came from the AFT, the American Federation of Teachers, which represents 1.8 million members, together with the UFT, the New York City affiliate representing 200,000 members in the US's largest school district. Both unions negotiated directly with Microsoft over the summer of 2026, and both signed in September.

The negotiating leverage was union recommendations on which products US districts should buy. US school procurement sits with district administrators, but teacher union recommendations carry substantive weight on classroom-facing software decisions. Microsoft wanted the AFT and UFT recommendations. The AFT and UFT wanted contractual protections for the data and the pedagogical environment. The two sides met in the middle, and the middle was legally enforceable.

Brad Smith, Microsoft's President, has said publicly that the terms can be adapted to other countries. OpenAI and Anthropic have reportedly discussed similar standards with the AFT. Google has not, at the time of reporting.

Why the add-ons matter for UK schools

There are six specific protections US school contracts now include that UK school contracts do not. For most schools the baseline through EDP is strong enough to run Copilot pilots within an acceptable risk envelope. The question is whether that baseline is where UK schools should settle, when a stronger benchmark now exists and is publicly available for sector bodies to point to.

The AI companion ban is the sharpest example. A UK school running Copilot today is relying on EDP's general commitment that Microsoft will not use customer data except as instructed. There is nothing in that commitment that stops Microsoft from launching, next year or the year after, a classroom-facing AI companion product designed for engagement. US schools under the AFT Standard have an explicit contractual block on that direction, which UK schools do not have in their current contracts.

The published contract is the other sharp example. Any UK procurement officer wanting to negotiate stronger terms with Microsoft is currently negotiating from an unseen reference point. US schools now have a published contract to point to. Any UK sector body asking Microsoft for parity has, as of today, a specific document to table.

The policy architecture gap

Three UK policy frameworks already ask schools to govern AI products commercially sold to the sector. KCSIE 2026 names AI-generated content, deepfakes, and AI companion risks as safeguarding concerns. The ICO EdTech audit from June called out procurement discipline on commercial AI products. The DfE EdTech Procurement Guidance from July set out expected standards for how schools buy EdTech.

None of those frameworks currently requires UK school procurement to include what the AFT-Microsoft contract now provides in US school procurement. The policy architecture gives the sector the governance obligations without giving it the contractual leverage to meet them cleanly. The AFT Standard shows what closing that gap looks like, through sector-body negotiation rather than new policy.

The DfE Education Buying Platform, ISC procurement bodies, the Catholic Education Service and the main multi-academy trust procurement vehicles can each close the gap with one conversation. The published contract exists and the commercial relationship with Microsoft is already in place. The only thing missing is the conversation.

What UK school leaders can do this week

Three practical actions for IT Directors, bursars, and Senior Leadership Teams.

The first is a benchmark review. Pull your current Microsoft 365 Education contract and the EDP terms that apply to it. Compare the baseline against the published AFT Standard. Document which of the six AFT add-ons you have and which you do not. A board that can point to a specific list of gaps is in a stronger governance position than one that cannot.

The second is a procurement conversation. If the school is coming up for Microsoft contract renewal in 2027 or 2028, the question for the account manager is specific. Will Microsoft provide the terms of the AFT-Microsoft Standard in a UK schools contract on request? If yes, those terms become the renewal baseline. If no, the school has evidence to document a procurement decision based on a known commercial gap.

The third is a sector conversation. Independent school procurement bodies, state sector buying frameworks, and multi-academy trust procurement vehicles have not yet, from the public record, raised the AFT Standard as a UK baseline. One sector body making the ask would do more for UK schools' procurement position than every individual school asking separately.

A broader point

I have been arguing for most of this year that commercial AI governance in schools is a procurement discipline problem. Microsoft's EDP shows that providers will offer substantive protections when the sector asks for them clearly. The AFT-Microsoft Standard shows that providers will go further when a sector body sits across the table with specific asks and real procurement leverage.

The guardrails US schools got today did not come from new US federal law or new US education policy. They came from a sector body, representing teachers, sitting across a table from a cloud provider and negotiating specific contractual terms that reflected the sector's substantive interests. That is the model UK schools should be asking their own sector bodies to pursue.

Microsoft has published the contract. The commercial precedent exists. The question is whether UK sector bodies will ask for the add-ons, or continue to operate on a reasonable baseline when a stronger benchmark now exists.

Read the AFT-Microsoft Standard. Compare it to your current EDP terms. Then raise the gap with whichever procurement body sits upstream of your school.

See you in the digital staffroom.