# Fix 403: disallowed_useragent during iPhone ADE enrollment with Google authentication

Executive Summary
-----------------

The error **Access blocked: Hexnode’s request does not comply with Google’s policies** with `403: disallowed_useragent` can appear when an iPhone is enrolled through Apple Business using an ADE enrollment profile that requires Google authentication. The issue occurs because Google no longer permits authentication through native web views used during the iPhone setup flow. Since the ADE setup screen is launched by iOS before a standard browser environment is available, the Google sign-in page cannot be completed at that stage.

For automated Apple Business deployments, the confirmed workaround is to route iPhones to a separate Apple Business MDM server and assign that server a Hexnode enrollment profile with **No Authentication**. This lets iPhones complete enrollment without the blocked Google sign-in page, while iPads and Macs can continue using a Google-authenticated enrollment profile on the primary ADE account.

Issue
-----

During iPhone enrollment through Apple Business [Automated Device Enrollment](https://www.hexnode.com/mobile-device-management/help/enrollment-of-apple-devices-through-dep/), the Google authentication page fails with an error similar to:

- **Access blocked: Hexnode’s request does not comply with Google’s policies**
- `403: disallowed_useragent`

This commonly occurs when the ADE enrollment profile assigned to the iPhone requires Google authentication.

Why the error occurs on iPhones
-------------------------------

Google has removed support for `allowsSignInWithWebView`, which means Google authentication is no longer permitted within native web views. During Apple DEP/ADE enrollment, the Hexnode setup screen is launched directly by the iOS operating system rather than through the Hexnode app or a full browser.

Because iOS controls this enrollment web view, Hexnode cannot force the setup flow to open in a different browser context during the initial ADE enrollment stage. Google identifies the native iPhone web view as a disallowed user agent and blocks the authentication attempt.

**Note:** Google authentication can continue to work for iPads and Macs in this enrollment context. The workaround below is intended for deployments where iPhones must avoid Google authentication while iPads and Macs continue using it.

Recommended configuration for automated Apple Business/ADE deployments
----------------------------------------------------------------------

Use separate Apple Business MDM servers to apply different ADE enrollment profiles by device type:

- Use the primary MDM server for iPads and Macs with a Google authentication enrollment profile.
- Use a secondary MDM server for iPhones with a **No Authentication** enrollment profile.

This avoids changing the authentication behavior for all Apple devices and allows iPhones to enroll without encountering the blocked Google sign-in page.

Create a separate MDM server in Apple Business for iPhones
----------------------------------------------------------

1. Log in to **[Apple Business](https://business.apple.com/)**.
2. Navigate to **Devices** > **Preferences** or **Management Service**.
3. Select **Add a New MDM Server**.
4. Enter a clear name for the server, such as an iPhone-specific MDM server name.
5. Go to the **Default Device Assignment** section.
6. Select the newly created MDM server as the default target for iPhones or iOS devices.

 Note: 
The exact Apple Business labels may vary by Apple Business interface version. Use the device assignment settings that control which MDM server receives newly added devices.

 

Integrate the new Apple Business MDM server with Hexnode UEM
------------------------------------------------------------

1. Log in to the **Hexnode UEM portal**.
2. Go to **Admin** > **Apple Business/School Manager** > **ADE Accounts**.
3. Set up the connection for the newly created Apple Business MDM server.
4. Download the Hexnode certificate.
5. Upload the Hexnode certificate to the new MDM server in Apple Business.
6. Download the generated Apple Business token from Apple Business.
7. Upload the Apple Business token back into Hexnode UEM to complete the ADE account integration.

Assign the No Authentication enrollment profile as the default profile
----------------------------------------------------------------------

1. In the Hexnode UEM portal, go to **Admin > Apple Business/School Manager > ADE**.
2. Go to **Accounts** and click the **Edit** or pencil icon next to the newly added ADE account.
3. Locate the **Default Configuration Profile** dropdown.
4. Select the enrollment profile configured with **No Authentication**.
5. Click **Save**.

After this configuration, iPhones assigned to the secondary Apple Business MDM server enroll through the No Authentication profile and bypass the Google sign-in screen that triggers `403: disallowed_useragent`.

Optional post-enrollment user assignment methods
------------------------------------------------

If user association is still required after iPhone enrollment without authentication, use one of the following approaches where applicable:

- **Post-enrollment user assignment using API:** Enroll the iPhone with no authentication, then update the associated user after enrollment using the Hexnode Change Owner API.
- **Pre-approved device import using CSV:** Import devices as pre-approved before enrollment and map them to the intended user records so that enrolled devices can be associated with the correct users.

Troubleshooting
---------------

### The iPhone still shows 403: disallowed\_useragent

- Verify that the iPhone is assigned to the secondary MDM server in Apple Business.
- Confirm that the secondary MDM server has been integrated as a separate ADE account in Hexnode UEM.
- Check that the ADE account used for iPhones has a **No Authentication** enrollment profile selected under **Default Configuration Profile**.

### Changing the enrollment profile affects all Apple devices

- Do not change the authentication type on the shared enrollment profile if iPads and Macs must continue using Google authentication.
- Create a separate enrollment profile for iPhones and assign it through a separate Apple Business MDM server/ADE account.

### There is no option to assign an enrollment profile directly by OS in Hexnode

- Use Apple Business device assignment to route iPhones to a separate MDM server.
- Assign the iPhone-specific **No Authentication** profile as the default profile for that server’s ADE account in Hexnode UEM.