Businesses still using Quest 2 or Quest Pro have two dates to put in their 2027 plans. Existing software can keep running as Meta winds down support. IT and training teams should use the remaining time to check supplier commitments, test replacements and budget for migration.
Meta will deliver the final operating system update for Quest 2 and Quest Pro by March 2027, with security patches and critical bug fixes continuing through the end of the year. The company published its support timetable on November 2.
“Your apps keep working,” Meta wrote. Developers can continue updating existing apps, and the store will remain available on both headsets. PC VR through Link and cross-play with newer Quest devices will also continue at the platform level.

The Quest 2 and Quest Pro Support Timeline
| Date | What Changes | What to Plan |
|---|---|---|
| By March 2027 | The final OS update reaches both headsets. Later platform features are reserved for newer devices. | Confirm which app versions your suppliers will keep testing and supporting. |
| December 2027 | Final security patch and the deadline for submitting new apps for these devices. | Complete your security review and agree a replacement or retirement date. |
IT teams need to check app support and device management contracts separately. A training module that still launches may depend on a login service, reporting system or supplier whose support ends earlier.
Five Checks for Enterprise Teams
- Count the devices doing useful work. Record active headsets, locations, apps and the teams relying on them. Include spares and privately distributed software. Start with the deployments where a failed session would interrupt training or a scheduled customer visit.
- Get support dates in writing. Ask each app and device management supplier how long it will support your models, how updates will be delivered and who will fix compatibility problems. For custom software, identify who owns the source code and can maintain it.
- Test the complete session. Check sign-in, shared-device or kiosk settings, casting, accessories and results reaching your learning management system. Run the same exercise on a proposed replacement. If an app uses eye or face tracking, check those requirements before choosing hardware.
- Agree the security cutoff with IT. Put the final patch date into your asset register and renewal discussions. The UK’s National Cyber Security Centre advises moving away from obsolete products; controls can reduce exposure, but continuing without security updates carries risk. Decide who can approve any temporary exception.
- Budget for the whole change. Allow for licenses, replacement accessories, device enrollment, application testing and staff time. Include comfort and wearability in the pilot, using a normal-length session. Get a small replacement batch working before committing to a fleet purchase.
Give each deployment an owner, a supplier-confirmed support date and a funded next step. Teams with a stable, supported application may have room to schedule the change around their training calendar – but others may need to move sooner if a supplier or internal security policy sets an earlier deadline.














