⚠️ This article is deprecated and no longer relevant for Meta Quest device enrollment.
As of February 26, 2025, Meta has changed how Quest devices enroll into ArborXR. To enroll, you’ll need to use ArborXR’s integration with Horizon managed services. This may come with changes to pricing, privacy, and agreements, as enrollment will be managed through Meta’s system.
Helpful resources:
Head over to our blog for existing customers to learn how these changes affect your current deployment and device management.
See this help article for steps to enroll Quest devices into ArborXR using Horizon managed services.
Overview
Quest devices require a Meta account to be set up. This is relatively easy when setting up a few devices, but scaling to more devices can be difficult and time-consuming. In this article, you’ll learn the options available to deploy Meta Learn how to efficiently set up large numbers of Meta devices with Meta Test User Accounts.
Meta Test User accounts vs. Meta accounts
A Meta account is required to use any Meta Quest device. Every user must create and/or log in with a Meta account using a unique email address, Facebook, Instagram login during the initial device setup. Alternatively, it is possible to leverage a developer feature, Meta Test User Accounts. Further, to enroll your devices in an MDM like ArborXR, you must enable Developer Mode from the Meta Horizon mobile companion app on the Meta account logged into the Quest device. This requires said Meta account to be associated with a Meta Developer Organization in some fashion. Below, we'll discuss the two available options to scale the set up of your Quest devices along with any benefits and limitations of each option.
1. The Meta Account
Meta Accounts are verified accounts that are traditionally tied to an individual's identity. Using the Business Verification steps below, you can add Meta accounts to your Quest Developer Organization and ready them for Developer Mode using only app-based 2FA. While 2FA is still required, this route is more scalable as it's not tied to a specific phone number and can use a solution like Google Authenticator or 1Password to manage 2FA codes.
Otherwise, the following are required to allow a Meta account to enable Developer Mode:
Added to a Meta Developer Organization
Have either or both added to the Meta Account:
2-Factor Authentication (SMS-based, NOT app-based)
Credit Card
As you begin planning your content strategy for your devices, it's critical to understand if you team's use case will require Meta Quest App Store apps. Many developers only make their applications available via the Meta Quest App Store. If you have any immediate or potential future needs for Meta Horizon App Store content, using a Meta Account is the only way to access applications directly from the Meta Horizon App Store.
2. Test Users
Test User accounts are a developer feature of a Meta Developer organization. The benefit of using Test User accounts to set up Meta Quest devices is that you can avoid setting up or using personal Meta accounts, they can be generated in bulk, and they are Developer Mode-ready without any SMS 2FA or Credit Card requirements.
A caveat to this, Test User accounts cannot directly access Quest Store content. ArborXR does not recommend using Quest Store apps for large-scale deployments. Instead, contacting app developers directly for Android Package Kits (APK) can save time and money. With an APK, content can easily be managed and installed on all of your devices through ArborXR.
Disclaimer:
ArborXR recommends using one unique Meta Account per device to avoid any potential issues with Meta’s terms of service. However, many organizations use Meta Test User accounts when deploying numerous Meta devices because the process is much easier to manage. Meta Test User accounts cannot download Quest Store applications. To directly access Quest Store content, you must go through the standard Meta account setup for each device and download the Quest Store app to each device. Quest Store applications cannot be simultaneously run from the same account on different Quest devices.
To use Meta’s Test users, you will need to verify your business within your team’s Quest Developer Organization. This is required to create more than 3 Test Users. Start below to get started.
Verifying Your Business
When using Test Users, the Business Verification process only requires a single Meta account and only needs to be done once.
Be sure to sign up for a Meta Quest Developer account and create an Organization. If you're already set up with a Meta Developer account and organization, skip to Step 2.
On the left sidebar, scroll down, and select Organization > Org Verification.
Then, under Business verification > Click Start verification.
Click Get Started.
Select the country where your business is located and click Next.
Enter all of your organization’s business details. Once entered, click Next.
Select your business from the list that appears, click Next.
Confirm your organization's details.
Note: When providing a phone number, provide a phone number that can receive SMS text messages or phone calls.
Choose to receive your verification code via text message or phone.
Enter your verification code.
Click Submit.
If your business isn't publicly listed, here's what you'll need to do:
After completing, Steps 1-6 above, click My business isn’t listed.
Confirm your method of contact. You can verify through email (recommended), phone call, or SMS text message your preferred contact method to upload documents and confirm the business details. Uploaded documents must indicate the legal organization name, organization address, and company phone number.
💡 It can take up to 14 business days for Meta to complete the verification process. Once the verification process is complete, you’ll receive a notification.
Setting up Meta Test User Accounts
If you have not already done so, sign up to be a Meta Quest developer. If you already have a Meta Quest developer account, move to Step 2.
Go to the Meta Developer Dashboard.
Click Development > Test Users in the left-side navigation menu.
Click the green Add Test User button in the top right corner.
Fill in the fields to create a Test User, and then click Submit.
Create up to five users at once, entering it in the “Number of Users to Create” field. The password will be the same for all accounts in each batch of accounts you create.
Passwords cannot be reset for Test User accounts, so be sure to record the email and password somewhere for future reference.
After clicking Submit, info about the Test User(s) will appear in the Test User table, including a randomly generated “Name,” “Alias,” and “Email Address.”
Once Test Users are created, they can be used to log in to headsets.
A Test User can only be logged into one device at a time.
If the Quest device was previously logged into a Meta account, it will need to be factory reset.
Open the Meta Horizon companion app on your mobile device and select Continue with email.
Input the Test User email as it appears on your Meta Developer Dashboard Test User Table.
Input the password that you set up for the Test User account.
Turn on your Quest headset.
Ensure that your mobile device’s WiFi and Bluetooth are turned on.
Your Quest device should appear in the Meta Horizon companion app.
Choose your headset and the companion app will begin configuring it.
The headset is now connected to the Test User account.
In the Meta Horizon companion app, select the Test User's profile in the middle of the bottom navigation bar, then click:
Select Menu (three lines in the upper-right)
Select Devices
Select the device from the pop-up list
Select Headset Settings
Select Developer Mode
Toggle on Developer Mode
Add Devices to Groups within ArborXR
Now that you have set up your Quest devices with Meta Test User accounts, you are ready to add them to Groups within ArborXR. Adding devices to a group allows you to manage and configure devices in bulk instead of one at a time.