Enterprise extended reality (XR) strategies have often been shaped by the immediate use case: a training simulation, a remote-assistance programme, a virtual design review or an immersive studio. But the harder question comes after deployment. How long will the hardware receive security servicing? Will the software stack continue to evolve? Can an employer maintain privacy and governance as devices become less conspicuous and more capable?
That lifecycle question is becoming more pressing as immersive technology moves beyond pilots. My recent UC Today analysis of BBC Sport’s XR studio expansion showed how display technology, real-time graphics, tracking and production workflow can become permanent workplace infrastructure rather than a temporary event installation. The same principle applies to headsets, smart glasses and spatial-capture tools: the value is not just in what the technology can do on day one, but whether an organisation can govern, maintain and scale it over time.
This week’s XR news does not point to one uniform market direction. Instead, it highlights three decisions facing enterprise buyers: how to retire ageing headset fleets without disrupting work, how to prepare for possible restrictions on camera glasses and how to assess lower-friction routes into digital-twin data.
TL;DR
Meta has set March 2027 as the point at which Quest 2 and Quest Pro devices receive their final operating-system release, with security patches and critical bug fixes ending by the close of 2027.
The UK Government is exploring options to restrict smart glasses in certain settings and sales to certain users, but no ban, legal mechanism or timetable has been announced.
Amrax has raised a mid-seven-figure euro round to expand smartphone-based building capture, illustrating how spatial-data collection may become more accessible to facilities and construction teams.
Why Is XR Lifecycle Planning Becoming a Workplace Issue?
Immersive workplace technology combines several interdependent layers: the device, operating system, management tooling, applications, network and identity controls, content, data governance and the workflow the technology is intended to support. A failure or end-of-support decision in one layer can affect the usefulness and risk profile of the rest.
For training and frontline teams, this matters because headsets may be deployed across distributed sites and used for tasks with a long content-development cycle. Replacing hardware is not simply a procurement exercise. It can require testing applications, revalidating device management, updating accessories and training materials, moving user accounts and deciding whether existing content will work as expected on the successor platform.
What Is an XR Lifecycle?
An XR lifecycle is the period during which an organisation can obtain, manage, secure and support an immersive device and its software for a defined business use case. It includes more than whether a headset still powers on: it also covers operating-system updates, security fixes, app compatibility, management support and the availability of replacement devices.
That does not mean every older device needs immediate replacement. It does mean enterprises need a documented decision about whether to refresh, migrate or accept the risks of keeping a fleet after feature or security support ends.
What Does Meta’s Quest 2 and Quest Pro Timeline Mean for Fleets?
Meta has confirmed that Horizon OS v2.13 will be the final operating-system release for Quest 2 and Quest Pro, reaching all eligible devices by March 2027. The company says v213 is also the last supported software development kit version for the devices.
Security patches and critical bug fixes are due to continue through the end of 2027. Meta’s developer guidance also says developers can submit new apps supporting the two headsets through December 2027; after that point, new titles will not be offered on Quest 2 or Quest Pro. Developers can continue updating existing apps, but Meta will no longer test new operating-system and software development kit releases against the older devices.
For an enterprise fleet, that distinction matters. An existing training application may remain available and maintainable, but the organisation will be operating on a fixed platform that no longer receives new operating-system capabilities. It should not assume future applications or management requirements will continue to work on those headsets without additional testing.
Key Takeaways for Quest 2 and Quest Pro Buyers
March 2027 — final Horizon OS release reaches devices.
December 2027 — security patches and critical bug fixes are scheduled to end, while new-app submissions for the headsets also close.
After feature support ends — application teams, rather than Meta, will carry more of the testing burden when platform changes elsewhere affect an existing deployment.
Meta’s schedule also creates a more concrete comparison point for organisations that have delayed a headset refresh. Microsoft has previously stated in its HoloLens 2 release notes that November 2024 was its final feature release, with monthly security servicing continuing through December 2027. The products serve different workloads and have different management models, but the shared end date for security servicing makes 2027 a notable planning horizon for enterprise teams running older mixed-reality hardware.
Meta’s managed-device route applies to newer hardware. In its update on Meta for Work, the company said Horizon Managed Services for Quest 3 and Quest 3S is supported until January 4, 2030. That support statement should not be read as extending the Quest 2 or Quest Pro lifecycle. Organisations with older fleets should confirm their own commercial and support terms with Meta or their reseller, particularly where device management is central to the deployment.
How Should Training and Frontline Teams Respond to the Deadline?
The immediate priority is discovery. Teams should establish where Quest 2 and Quest Pro devices are deployed, which applications they run, whether the devices access corporate systems or sensitive data, and which workflows would be interrupted by a migration. This is especially important where a headset fleet is shared across shifts or sites and where training content has been developed by an external supplier.
Next, buyers should test successor hardware against real tasks rather than only reviewing specifications. A refresh programme should assess application compatibility, account and identity flows, device enrolment, Wi-Fi performance, hygiene and accessory requirements, content-transfer processes and user comfort. A device that is technically supported may still be unsuitable if it makes a frontline workflow slower or harder to administer.




