Microsoft's Copilot pages skip the age question schools ask first

The classroom note

A school IT administrator setting up Microsoft 365 Copilot for staff and older students has three questions to answer: which licence tier, what data protection applies, and at what age a pupil may hold an account. Microsoft's own documentation, read together, answers the first two in detail and leaves the third unstated. The Microsoft 365 Education documentation hub, as retrieved 16 September 2026, sets out three licence tiers, Baseline (A1), Standard (A3) and Advanced (A5), each adding identity, security and device management on top of the last, which is the frame a district actually configures Copilot within.

What the evidence says

The enterprise data protection page states that "prompts, responses, and data accessed through Microsoft Graph aren't used to train foundation LLMs," and that this protection applies once a user signs in with an organisational account under the tenant's Data Protection Addendum, the same terms Microsoft applies to email in Exchange. The Copilot overview page lists the admin controls that follow: group permissions, single sign-on, usage reporting, and the ability to "remove user access to Copilot Chat entirely." Neither page, nor the general Microsoft Education Copilot page, states a minimum age for a student account, in contrast with Google's published 13-and-18 figures for personal and work Gemini accounts and Khan Academy's stated 18-and-over rule for a paid Khanmigo subscription. That absence is itself a finding: the age question, for Microsoft, is answered somewhere other than the pages a search for "Copilot education requirements" surfaces.

The implementation question

What a district actually controls is the tenant, not an individual pupil's date of birth. Enterprise data protection attaches to any sign-in through the school's Microsoft Entra identity, so the practical safeguard is whether an administrator has issued an account to a given student and which licence tier that account carries, a pattern echoing Google's school accounts. This is an editorial inference from what the documentation does and does not say, not a quoted rule: because eligibility is not framed around age in these pages, a district cannot rely on Microsoft's own documentation to decide which year groups should have access; that decision falls entirely on local policy.

What holds and what fails

The data-protection and licensing claims are specific and stated plainly. What does not hold is any assumption, common to the vendors compared across this batch, that "education access" implies a published age floor; Microsoft's own pages, at least as retrieved, do not carry one, and a school cannot cite Microsoft's documentation to justify an age cut-off it has not set itself.

• Which licence tier, A1, A3 or A5, governs the Copilot features our students can actually reach?
• Has our administrator set an explicit minimum age or year group for issuing Copilot-enabled accounts, given that Microsoft's pages do not set one?
• Does our tenant's Data Protection Addendum cover the specific Copilot experience students use, or only the enterprise default?

Where Google names ages and Khan Academy names one, Microsoft's education documentation names licences and data terms instead, leaving the age decision to the school that switches the feature on.