SkieHow do you freeze provisioning for an organisation?
An owner can freeze an organisation, which blocks new provisioning while devices that are already enrolled keep working and keep their rules. It is used when you suspect someone is trying to enrol devices they should not, or when a licence or a rollout needs to pause. Lifting the freeze allows new enrolments again.
Provisioning is the moment a new device joins your organisation, so it is the moment worth protecting. If a token leaks, a sign-in is shared by mistake, or someone starts enrolling devices that are not meant for the school, you want a quick way to say stop. The freeze is that switch.
While an organisation is frozen, new provisioning is blocked at the licence and readiness checks. Both the laptop route and the Provision app stop with a reason. Devices already provisioned are unaffected. They keep syncing, enforcing the rules they have and reporting compliance, so a freeze does not disturb the school day.
The freeze is a control for the owner side and for the administrators the organisation has authorised. Its purpose is calm. You freeze, look at the audit log and the device list for anything you did not expect, fix the sign-ins, and unfreeze. Skie's audit log records who did what.
A related but different switch is panic lock, which locks all devices at once. Freezing is about adding devices. Locking is about the devices you already have. Use them for different problems.
Practical tip: after a freeze, tokens created earlier for devices that have not been provisioned should be treated as stale, and you should create fresh ones when you resume. For related controls see role based access and what to do if a token fails.
- Blocks new provisioning only
- Enrolled devices keep working
- Different from panic lock
- Audit log shows what happened