HMS (Meta Horizon Managed Services): What Does It Actually Change?

In many organizations deploying Meta Quest headsets for training, virtual tours, maintenance, or collaboration, the same question arises when scaling up: how can a headset fleet stay under control without spending entire days configuring devices one by one?

That is exactly where HMS comes in. And since early 2026, HMS has also become a “hot” topic because Meta announced a major shift in its business offering.

What exactly is HMS?  

Meta Horizon Managed Services (HMS) is the “enterprise layer” that enables an organization to manage Quest headsets and work identities through an Admin Center, and to align devices with an IT management approach (deployment, restrictions, applications, etc.).

In simple terms, HMS helps move a headset from a consumer setup (personal account, manual management) to an enterprise-ready model that can be deployed and governed at scale across a company or school.

Key building blocks to remember:

• Admin Center: an administration interface to manage accounts and devices.
• Managed Meta accounts: accounts created and administered by the organization (instead of personal accounts).
• Bridge to an MDM: HMS can integrate with device management solutions (e.g., ManageXR) to push policies, control settings, and standardize the experience.

The real shift in 2026: Meta for Work is changing 

The most important point is not only what HMS is, but what Meta has announced about the future of this offering.

In a mid-January 2026 update, Meta notably indicated:

• The end of sales for certain parts of the “business” offer (Horizon Managed Services and certain Quest “commercial SKUs”) starting February 20, 2026.
• Starting February 20, 2026, Meta states that Meta Horizon Managed Services becomes free (US$0/month) for organizations: HMS licenses are no longer billed.
• Meta also indicates that Meta Horizon Managed Services will remain available until January 4, 2030 (for Quest 3 and Quest 3S), at which point the program reaches its end.

If an organization previously considered the Meta business package as a plug-and-play solution, the access model changes: it now requires thinking in terms of standard Quest devices + HMS/MDM governance + IT processes.

What changes for Learning & Development (L&D) or operational teams?  

a) Cleaner deployment, less “handmade”

Without governance, headset deployments often end up with:

• heterogeneous personal accounts,
• apps installed manually,
• unexpected updates,
• difficulty delivering the same experience across all devices.

HMS structures the organization layer (managed accounts + fleet connected to an Admin Center) and makes it possible to rely on an MDM to industrialize deployment.

b) A more stable learner experience (fewer distractions)

Enterprise deployments often aim to reduce:

• consumer-style interruptions,
• unwanted screens,
• non-compliant behaviors in a training context.

HMS + MDM integrations emphasize a more controlled “kiosk / managed home screen” experience and additional controls.

c) Clearer accountability between business and IT

As pilots become programs, the question is no longer only “Is the content good?” but also:

• who manages inventory?
• who defines usage policies?
• who controls updates and compliance?

HMS (via Admin Center) clarifies this perimeter and creates a gateway to IT tooling.

What changes for IT? 

a) A Meta administration reference point for the organization

HMS provides a control center (Admin Center) and a “managed account” model, rather than a stack of personal accounts.

b) A new Meta standardization layer

Several MDM resources describe HMS as the expected (or required) layer for business enrollment and access to management capabilities—depending on the MDM used and contractual context.

c) Roadmap and vendor-risk implications

Meta’s 2026 shift implies securing:

• the equipment strategy (standard fleet vs “commercial” fleet),
• dependency on a program described as evolving,
• the support trajectory.

Specialized media report the discontinuation of certain business components and a defined end-of-program horizon.

Practical impacts: what to check before deciding 

Checklist before going further

1. Eligible country: HMS is not available everywhere; check the official list.
2. Access model: based on Meta’s timeline, purchasing “HMS” as a product may no longer work as before; review Meta’s communication and your status (new vs existing).
3. MDM: decide whether the organization relies on a partner MDM (ManageXR, etc.) and which capabilities are needed (kiosk, restrictions, configuration…).
4. Internal governance: who administers, deploys, and supports the fleet?
5. Lifecycle: update policy, hardware replacement, account management.
   
   

FAQ 

Does HMS replace an MDM?

HMS is primarily Meta’s layer (Admin Center + managed accounts) and a gateway to enterprise governance. An MDM is often still needed for fine-grained device management (policies, kiosk modes, advanced settings), depending on requirements.

Is HMS free?

Meta and several ecosystem players have communicated that HMS moves to US$0/month starting February 20, 2026 for the relevant customers. The exact situation depends on status (new vs existing) and Meta’s current terms, so official Meta for Work information and partner channels remain the primary references.

Is Meta for Work stopping entirely?

Meta announces the end of certain business sales starting February 20, 2026, and specialized press points to an end-of-program trajectory. For equipment decisions, official Meta pages should be used and, if needed, guidance from an MDM partner or integrator.

Conclusion