From the Microsoft edition of October 30, 2026
Microsoft fact sheet: from Nov. 1, every US school district can add the AFT-agreed AI Safety & Privacy Standard protections to new or existing Microsoft agreements without renegotiation; 10 contractually enforceable protections
Microsoft (with the American Federation of Teachers) · K-12 · United States
- Publisher
- Microsoft
- Original publication
- Undated fact sheet; protections available from 2026-11-01
- Source retrieved
- 2026-10-31
- Event date
- 2026-11-01
What happened
A Microsoft fact sheet on the AI Safety & Privacy Standard agreed with the American Federation of Teachers says that beginning Nov. 1, 2026, Microsoft will make the Standard's protections available to every US school district, which can add them to new or existing agreements with no renegotiation or renewal, and that the protections are contractually enforceable. It lists 10 protections, including no training on student or educator data (apart from a narrow safety and security exception), data minimisation, customer data ownership with no sale or advertising use, human review of high-risk decisions and a ban on AI companions, breach reporting within 72 hours, encryption and independent testing, plain-language family guides, accessibility commitments including funding an independent study, no feature creep or vendor lock-in, and permanent training and sale bans.
Why it matters
Takes effect Nov. 1, two days after this edition: districts using Microsoft AI can add enforceable student-data and safety terms. Cross-tagged to k12 because it applies to every US school district.
Evidence and measured results
Vendor-authored summary of contractual commitments. Contract language and enforcement mechanics were not reviewed; no independent assessment.
Limitations and uncertainty
Vendor fact sheet, undated; the binding contract text was not inspected. Whether the protections cover all Microsoft AI products and how disputes are resolved is not shown. Applies to US districts only.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-31; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Districts need enforceable student-data and safety terms for AI products from major vendors.
- Stakeholders
- Superintendent
- District counsel
- Director of technology
- Teachers' union
- School board
- Discovery questions
- Have you reviewed the Standard's terms?
- Who will sign the addendum?
- How will compliance be monitored?
- Which Microsoft AI products do you use with students?
- Value hypothesis
- Opting in and operationalising the protections may strengthen trust with families and staff.
- Potential engagement
- Contract opt-in support and compliance-monitoring setup for the AI Safety & Privacy Standard.
- Unsupported claims
- The protections improve safety outcomes
- Contract text details (not reviewed)
- Coverage of every Microsoft product
Pre-sales engineering
Role takeaway
- Fit
- US districts using Microsoft 365 Education and Copilot.
- Architecture and integration
- Mapping contract commitments to tenant controls and processes.
- Prerequisites
- Addendum text
- Admin controls inventory
- Incident-response plan
- Constraints
- Fact sheet only
- US only
- Security
- Verify that no-training, deletion and breach terms are reflected in processes.
- Proof of value
- Tabletop a breach to test 72-hour reporting
- Audit feature-rollout controls
Delivery
Role takeaway
- Work
- Opt-in, policy update and compliance routine.
- Dependencies
- Legal review
- Board approval if required
- Ownership
- District counsel with the technology director.
- Skills and adoption
- Staff briefing on the protections and family guides.
- Governance checkpoints
- Addendum signed
- Annual compliance review
- Acceptance criteria
- Proposed: addendum executed and policy updated within a term
- Risks
- Assuming protections without signing
- Gaps between fact sheet and contract
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Commitments on feature control and data export may affect how new AI features are enabled in district tenants.
Governance
Who approves, reviews and stays accountable for outcomes?
Districts gain contract terms on human oversight, transparency and feature control that can anchor board AI policies.
Security and privacy
What data, permissions and controls need testing?
72-hour breach reporting, no-training and no-sale commitments, and deletion duties after contract end are concrete privacy terms to verify in the actual addendum.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Includes accessibility and equity commitments and funding of an independent study.
Procurement
What should contracts, pricing and exit terms secure?
Districts can attach protections to existing agreements without renewal, a low-friction contract action.
Operating model
Which teams own the service once it runs?
District legal and technology staff need a process to opt in and monitor compliance.
Publication history
- 2026-10-30Microsoft · Issue 0213 resources
Stable resource ID: microsoft-ai-safety-privacy-standard-schools-available-all-us-districts-nov-1-2026