Deploying Meta Quest headsets at work used to come with a mandatory per-device license fee for Horizon Managed Services — as of February 20, 2026, that fee is zero. HMS is what made that fee mandatory in the first place — without it, organizations had no way to centrally enroll, configure, or control Quest devices at scale. That turned the license cost into the first real barrier for enterprise deployment. The fee is gone.
What Is Meta Horizon Managed Services?
Meta Horizon Managed Services is the software layer that turns a consumer Quest headset into a managed enterprise device. It handles MDM enrollment, work identity management, app distribution, and policy control — the infrastructure an IT team needs to deploy headsets across a workforce rather than hand-configure each one individually. Without it, Quest is just consumer hardware.
In practice, that means an IT administrator can enroll a new headset remotely, push the approved app catalog automatically, enforce usage policies, and wipe or reassign devices without ever touching the hardware. The headset arrives, connects to the network, and is ready for work. That workflow — invisible to the end user, essential to the IT team — is exactly what HMS enables.
The distinction matters in practice. A single Quest on someone’s desk is a device. Fifty Quests across a distributed team, each enrolled, provisioned, and policy-controlled from a central console, is infrastructure. HMS is what makes the second thing possible — and as of February 20, that capability carries no per-device subscription cost.
What Just Got Cheaper — and What Didn’t
The fee that disappeared is specifically the HMS license. As of February 20, Meta removed per-device licensing costs entirely — organizations can now activate HMS through the portal at forwork.meta.com at no charge. That covers enrollment, identity management, app distribution, and policy control.
Hardware costs did not change. A Meta Quest 3 still runs roughly $500 per device, and Meta’s pricing for consumer hardware is unaffected. Per the January announcement, Meta also discontinued its commercial Quest SKUs on the same date — a shift that does not favor enterprise teams. Consumer Quest 3 devices remain fully enrollable in HMS, so organizations can still buy and manage them.
Third-party MDM tools like ManageXR and ArborXR remain a separate cost. Those vendors have publicly confirmed continuity, so HMS-free does not pull the rug from existing deployments. The concrete win is narrower than the headline suggests: pilot fleets and education organizations that were paying per-device licensing fees now carry none of that overhead.
To put a number on it: a ten-headset pilot that previously required HMS licensing now has that line item at zero. The hardware spend is unchanged, and any third-party MDM subscription stays on the invoice. But the software barrier to enrollment — the one that required a recurring commitment before a single meeting was held — is gone. The scope of the change is specific, and so is the benefit. For teams that were stalling a pilot on that specific cost, the stall is over.
What “Maintenance Mode Through 2030” Actually Means
Maintenance mode, as ManageXR describes it, means “bug fixes and support, but no new platform capabilities.” HMS will keep running — it will receive patches, it will remain supported — but Meta will not extend or expand the platform. According to ManageXR, Meta is unlikely to deliver feature requests that depend on new or expanded APIs.
What maintenance mode does not mean is a cutoff. Device enrollment continues without disruption. Organizations already running HMS alongside ManageXR or ArborXR can keep doing exactly that, and ManageXR has stated as much explicitly. The infrastructure your team built on HMS keeps working until January 4, 2030.
Four years is a real planning horizon. For most enterprise VR evaluations — proof of concept, departmental pilot, measured rollout — that window is long enough to validate ROI and make an informed migration decision before the deadline arrives. The runway is not infinite, but it is sufficient.
Beyond 2030, Meta has made no commitments. Inside that ecosystem, MDM vendors say they will adapt and communicate as clarity emerges — but that clarity does not exist yet. The practical move is to treat 2030 as your evaluation deadline. Plan the assessment inside the maintenance window, reach a decision before it closes, and avoid building anything that depends on HMS expanding beyond what it does today.
What This Means for VR Meetings
The team that has been waiting for the right moment to pilot VR meetings now has a specific thing to point at. With HMS free, the software management cost for a small meeting fleet is zero — enrollment, policy control, and app distribution. That is a real line item removed from the pilot budget.
Hardware cost is unchanged. A Quest 3 still runs roughly $500 per device, and nothing in the HMS announcement touched that number. The total cost of a meeting fleet did not collapse; one layer of it did.
The field those teams would be entering has also narrowed. Horizon Workrooms shut down on February 16, 2026, and MeetInVR has announced it closes April 30, 2026. At the same moment the deployment barrier dropped, the platforms built around the meeting use case consolidated.
That consolidation changes the evaluation. A year ago, an enterprise team comparing VR meeting platforms had several options, including ones backed by Meta’s own enterprise division. That division is gone. The comparison set is smaller now, but the platforms still standing built their entire product around the meeting use case — they were not hedging on it. For teams evaluating now, the field is cleaner and the commitments are clearer.
What remains are the platforms that treat immersive meetings as a primary product — not a feature bundled into a broader enterprise suite. The infrastructure HMS provides is exactly what those platforms run on: enrolled devices, managed identities, controlled app distribution. For a team deciding where to put that infrastructure to work, the full case for what VR meetings actually change is the right place to start.
If your team has been considering VR meetings, or has Quest devices sitting underdeployed, the window to run a real pilot has become materially cheaper to open. The management overhead is gone. The hardware commitment is the same as it always was — but a fleet that was stalled on software cost now has no software cost to stall on. raum.app is built for exactly this use case: professional, fully-immersive VR meetings for distributed teams. [Start there.]([raum.app product page URL])
Frequently Asked Questions
What is Meta Horizon Managed Services?
Meta Horizon Managed Services is the software layer that enables enterprise and education deployment of Meta Quest devices at scale. It covers MDM enrollment, work identity management, app distribution, and policy control — the infrastructure an IT team needs to manage a fleet rather than configure each headset individually. Until February 20, 2026, that capability came with a mandatory per-device subscription fee. As of that date, the license is free.
Is Meta Horizon Managed Services actually free now?
Yes — as of February 20, 2026, HMS carries zero license fees. Organizations can activate it through the Meta for Work portal at forwork.meta.com at no charge; Meta confirmed this in the January announcement. Hardware costs are unchanged: a Quest 3 still runs roughly $500 per device. If your deployment uses third-party MDM tools like ManageXR or ArborXR, those remain a separate cost.
What does “maintenance mode” mean for my VR deployment?
Maintenance mode means bug fixes and support continue, but Meta will not add new platform features or expand HMS APIs. Existing device enrollment, identity management, and app distribution workflows keep running without disruption — nothing your team has already built will break. This is a stability commitment, not an end-of-life notice. The maintenance window runs through January 4, 2030.
What happens to HMS after 2030?
Meta has made no commitments about the platform beyond January 4, 2030. MDM vendors like ManageXR and ArborXR have stated they will adapt to whatever Meta does next and will communicate as clarity emerges — but that clarity does not exist today. For organizations piloting VR now, a four-year supported window is substantial runway to validate ROI and reach a migration decision before the deadline. The practical move is to treat 2030 as your evaluation deadline, not a cliff.
Who benefits most from HMS being free?
The organizations that benefit most are those for whom the per-device licensing cost was the specific thing blocking action. Enterprise teams running pilots can now enroll and manage a proof-of-concept fleet without recurring software overhead. Education and training organizations gain the most in raw dollars — HMS licensing was a meaningful per-device line item for schools and L&D programs on constrained budgets. Small teams trying VR meetings for the first time have less administrative overhead to start and nothing to cancel if the pilot does not stick. Organizations with Quest devices already on hand but underdeployed can now enroll and manage that hardware at no additional software cost.