Microsoft specialists

Every layer of your Microsoft estate, understood before it moves.

Technology change, made simple. Glaicier is a UK team of Microsoft specialists. We move organisations to Microsoft 365, make sure only the right people (and AI tools) can see what’s stored there, and build the cloud set-up underneath, for the NHS, the wider public sector and private organisations. Our own platform, Novalysis, does the heavy lifting from inside your own Azure subscription.

How we can help Meet Novalysis
  1. 04Ready for AIWhat Copilot would surface today, and what to fix first
  2. 03Who can see whatDown to the individual file
  3. 02Microsoft 365 movesWaves planned around teams and what they depend on
  4. 01The cloud underneathSecure Azure set-ups, research environments and sign-in
How we deliver
The engineers on the first call do the work
What we bring
Our own platform, Novalysis, built and used in production
Where your data stays
In your own Azure subscription, not a shared service
Who we are
A UK company, founded in 2024

What we do

For IT teams, the consultancies running the move, and NHS trusts on the Unite Programme. How we support Unite

What good looks like

Everyone can work on the Monday after the move.

Most migration plans are lists of objects: mailboxes, sites and accounts. People don’t work in objects. A referrals team works through a shared mailbox, a flow, a SharePoint list and an app, and if those move in different waves the team stops on Monday morning, even though every item passed its checks.

We plan each wave around teams and what they depend on, so the things that work together move together. Every decision about what moves, what stays and why is recorded, so it can still be found long after the project ends.

Read how a migration really goes

Migration teamTo: Referrals team

Wave 3 complete: referrals team

Your shared mailbox, the flow that files new referrals, your SharePoint list and the triage app moved together this afternoon. All four passed their checks.

Sign in as usual on Monday, and reply to this email if anything looks different.

Referrals teamChat

Monday

  1. Asha Kaur

    Morning. Is anything different today?

  2. Tom Reid

    New sign-in page. Everything else looks the same.

  3. Grace Obi

    Friday afternoon’s referrals are all in the app.

  4. Asha Kaur

    Great. I’ll take the first three.

Friday’s email, and the referrals team on Monday. Illustrative.

Who can see what

Security keeps fixing the same site.

Picture a site built around the org chart, with a library for each team. The people using it work on cases that cut across those teams, so to get a case in front of the right people they share a folder here and a file there. Inheritance breaks a little more each time. Security finds hundreds of unique permissions, raises a ticket and resets them. Six months later they’re back.

The site follows the org chart and the case work doesn’t. Until that work has a place of its own, with permissions set for the people who do it, each reset starts the clock again.

A move off SharePoint Server is the best chance to fix it, because the new sites don’t exist yet. Before anything moves, we map who shares work with whom on the old farm and draw the new sites around those groups.

In NovalysisIn SharePoint Online, Novalysis works through each site’s permissions down to the item and inventories its sharing links. Where the files in a folder keep being shared with the same few people, it treats them as a working group. Then it suggests where that work belongs: a private team in Microsoft Teams, a restricted library, or a space shared with the department they work with.

How the site is organised

  • Operations site
    • Finance
      • Case 4471, unique permissions
      • Budgets
      • Case 4519, unique permissions
    • Clinical
      • Case 4471, unique permissions
      • Case 4502, unique permissions
      • Policies
    • Admin
      • Case 4502, unique permissions
      • Rotas

Unique permissions

Who actually works together

Working group

Case 4471 in Clinical: files shared one by one with the same 6 people, from Finance and Admin as well as Clinical

Suggested A private team in Microsoft Teams for case work

How the site is organised, and who works together. Illustrative.

Getting ready for AI

Copilot finds whatever your permissions allow.

Copilot answers from anything the person asking can open. On a site where permissions have drifted, that’s a lot of documents they were never meant to see, which until now stayed out of sight only because they were hard to find.

It’s the SharePoint problem again, one question away, so making Copilot safe starts with the site structure.

In NovalysisNovalysis scores each site for Copilot readiness and gives its owner a plan of what to fix. Causes that sit in tenant settings, such as the default sharing link, are picked out separately, because fixing those site by site only lets them grow back. Copilot then goes to each department as its sites are ready, announced with the same campaigns and staff page as a migration or an MFA rollout.

What changes are planned for our department?

Three restructure options are under discussion. The second would merge your team with Admin from the spring.1

1Restructure options - board only.docx

Operations site › Clinical › Case 4471 › Restructure options - board only.docx

Shared with Everyone except external users when inheritance was broken on this folder

An answer citing a file shared with everyone through a broken permission. Illustrative.

Where it runs

Novalysis runs in your own Azure subscription.

Your data, plans and decisions stay with you, not in a shared service, so nobody needs a copy of your Microsoft 365 data on their laptop to plan the move.

How Novalysis handles your data

Glaicier

  • Gateway for sign-in and routing
  • Licences and entitlements
  • Operational logs, 30 days, UK
  • Daily usage counts
API calls pass through; content not stored

Your Azure subscription

  • Function Apps
  • Azure SQL, Entra-only
  • Azure OpenAI and AI Search
  • Key Vault
  • Private endpoints

Your tenant data, plans and decisions are stored here

NHS.net Connect · Unite Programme

The trust side of Unite, carried for you.

The Unite Programme moves your organisation into NHS.net Connect, the shared NHS Microsoft 365 service formerly known as NHSmail. The programme moves your information, and a substantial body of work stays with you: identity, permissions, licence decisions, Power Platform and Forms, and everything that decides how the Monday morning feels. That is the work we carry alongside your team.

How we support Unite
  • The programmeFunded migration of information into NHS.net Connect.
  • Your organisationOwns the decisions, the evidence and the sign-off.
  • GlaicierCarries the trust-side workload alongside your team.

We plan the move. Your migration tool does the moving.

Quest, ShareGate, BitTitan and CodeTwo do it well, and most organisations we talk to already have one. We don’t compete with them. Our work comes before the move: what to leave behind, what needs special care, and the order that lets people keep working. Novalysis flags the mailboxes, sites and Teams nobody has used in months, and the desktop Office licences going unused, so whatever you leave behind or scale down is a decision someone made and recorded.

  1. Decide in Novalysis what moves, what stays and when
  2. Sign off each wave and export it in your tool’s import format
  3. Move it with Quest, ShareGate, BitTitan or CodeTwo

Who we work with

  • NHS acute hospitals and foundation trusts
  • NHS ambulance services
  • The wider public sector
  • Private sector organisations

Before you move it, find out what it’s holding up.

Bring us a migration, a site security keeps fixing, or a Copilot rollout you’re not sure about. The first call takes about 30 minutes, with no slides, and the engineers on it are the ones who’d do the work.

Get in touch [email protected]