A Practical Guide to the Meta HMS Changes for XR Teams

Meta announced changes to HMS and commercial Quest SKUs, sparking questions and misconceptions. Here’s what changed and what XR teams need to know.
calendar-solid
January 22, 2026
tags-solid
Hardware
Meta Quest
News
VR
Quest
Smiling man with short dark hair and beard wearing a black shirt against a blue circular background.
by
The Organization
The Problem
The Solution

On January 15, 2026, Meta announced major changes to how Horizon managed services (HMS) and commercial Quest SKUs will work.

On January 15, 2026, Meta announced that Horizon managed services (HMS) and commercial SKUs of Quest devices will soon no longer be available for purchase. Since this announcement, the XR industry is abuzz with questions about what this means for the future of VR programs, what teams using Meta devices can expect from Meta for support, and more.

We’ve spoken with our customers, ISVs, and partners to understand the most common questions XR teams are asking about these changes to Meta HMS. In this blog, we’ll cover these top questions and take a look at what lies ahead.

What Changed With Meta HMS?

Here are the facts:

HMS Is Free

Starting February 20, 2026, Horizon managed services will be free. Organizations will no longer pay licensing fees to enroll Quest devices into MDM platforms like ArborXR.

Critical point: HMS is not going away. It remains required for all Quest device enrollment. The technical process stays the same. Only the cost changes.

HMS Is Entering Maintenance Mode

Meta will support HMS in maintenance mode through January 4, 2030. This means:

  • No new features or development
  • Security updates expected to continue via Meta's OS update process
  • Reduced support from Meta's enterprise teams
  • No commitment on what happens after 2030

This is an end-of-life product. Meta is no longer positioning HMS as a reliable long-term device management platform for enterprise.

Commercial SKUs Are Gone

Meta will stop selling enterprise or commercial Quest SKUs. All Quest hardware will be sold as consumer units. This means customers can purchase Meta Quest headsets wherever and enroll them in ArborXR. Some resellers may offer third-party warranties and support, but the commercial SKU from Meta that included a 3-year commercial warranty and support is going away. 

Context: There was never a hardware difference between commercial and consumer Quest devices. The distinction was how Meta marked serial numbers in their system. Consumer devices have always supported enrollment into enterprise MDMs like ArborXR through HMS.

Clearing Up Misconceptions

These changes created confusion. Let’s address the misunderstandings we’re hearing from XR teams.

Misconception: HMS is going away

Reality: HMS remains mandatory for enrolling Quest devices into any MDM platform. The enrollment process is not changing. HMS is becoming free and entering maintenance mode.

Misconception: Consumer devices cannot be managed in enterprise

Reality: All Quest devices, wherever purchased, can be enrolled via HMS into enterprise MDM platforms. The consumer SKU is a pricing and distribution change, not a technical limitation.

Misconception: Free HMS means free device management

Reality: Free HMS signals that this product is now an end-of-life product. Yes, HMS is free but now organizations need to consider eligibility, procurement, and support issues. We regularly hear that HMS is frustrating to use for management and has bugs and quirks that make it less than stable. These issues won’t go away and it’s expected that management functionality will only degrade over time as minimal/no engineering resources and no new features are planned.  In addition, organizations needing support of any kind from Meta for HMS management use won’t have any options. 

Misconception: Meta is exiting VR

Reality: Meta remains committed to VR. Their focus is consumer VR, AI wearables, and AR glasses. They have 13,500 employees in Reality Labs. Enterprise VR is not their strategic priority. They are asking partners like ArborXR to fill the enterprise support gap.

Disclaimer: The information on this blog represents what is known as of publishing (January 22, 2026). We will continue to update this blog as more information becomes available from Meta and our partners.

Common Questions From Enterprise XR Teams

Below, we cover the most frequently asked questions from enterprise XR teams about the changes to Meta HMS, how these changes impact XR programs, and what it means for ArborXR users.

1. Now that HMS is free, should I consider using it for managing my devices?

HMS is free, but it’s not a fully reliable solution moving forward. It’s limited to Meta devices, has minimal support, and is in maintenance mode with no new features until it ends in 2030. 

ArborXR is a fully featured, actively developed MDM for all XR devices. You get more control, better device and content management, analytics, security, and real human support. So while HMS can get you started, ArborXR is built to scale.

2. What does Meta moving HMS into maintenance mode mean for enterprise XR programs, in practical terms?

After February 20, Meta will no longer provide direct enterprise support for HMS. Support is limited to basic maintenance until January 4, 2030. This means no feature updates, major patches, or roadmap expansion. 

IMPORTANT: For device enrollment, HMS remains required for enrolling devices into ArborXR. However, HMS on its own is no longer positioned as a fleet management solution for enterprise XR programs.

3. Does Meta still provide enterprise-level support for HMS-related issues after the February 20 deadline?

For ArborXR customers, we expect continued support on the Meta side for devices enrolled in ArborXR through HMS. This includes OS and security updates. 

ArborXR will continue to be an official integration partner with direct lines of communication with Meta. 

For other organizations using HMS to manage headsets, support will be minimal. Meta has shared publicly that they will fulfill existing contract obligations, but HMS will be in maintenance mode until the platform’s end-of-life in 2030. 

4. What happens to enterprise XR programs after Meta’s stated 2030 support horizon?

At this time, we don’t have direct information from Meta on what happens after 2030. Our internal expectation is that Meta will find a graceful path for enrolling Meta Quest devices into MDMs like ArborXR as long as they continue to sell Meta Quest headsets. That being said, we don’t have any guarantee of this, and it’s possible that it could change down the road.

5. Can existing Meta Quest devices continue operating without paying Meta any ongoing HMS fees?

Yes, HMS will be free for new and existing Meta Quest device owners after February 20, 2026.

6. Are net new customers able to enroll devices into HMS after February 20, 2026?

Yes, new customers will be able to purchase Meta Quest headsets from anywhere and enroll devices using HMS for free. 

7. Will devices enrolled via HMS into ArborXR continue receiving Meta OS and security updates?

Yes, devices will continue to receive Meta OS and security updates.

8. Is HMS still required for device enrollment into ArborXR? Can I enroll devices directly into ArborXR? 

For Meta Quest devices, HMS remains the enrollment bridge into ArborXR.  

It is not possible to bypass HMS and enroll devices directly into ArborXR. Much like Apple Business Manager facilitates the enrollment of Apple devices into MDMs, HMS facilitates the enrollment of Meta Quest devices into partner MDMs like ArborXR. 

After enrollment, HMS is not needed for device management. ArborXR becomes the system of record for device configuration, content delivery, updates, and fleet operations.

Learn more about enrolling Meta Quest via HMS.

9. What is the difference between HMS management features and ArborXR?

HMS provides basic device management for Meta headsets. It’s free, but limited. This means few features, minimal support, no cross-device compatibility, and no new updates until it ends in 2030.

ArborXR works across all XR devices and gives teams more control, flexibility, and reliability:

  • Device management: location tracking, remote reboot, nested groups
  • Content management: version control, release channels, scheduled installs, remote launch
  • In-headset experience: custom environments, 360 backgrounds, in-VR single sign-on
  • Analytics: LMS and BI integrations for reporting and ROI
  • Enterprise security: kiosk mode, Wi-Fi certificates, remote wipe, casting, and more
  • Support: real humans to help with troubleshooting, content, and hardware decisions

HMS can get you started, but ArborXR is built to scale, manage larger fleets, and support more complex XR programs.

10. Should enterprise teams delay purchasing new Quest headsets until after February 20 to avoid added costs?

If you are able to purchase Meta Quest devices through retail channels or through a reseller, devices will already carry the consumer SKU. You might save more money by waiting until after February 20.

Important to note, the commercial SKU Meta Quest that you can purchase through channel is only available until Feb 20th. After that, only consumer SKU Meta Quest devices are available. These don’t include a commercial warranty or commercial support from Meta.

Warranties and support may be available from resellers such as VR Expert, Bloom, and CDW after February 20. For more information, please reach out to our team and we can help connect you to the right resource. 

11. Are consumer Quest SKUs fully manageable for enterprise use after the HMS change?

Yes. Consumer Quest SKUs can be enrolled in ArborXR through HMS and at that point are fully manageable for enterprise use.  

It is important to note the consumer SKU does not include a commercial warranty or support. Third-party support and warranties may be offered by resellers and we’ll update this resource as we get more information. 

In general, we are now recommending enterprise teams look to other OEMs (like PICO) to build stable XR programs. 

12. How do these Meta updates impact Shared and Individual modes? 

Shared Mode and Individual Mode remain unchanged. 

When enrolling devices into ArborXR via HMS, your configuration choice determines whether the device operates in Shared Mode or Individual Mode.

  • Shared Mode: Triggered automatically when you configure devices to ArborXR Home or ArborXR Kiosk Mode.
  • Individual Mode: Triggered when devices are left in the default Device Home Environment.

It is important to note that the on-device Meta Horizon App Store cannot be accessed while devices are configured to Shared Mode. 

Learn more about Shared Mode and Individual Mode. 

13. Does ArborXR support casting? 

Yes. With ArborXR you can cast one or multiple devices over Wi-Fi (we call this feature “Remote View”). You can also remotely launch apps or videos to multiple headsets at once with one click. 

Learn more about casting.

Learn more about remotely launching content. 

14. Will ArborXR continue developing features for Meta Quest despite HMS being in maintenance mode? 

Yes, ArborXR remains fully committed to supporting Meta Quest devices. Because our platform operates at the Android system level, we are not solely dependent on Meta’s proprietary APIs for our core functionality. This allows us to continue building and releasing powerful features that work seamlessly across all supported devices, including the Quest.

However, there is a distinction regarding Quest-specific settings:

  • General Features: We will continue to develop and launch new features that improve your overall device management experience.
  • Device-Specific Settings: Because HMS is now in maintenance mode, Meta is no longer releasing new APIs for partners to control bespoke device settings. As a result, we likely won't be able to develop new features that specifically control or configure internal Meta-only settings.

In short: You can expect the same robust ArborXR experience you have today, and we will continue to innovate on everything within our control to ensure the Quest remains a first-class citizen in the ArborXR ecosystem.

15. Are there any new device restrictions, enrollment hurdles, or regional limitations enterprises should plan for?

No new restrictions were announced as part of the HMS change. In regions where only consumer Quest headsets were available, those devices can now be used for enterprise programs. Availability does not change in regions where Quest headsets are not sold.

16. What procurement, warranty, and lifecycle strategies should enterprises adopt without an enterprise Meta SKU?

When purchasing consumer Quest devices, they include a limited one-year consumer warranty. For enterprise use, we recommend purchasing through a channel partner such as VR Expert, Bloom, or CDW, who can provide extended warranty options and enterprise-level support.

We encourage teams to reach out to us directly so we can help facilitate an introduction to the right channel partner based on your deployment needs.

17. How should enterprise XR teams interpret this change in Meta’s broader XR strategy and long-term commitment?

The changes to Meta HMS and Meta Quest signal a return to a consumer-first focus. Meta is prioritizing consumer XR and increasing investment in AR and AI wearables. This does not indicate Meta is exiting XR hardware or abandoning the Quest platform. The Meta Raybans have been a hit and Meta is scaling production to an estimated 20,000 devices in 2026. 

Meta Quest headsets continue to see strong adoption across both consumer and enterprise use cases. Meta appears committed to building competitive XR hardware, but not to owning the enterprise management layer. For enterprise teams, this reinforces the need to plan around third-party platforms for device management, content distribution, and long-term program stability rather than relying on Meta to provide enterprise tooling directly.

ArborXR Is Here to Help You Navigate These Changes

For many teams, these changes to the Meta HMS ecosystem reduce cost and simplify deployment. For others, the transition away from HMS introduces new planning requirements.

One point applies to every enterprise XR program. Scaling beyond January 2030 requires an enterprise-grade MDM that is not tied to a single hardware vendor. ArborXR provides the device management, content distribution, and operational controls teams need to run XR programs with confidence as platform strategies evolve.

Try ArborXR for Free

XR device management your way, on a platform you can trust.