A board with six schools assigns Copilot licences to its staff after the summer. In the first week, a form tutor asks Copilot what is known about a pupil, to prepare for a meeting with the parents. The answer is tidy, with citations, and includes a passage from the report of a pupil support meeting, stored on a team site open to all staff.
Nothing was hacked and nothing was broken. That is precisely why the licence is the beginning, not the end. Beyond the licence, an education organisation needs to settle four things: which variant staff use, the permissions on the places where pupil data is kept, which data and connections are allowed in, and what has been decided about the AI tools teachers use alongside Copilot. The general version of those decisions is covered in our article on Microsoft Copilot governance; this piece is about what is different in a school.
Which Copilot do staff get?
Three services go by the name Copilot. The consumer version on copilot.microsoft.com, used without a school account, runs under consumer terms. Microsoft 365 Copilot Chat, used while signed in with the school account, falls under Microsoft's enterprise data protection. Outside Outlook it works with the web and with whatever the user adds. Inside Outlook it can use email, calendar, meetings, chats and a bounded set of OneDrive and SharePoint files, even without a licence (Microsoft Learn, Microsoft Copilot Chat Privacy and Protections, checked 25 October 2026). For a special educational needs coordinator who emails about pupils, that matters. The paid Microsoft 365 Copilot reaches everything the user has access to through Microsoft Graph: mail, calendar, Teams, SharePoint, OneDrive. The facts for each variant are set out in our article on the privacy risks of Copilot.
For a school, that means two decisions. Who gets the paid variant and who works with Copilot Chat: a special needs coordinator with access to pupil support files is a different kind of user from a teacher preparing lesson materials. And what status does the consumer version get, given that some teachers were already using it at home on a personal account before the licence existed? Whether pupils get a variant too is a separate decision, with Microsoft's own terms, and falls outside the scope of this piece.
Where do the pupil files really live?
Officially in the pupil tracking system, which is usually a separate environment that Copilot does not search. In practice there is a second layer in Microsoft 365: the support meeting report on a team site, the development plan as a Word file in OneDrive, an exported mark sheet as an email attachment, the notes from the pupil progress meeting in a channel. That layer grew without anyone ever calling it a pupil file.
Copilot does not break permissions. It searches with the user's permissions, and that is the problem: a team site opened up to "all staff" in 2022 because something had to be shared quickly was only protected by the fact that nobody knew the report was there. An assistant searches by meaning, everywhere at once, and summarises what it finds. What changes is not the access but the effort involved. How that works is explained in our article on Copilot and SharePoint, and it is why Microsoft puts tackling oversharing first in its own deployment guidance, before licences are assigned.
On top of that, a school faces two questions that matter less in an office. Who is allowed to see a pupil support file: the support team, the form tutor or everyone who teaches the class? And what happens to the files of pupils who have left, on sites that were never archived? Both questions already existed; the assistant makes them urgent.
Which data and connections are allowed?
Microsoft 365 Copilot does not use prompts, responses or Graph data to train its models. That tells you something about what Microsoft does once the data has arrived, not about what may be sent. Can a form tutor ask Copilot to summarise a support note for a parents' meeting? In an environment with the school account and a data processing agreement, the answer is often yes, subject to conditions, and those conditions need to be written down.
What already exists is the DPIA on Microsoft 365 Copilot published by SURF and SLM Rijk, which manages Microsoft contracts for Dutch central government. The first version, in December 2024, found four high risks and advised against using the service for the time being; after Microsoft's changes, the September 2025 update downgraded the risks to amber, with two residual concerns. That DPIA describes the service. It does not describe the permission structure of your sites, the connections and agents your administrators switch on or the tools used alongside it; what the board needs to add itself is covered in our article on a DPIA for Microsoft Copilot.
| Decision | The question for a school board | What you record |
|---|---|---|
| Variant and users | Who gets the paid variant, who gets Copilot Chat, what applies to the consumer version | A status for each variant, with the reason |
| Permissions on pupil data | Which team sites and folders with support reports, development plans and exported mark sheets are open to more people than intended | A permissions report with a date, and who cleaned it up |
| Data in the prompt | Can a support note, a mark sheet or a meeting report go in, and on what condition | One line per category |
| Connections and agents | Which connectors and agents are switched on, and who signed them off | A list with an owner for each connection |
| Tools alongside Copilot | What status ChatGPT, MagicSchool, the extensions and the grading tool have | A register with four statuses |
| Measurement | Are staff using the preferred tool, without you tracking individuals | Counts per tool, no names |
Which tools run alongside it?
Assigning licences rarely means all AI use goes through Copilot. At the board in the opening paragraph, an inventory in the spring shows that besides Copilot, the free version of ChatGPT, MagicSchool and an extension that summarises lesson videos are in use, plus a grading tool at one school. No decision was ever taken on three of them. Why teachers do that is a separate question; what matters to the board is that it happens and that the Copilot policy says nothing about it.
The point is not which tools you ban, but that every tool in use gets a status: allowed, limited use, no decision yet or not allowed. Naming Copilot on the school account as the preferred tool is a decision too. BeeSensible matches a catalogue of AI tools against the use observed in the organisation: only the domain, at most once a day per device, with no user ID. In the Inbox, an administrator sees which tools have no decision yet and records one; consumer and business variants of the same service appear as separate rows.
