Category filter
Fix 403: disallowed_useragent during iPhone ADE enrollment with Google authentication
TL;DR
During Apple Automated Device Enrollment, iPhones may fail at the Google authentication step with 403: disallowed_useragent because Google blocks sign-in from native iOS web views. To keep Google authentication enabled for iPads and Macs while allowing iPhones to enroll, create a separate MDM server in Apple Business for iPhones, integrate that server as a separate ADE account in Hexnode UEM, and assign a No Authentication enrollment profile as the Default Configuration Profile for that ADE account.
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, 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
- Log in to Apple Business.
- Navigate to Devices > Preferences or Management Service.
- Select Add a New MDM Server.
- Enter a clear name for the server, such as an iPhone-specific MDM server name.
- Go to the Default Device Assignment section.
- Select the newly created MDM server as the default target for iPhones or iOS devices.
Integrate the new Apple Business MDM server with Hexnode UEM
- Log in to the Hexnode UEM portal.
- Go to Admin > Apple Business/School Manager > ADE Accounts.
- Set up the connection for the newly created Apple Business MDM server.
- Download the Hexnode certificate.
- Upload the Hexnode certificate to the new MDM server in Apple Business.
- Download the generated Apple Business token from Apple Business.
- 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
- In the Hexnode UEM portal, go to Admin > Apple Business/School Manager > ADE.
- Go to Accounts and click the Edit or pencil icon next to the newly added ADE account.
- Locate the Default Configuration Profile dropdown.
- Select the enrollment profile configured with No Authentication.
- 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.
Frequently Asked Questions
Why does Google authentication fail only on iPhones during ADE enrollment?
During ADE enrollment, iOS launches the Hexnode setup screen in a native OS-controlled web view. Google blocks authentication from this web view and returns 403: disallowed_useragent. The setup flow cannot be forced into a different browser during this stage.
Do iPads and Macs also need No Authentication profiles?
No. Google authentication can continue to be used for iPads and Macs. The separate MDM server approach is used to avoid disabling Google authentication for all Apple devices when only iPhones are affected.
Can iPhones be enrolled first and assigned to users later?
Yes. iPhones can be enrolled with No Authentication, and the associated user can be updated after enrollment using the Hexnode Change Owner API. Devices may also be imported as pre-approved using CSV before enrollment when that workflow is suitable.
Is removing the device from Apple Business Manager required?
No. The device does not need to be removed from Apple Business Manager. Route iPhones to the appropriate MDM server in Apple Business Manager and assign a No Authentication profile to that server’s ADE account in Hexnode UEM.