Keep staff and student data apart.
Staff and student environments need different rules. We keep them apart, keep safeguarding evidenced, and move the servers you still run into Azure.
What schools, colleges and universities tell us.
“Students can see staff content.”
Separate governance models, sensitivity labels and hub-level sharing controls, with permissions reviewed against the audit log rather than assumed.
“Every school in the trust has its own setup.”
Multi-academy trusts often inherit one tenant per school. The cross-tenant consolidation approach we use for other sectors brings them into one estate with per-school governance.
“Our datacentre is end of life.”
Azure Site Recovery migration with hub-and-spoke networking, ExpressRoute and paired-region DR, delivered for a UK university.
“Copilot is coming and we are not ready.”
Classification first. Copilot can surface unlabelled student data to anyone who has access to it, so labelling comes before rollout.
The order we do it in.
We split the estates first, then classify the content, then move the infrastructure underneath.
The services that usually come first.
Managed Microsoft 365
Tenant, identity, Intune and a UK support desk, including Copilot agent identities.
From £14 per user per monthMicrosoft Azure
Azure set up, backed up and sized for the systems you run today.
Consumption plus management feeCopilot and agentic AI
Copilot readiness and Copilot Studio agents, with the Purview labelling that has to come first.
Readiness assessment from £3,200Talk to us about separating your estates
Take the free Cloud Modernisation Assessment: 18 questions, then your score and a personalised report on what to fix first.