Microsoft 365 for
independent schools and FE / HE.
Safeguarding-aware Copilot governance. Parent and student communications that scale. MIS integration done properly. Teams in education tenants configured for the realities of school life rather than corporate office work.
E
What we build for UK
education clients.
Education is a sector with its own technology context: Microsoft Education licensing rather than commercial, specific safeguarding considerations, a young user population, MIS systems at the core of operations, and a relationship with parents and students that adds two more stakeholder groups to every project.
Student services and pastoral workflows
Pastoral case management, behaviour incident reporting, attendance follow-up, exam concession applications, careers and progression. Power Apps and Power Automate with the appropriate access controls (pastoral content is more restricted than academic), audit trail safeguarding demands, and MIS integration.
Parent and student communications
Branded communication workflows for parents (newsletters, term-time announcements, individual student updates) and students (calendar updates, assignment reminders, careers content). Power Automate workflows, Power Pages or M365 group emails for distribution.
Teams and SharePoint governance for education tenants
Microsoft 365 Education tenants need different governance than commercial tenants. Student Teams have different requirements than staff Teams. Safeguarding affects guest access. Younger users have GDPR considerations. We design the baseline specifically for education.
Safeguarding-aware Copilot governance
Copilot in education is more complex than in commercial environments. Governance accounts for student data (special category under GDPR), safeguarding records (highly sensitive), KCSiE statutory framework, and a population that includes minors using the tools their teachers use.
The standards and regulators that
shape this work.
Keeping Children Safe in Education (KCSiE)
Statutory safeguarding framework for schools and colleges in England. The Microsoft 365 configuration and Copilot governance both account for KCSiE.
GDPR + Age Appropriate Design Code
Enhanced considerations for under-18 data. Consent considerations differ for under-13s and 13-to-18s. Higher data minimisation discipline.
Inspection frameworks
ISI for independent schools, Ofsted for state and academy, Education Scotland, Estyn, ETI. Inspection readiness documentation lives in the Microsoft estate in findable form.
M365 Education tenant
A1, A3, A5 plans, the interaction with commercial licences for finance/admin staff, data handling specific to education tenants.
JCQ examinations
Examinations integrity regulations, workflows for access arrangements and concessions, document retention requirements.
HE-specific (OfS, QAA, Prevent)
For HE clients: Office for Students regulations, QAA quality framework, Prevent duty considerations, OIA complaints handling.
Fixed-price packs that
fit this sector.
The Cloudbliss services that
fit this sector.
Our previous setup had pupils accidentally in staff Teams. Cloudbliss rebuilt the tenant with proper boundaries and gave us a Copilot policy our DSL was happy to sign.
Things sector leaders
actually ask.
For most staff in independent schools and colleges, A3 is the right answer. A5 is justified where the school or college has serious security or compliance pressures (some independent schools opt for A5 because of higher safeguarding requirements). A1 is free and is fine for student use in many contexts. We help map this during the Licence Health Check.
Yes, with caveats depending on the platform. SIMS (ESS) and Arbor have well-documented APIs that support deeper integration. Bromcom has improving API coverage. iSAMS has API access through their partner programme. For the parts of the MIS without API support, we use scheduled exports or Power Automate flows that work against the export data.
Sensitivity labels for safeguarding records (the highest classification, with restricted access and audit logging). Conditional access policies that limit where safeguarding content can be accessed from. Designated safeguarding lead access controls. Retention policies aligned to safeguarding records retention requirements. Audit logging that supports incident investigation.
Microsoft 365 Copilot is available for education tenants but with specific considerations for student use. Copilot for staff use is broadly available under appropriate governance. Copilot for student use is subject to more careful scoping and parental consent considerations, especially for under-18 students. We help schools design a Copilot strategy that fits both educational ambition and safeguarding duty.
Several patterns. For schools using a dedicated parent platform (ParentMail, MyEd, Arbor's parent portal), we integrate from Microsoft 365 rather than replacing it. For schools wanting to build the parent communication on Microsoft 365 directly, we use M365 group emails for distribution and Power Pages parent portals for self-service content.
Teams in education is a different governance challenge to Teams in commercial environments. We configure Teams for education tenants with appropriate guest access controls, retention policies, and monitoring. The class team pattern, the student club pattern, the parent communication pattern, the pastoral team pattern, all have different governance.