How to Enable Developer Mode on Meta Quest Managed by an MDM
Learn how to enable Developer Mode on Quest headsets managed by Meta Horizon Managed Services. Pro guide for debugging and sideloading Omnicast VR.
When your Meta Quest headsets are enrolled in an MDM (Mobile Device Management) such as Meta Horizon Managed Services (HMS), Developer Mode is not switched on from a personal developer account. It is authorized centrally by the administrator, then confirmed on each headset. This guide walks you through the full procedure, from the admin console to the first USB connection with OmnicastVR, and covers the most common blocking points.
In short: 1) the administrator allows Developer Mode / USB debugging in the device policy, 2) the policy is pushed to the headsets, 3) you check Settings > System > Developer in each headset, 4) you plug the headset into the PC and choose "Always allow from this computer".
Not using an MDM? If your Meta Quest is linked to a personal Meta account and the Meta Horizon mobile app, follow our guide How to Enable Developer Mode on Meta Quest via USB (No MDM) instead.
Before you start: what you need
- Admin access to the Meta Horizon Managed Services admin center, or to the third-party MDM your organization uses (for example Microsoft Intune or VMware Workspace ONE).
- The Meta Quest headsets already enrolled in your organization.
- A USB-C cable that carries data (many charging-only cables do not), and the Windows PC where OmnicastVR is or will be installed.
Unlike consumer headsets, no individual registration on the Meta developer portal is required: authorization comes from your organization's policy.
1. Allow Developer Mode in the MDM policy (administrator)
The first step is handled by the system administrator from the management console. It is the most secure way to manage a professional fleet: the setting is applied to the right group of devices, in one go.
| Step | Action |
|---|---|
| MDM console | The administrator signs in to the Meta Horizon Managed Services admin center, or to the third-party MDM connected to it. |
| Device policy | They open the device policies or restrictions that apply to the Meta Quest headsets (a whole group or specific devices, such as Quest 3). |
| Feature activation | They enable the option that allows Developer Mode or USB debugging. The exact label depends on the MDM. |
| Deployment | Once saved, the policy is pushed remotely to the headsets. They must be switched on and connected to the internet to receive it. |
2. Check the setting in each headset
When the policy allows it, and especially when the headset is used in Individual Mode with a managed account, finalize and check the activation directly on the device.
- Open the Developer menu: in the headset, go to Settings > System > Developer.
- Enable USB debugging: make sure Enable USB Debugging is turned on. If it is not, turn it on.
- Restart: if you had to change the setting, restart the headset, then check that the option is still active.
3. Connect the headset to the OmnicastVR PC
This one-time step links the headset to your supervision PC. After that, it is recognized automatically.
- Plug in the headset: connect it to the PC with the data USB-C cable.
- Authorize the PC: put on the headset. A window asks you to Allow USB debugging. Tick "Always allow from this computer", then press "Allow".
- Done: the headset is now visible to OmnicastVR. For the first stream, follow our ADB connection and first stream tutorial.
4. Troubleshooting: Developer Mode or USB debugging won't appear
- No "Developer" menu in the headset: the policy has not reached the device yet. Check that the headset is on, connected to the internet and in the right device group, then restart it.
- The Meta Horizon app says Developer Mode is only available to device owners: the headset is managed by your organization. The setting must be allowed by the administrator in the MDM, not from the mobile app.
- The "Allow USB debugging" window does not show up: use a USB-C cable that carries data, put the headset on before plugging it in, then unplug and plug it back in. Restarting OmnicastVR also brings the prompt back.
- The window was dismissed by mistake: unplug the cable, go to Settings > System > Developer, check that USB debugging is still on, then plug the headset back in.
- The headset is still not detected: see our VR headset streaming troubleshooting guide.
5. MDM headsets vs consumer headsets: what changes
| Consumer headset (personal Meta account) | Headset managed by an MDM | |
|---|---|---|
| Who allows Developer Mode | The user, from the Meta Horizon mobile app | The administrator, in the MDM policy |
| Meta developer account | Required (organization on developers.meta.com) | Not required |
| Scale | Headset by headset | Whole fleet at once |
| Guide | Developer Mode via USB (No MDM) | This page |
6. What about the end of Meta Horizon Managed Services?
Meta stopped selling Horizon Managed Services and commercial Meta Quest models on February 20, 2026. Since then, HMS licenses are free, and Meta supports the current product, including access for Meta Quest 3 and 3S, until January 4, 2030. Your managed headsets therefore keep working, but the service will not get new features.
If you are reconsidering how you manage your fleet, compare the options in MDM vs OmnicastVR, and read Meta Horizon Managed Services Is Free Until 2030 to see who can still sign up and when OmnicastVR alone is enough.
Next steps with OmnicastVR
An MDM deploys policies and apps to your fleet. OmnicastVR is what the trainer uses in the room, during the session: see every headset screen, launch apps on all headsets at once and switch them off with one click, over a local Wi-Fi network. Learn more about how OmnicastVR complements a VR MDM.
- OmnicastVR onboarding: video tutorials and FAQ
- Install APKs on several VR headsets at once
- How many VR headsets can my PC stream?
- Download OmnicastVR for free
Frequently Asked Questions
Do I need a Meta developer account to enable Developer Mode on a headset managed by an MDM?
No. On a headset enrolled in Meta Horizon Managed Services or another MDM, Developer Mode and USB debugging are allowed by the administrator in the device policy. Registering an organization on the Meta developer portal is only needed for consumer headsets linked to a personal Meta account.
Why can't I turn on Developer Mode in the Meta Horizon app?
If the headset belongs to your organization's fleet, the Meta Horizon app cannot change this setting: it is controlled by the MDM. Ask your administrator to allow Developer Mode or USB debugging in the device policy, then restart the headset once the policy has been applied.
Do I have to allow USB debugging again before every session?
No. If you tick "Always allow from this computer" during the first connection, the headset remembers your PC. It is then recognized automatically in later sessions. You only need to authorize it again with a different computer or after a factory reset.
Do headsets managed by Meta Horizon Managed Services still work after the end of sales?
Yes. Meta stopped selling Horizon Managed Services on February 20, 2026, but licenses are now free and the current product is supported until January 4, 2030, including for Meta Quest 3 and 3S. The service will not get new features.
