Meta Quest for Business is being wound down. Since February 20, 2026, Meta no longer sells commercial (Work/Edu) Quest 3 and Quest 3S SKUs and no longer accepts new sign-ups for Horizon Managed Services, its enterprise device-management subscription. Existing subscriptions drop to $0 and stay usable until the program's full shutdown on January 4, 2030. If your company trains staff on Quest headsets, or is about to start, here is exactly what changed and what to do about it.
What Meta actually changed
Three separate things ended together, and it is worth untangling them because they matter differently to a training rollout:
- 1Commercial hardware SKUs. The dedicated "Work/Edu" variants of Quest 3 and Quest 3S (sold with business terms and support) are no longer available to purchase.
- 2New Horizon Managed Services subscriptions. HMS, Meta's MDM subscription (previously $15–24/month per device for individual or shared modes), stopped accepting new customers.
- 3Horizon Workrooms, Meta's enterprise meeting-room product, was discontinued around the same time.
What did not change: existing HMS customers keep access, at $0/month, through January 4, 2030, and current hardware keeps working. Source: Meta, "An Update on Meta for Work" (2026).
Why now
Meta's own explanation is that it is "increasing focus on building the world-class first-party consumer hardware and software needed to advance the virtual reality market". In plain terms: doubling down on consumer Quest rather than a separate enterprise line. Independent reporting frames it as part of a broader strategic pivot toward Ray-Ban Meta smart glasses, alongside Reality Labs staff reductions, the closure of three VR game studios (Twisted Pixel, Armature, Sanzaru Games) and no new Quest headset launch in 2025. Source: Forbes, January 2026.
Not the same as "Meta is leaving VR"
Meta is not discontinuing Quest hardware itself — Quest 3 and 3S remain on sale and supported for consumers. What ended is the separate enterprise commercial program built around them.
Before vs. after, at a glance
| Before Feb 20, 2026 | Now | |
|---|---|---|
| Hardware you buy | Commercial "Work/Edu" Quest 3 / 3S SKU | Standard consumer Quest 3 / 3S |
| Warranty / support | Business terms, dedicated support | Standard consumer terms |
| Device management (HMS) | New subscriptions open, $15–24/month/device | No new subscriptions; existing ones $0/month until Jan 4, 2030 |
| Horizon Workrooms | Available | Discontinued |
What this means if you buy headsets for training
For a company evaluating VR safety or skills training, the practical consequences are narrower than the headlines suggest:
- You can still buy Quest 3 / Quest 3S — just the standard consumer version, at consumer retail pricing, without a bundled business warranty or a Meta-run support line.
- You lose the option to start new Meta-run centralized MDM through HMS. Companies that already use Microsoft Intune, VMware Workspace ONE or Ivanti UEM alongside HMS keep those integrations for now, per the transition terms; new HMS sign-ups are what's closed. Source: UploadVR, "Meta Is Shutting Down Its Quest For Business Program" (2026).
- Warranty and support now follow Meta's standard consumer terms rather than a business SLA, which matters for fleets of 20+ headsets that previously relied on business-grade replacement turnaround.
None of this blocks running VR training. It changes who is responsible for device management and support once you buy the hardware.
Where LMS-level device management already covers the gap
Meta's HMS was one layer of headset management (screen locking, app allow-lists, remote wipe). It is a different layer from training device management: knowing which headset ran which course, for which employee, with which certificate issued. That layer was never Meta's job.
On Skillsive, a headset is added to your organization by signing the EHS Academy app (downloaded like any consumer app from the Meta Store) into Organization → Devices with a one-time code, independent of HMS. Course assignment, seat usage, completion tracking and certificates run entirely in the Skillsive panel, so companies that never subscribed to HMS in the first place are unaffected by its shutdown. See connecting a VR headset to Skillsive for the exact steps.
If your team specifically needs OS-level kiosk lockdown on shared devices (blocking the Meta Store, Wi-Fi settings, etc.), that is now a gap Meta itself is not filling for new customers. It is worth confirming directly with your MDM vendor of choice, or with other headset makers' current enterprise programs, before you commit to a device count.
It is also worth remembering that a training rollout does not have to be single-headset-vendor. Skillsive's own courses run on Meta Quest, Pico and HTC Vive Focus headsets, so if centralized device management ends up mattering more to your IT team than any one manufacturer, the decision is a device-management one, not a training-content one: the same courses and completion records follow the employee regardless of which headset they used.
Practical steps for a rollout starting now
- 1Buy consumer Quest 3 or Quest 3S: same hardware, same performance, no business SKU required.
- 2Set your budget for standard consumer warranty terms, not the business SLA that used to come bundled. Factor in a slightly higher device-failure buffer for larger fleets.
- 3Manage courses, completions and certificates through your training platform's panel, not through HMS. This was already the correct architecture for a fleet used mainly for training rather than general office productivity.
- 4If shared-device lockdown matters, evaluate it as a separate MDM decision rather than assuming it comes with the headset purchase.
- 5Start small. A pilot with a single consumer headset and one course from the applications catalog tells you within days whether the training content works for your team, before you decide on fleet size.
The bottom line
Meta Quest for Business is gone as a purchasing category, not as a training platform. The headsets are still on sale, still supported for consumers, and still perfectly capable of running VR safety training. You now source device management and support separately from the LMS that runs your courses, which for most training-focused deployments was already the sane split.
