For about a decade, the deal in Apple Business Manager was simple: you bought an app once, you got a license, and you handed that license to a person or a device. Reclaim it when they leave, hand it to the next person. Clean. A library card system — the book goes back on the shelf.
As of October 23, 2026, that same Apps and Books workflow can now buy auto-renewable subscriptions in volume. Apple calls it multiseat purchasing. The pitch, stated and implied, is that subscriptions now behave just like the licenses you already know how to manage. Let’s pressure-test that, because the word “renewable” is doing a lot of quiet work.
Is it really the same workflow?
Mostly, yes — and that’s the genuinely useful part. You discover eligible subscriptions in the same place you buy everything else, you buy a quantity of seats, and you distribute them through your MDM to either a managed Apple ID (user assignment) or a device (device assignment). No new console, no separate contract portal, no per-user App Store receipts to chase. If you can run Apps and Books today, you can run this.
The old pattern this replaces was ugly. When an app moved to a subscription model, enterprise admins were left with two bad options: tell every user to subscribe with a personal payment method and expense it, or build a shared-account workaround that skirted Apple’s intended use policies and broke the moment someone enabled two-factor properly. Both were reimbursement nightmares and neither scaled. Killing that is worth the headline on its own.
So where does “just like a license” break down?
Here’s the shelf-versus-stream distinction. A one-time license is a book. A subscription seat is a water meter — it’s only worth anything while it’s turned on, and the bill arrives again every cycle whether or not anyone drank.
That changes the reclamation math. With a perpetual license, an unassigned seat sitting in your pool costs nothing; it’s inventory. With a subscription, an unassigned-but-still-paid seat is pure waste until you either reassign it or let it lapse at renewal. Reclaiming the seat from a departed user is now the beginning of the decision, not the end. You reassign fast, or you right-size the quantity at the next renewal boundary. Nobody reclaims a subscription seat to put it back on a shelf. There is no shelf.
So the operational muscle you need isn’t new tooling — it’s a renewal calendar and someone who owns it. The failure mode six months out is predictable: 240 seats purchased, 170 actually assigned, and a finance team asking why the invoice didn’t shrink when headcount did.
Which apps actually offer this?
This is the asterisk the headline won’t tell you. Multiseat subscription purchasing is opt-in for developers. An app’s subscription is only buyable in volume if its publisher has enabled it. On day one that is a short list, and you have no way to force a vendor onto it. Before you redesign any procurement process around this, go into Apps and Books and confirm the specific subscription you care about actually appears as a volume-eligible item. If it isn’t there, none of the above applies to you yet — you’re still on the personal-subscription-and-expense-report treadmill for that title.
User seat or device seat?
The same two assignment models carry over, and the choice matters more with subscriptions. Device assignment binds the seat to hardware — sensible for shared iPads, kiosks, and lab Macs where the person changes but the device doesn’t. User assignment binds it to a managed Apple ID and follows the human across their devices — sensible for a named professional who needs the app wherever they sign in. When that person offboards, deprovisioning their managed Apple ID is what frees the seat. Which means your Entra or Okta offboarding flow is now also your subscription cost-control flow. Wire them together, or don’t be surprised by the bill.
The honest verdict: Apple didn’t just extend volume purchasing to subscriptions, it extended the responsibility. The buying got easier. The not-wasting-money got harder, and it now lives in your identity lifecycle, not your app catalogue.