Microsoft HoloLens 2 remains embedded in many enterprise mixed-reality programmes. Although production has ended, organisations may still rely on deployed devices, approved applications and established workflows. This guide explains the practical options for maintaining continuity, sourcing replacement hardware and planning a controlled transition.
What is Microsoft HoloLens 2?
Microsoft HoloLens 2 is a self-contained, optical see-through mixed-reality headset designed primarily for professional use. It places digital information within the user’s physical environment and supports interaction through hand tracking, eye tracking, voice and spatial mapping.
Organisations have used HoloLens 2 for guided work, remote expert support, training, design review and visualisation. In many deployments, the hardware is only one part of a wider system that may also include purpose-built applications, device management policies, user training, accessories and documented operating procedures.
HoloLens 2 discontinuation and support timeline
Microsoft stopped producing HoloLens 2 and announced a last-time-to-buy position in 2024. Microsoft stated that support for HoloLens 2, including security updates, is scheduled to end on 31 December 2027.
End of production and end of support are different milestones. Devices already in service do not immediately stop working because manufacturing has ended. However, the availability of replacement units, accessories and suitable donor devices can become more limited as remaining stock is absorbed.
Organisations should confirm the current Microsoft support position, their application dependencies and their own security requirements when planning continued use.
The operational problem for existing deployments
A deployed HoloLens 2 programme may depend on a consistent hardware platform. Replacing a failed unit with a different headset is not always a simple swap. Applications may need redevelopment or validation, accessories may not transfer, device-management processes may change, and users may require retraining.
This creates several practical risks:
- insufficient spare units for device failures or expansion
- inconsistent condition or configuration across a fleet
- difficulty locating the correct edition, accessories or quantity
- uncertainty about battery health, optics, sensors and previous use
- pressure to migrate before a replacement platform has been properly tested
The right response depends on the organisation’s deployment size, expected remaining service life, security obligations and application roadmap.
Options for replacement, refurbishment and continued support
1. Maintain a controlled spare pool
For business-critical deployments, holding tested spare units can reduce disruption. The number required should reflect fleet size, failure history, repair lead times and the importance of the workflow.
A useful fleet review should record serial numbers, edition, physical condition, battery behaviour, accessories, configuration and assigned location. This makes it easier to identify gaps before a device failure becomes urgent.
2. Refurbish suitable existing units
Refurbishment can extend the practical life of a deployment when devices are structurally sound and compatible with the required software. Units should be assessed individually rather than described as refurbished solely because they have been cleaned or reset.
Checks should cover the display and optics, tracking cameras and sensors, audio, buttons, connectivity, charging, battery performance, physical adjustment and enrolment readiness. Any refurbishment decision should also consider the availability of parts and the value of the unit relative to its expected remaining life.
3. Source genuine replacement HoloLens 2 hardware
New old stock, professionally refurbished units and tested used devices may all have a role. The appropriate condition depends on budget, warranty requirements, deployment risk and intended use.
Genuine compatible stock matters because organisations need the correct Microsoft hardware, edition and accessory set—not simply a listing labelled “HoloLens”. Buyers should verify model and edition, serial information, condition, included accessories, reset status, warranty and whether the unit can be enrolled into the intended environment.
For multi-site or larger deployments, consistency is particularly important. A mixed batch with unclear condition or missing components can create additional work for IT, procurement and end users.
4. Plan a platform transition
Where a deployment must continue beyond the practical life of HoloLens 2, organisations should evaluate replacement platforms against the actual use case. Display type, field of view, tracking, input methods, safety requirements, application compatibility, device management, data handling and working environment can all affect suitability.
Alternative hardware should not be assumed to be a direct replacement. A controlled pilot can reveal redevelopment, integration and training requirements before a wider rollout.
How XRDepot can help
XRDepot can source new, refurbished and used Microsoft HoloLens 2 units, subject to availability. This includes individual replacements, spare-pool requirements and hard-to-find quantities for organisations that need to maintain consistency across an existing deployment.
We can help clarify the required edition, condition, quantity, accessories, warranty and delivery location before sourcing begins. For refurbished and used units, the scope of testing and supplied accessories should be agreed clearly so that procurement teams can compare like for like.
Need HoloLens 2 hardware? Speak to XRDepot about sourcing.
Sources and further reading
Microsoft HoloLens documentation: https://learn.microsoft.com/hololens/
Microsoft’s October 2024 production and support statement was reported by The Verge: https://www.theverge.com/2024/10/1/24259369/microsoft-hololens-2-discontinuation-support