Shared iPads Without Apple IDs — A Simpler Approach

Managed Apple IDs for every pupil sound tidy on paper. In a primary classroom of thirty children sharing six iPads, they're a daily support headache. Here's a simpler setup that's worked across our schools — using Apple School Manager and Intune, with no per-pupil sign-in at all.

The promise of "one Apple ID per child" rarely survives contact with a Reception class. Children forget passwords, devices get picked up at random, and a single forgotten sign-in can stall a whole lesson. For shared devices that move between hands all day, the goal isn't personalisation — it's a clean, identical, ready-to-go iPad every single time.

Why we moved away from per-pupil Apple IDs

We started where most schools do: Managed Apple IDs synced from our MIS, one per child. It worked — until it didn't. The failure points were predictable and constant:

• Password resets became a weekly job for a cohort that can't yet reliably spell their own surname.
• Slow handovers — signing out and back in between groups ate into lesson time.
• Storage sprawl — each ID carried its own iCloud data, and shared devices filled up fast.

None of this added real learning value. The children needed the apps, not an account.

The setup, end to end

1. Enrol every device in Apple School Manager

Buy devices through an Apple-recognised reseller so they land in your Apple School Manager (ASM) account automatically. This is what lets you supervise them and stops anyone factory-resetting their way out of management.

2. Link ASM to Intune and build an enrolment profile

Connect ASM to Microsoft Intune so new devices appear there on first power-on. Create an enrolment profile that does not turn on Shared iPad mode — that's the Apple feature that asks for a sign-in. We want the device supervised but account-free.

3. Push apps with volume licensing (no Apple ID needed)

Buy apps in volume through ASM and assign them to devices rather than users. Intune installs them silently. Because the licence sits with the device, there's no App Store prompt and nothing for a child to log into.

4. Lock down the experience

A configuration profile does the tidying: hide the App Store, disable account changes, set a clean home-screen layout, and switch on a kiosk-style restriction set for younger years. The iPad becomes a predictable appliance, not a personal device.

5. Reset between groups automatically

For devices that need a truly fresh slate each session, schedule an automated wipe-and-reconfigure outside lesson hours. The device re-enrols itself overnight and is identical by morning.

“The best shared iPad is a boring one — same apps, same layout, no surprises, no login.”

What you gain

• Zero sign-in support tickets — there's nothing to forget.
• Faster lessons — pick up any device and it just works.
• Easier audits — every iPad is in a known, identical state.
• Cleaner offboarding — no orphaned pupil accounts when children leave.

The trade-offs (be honest)

This isn't free of compromise. Without individual accounts you lose per-child work continuity — anything not saved to a shared, web-based platform (think OneDrive, Google Drive, or Seesaw) doesn't follow the pupil. For older students doing sustained, account-based work, Managed Apple IDs or 1:1 devices may still be the right call. Match the model to the age group and the task, not to a single tidy policy.

Worth doing?

For shared, lower-school devices, yes — comfortably. We cut iPad support tickets dramatically and gave teachers back the few minutes per lesson that sign-ins used to swallow. The setup takes an afternoon to design and pays for itself within a half-term.