Hi,
Problem statement:
Autopilot or Microsoft Entra Enrollment, are not working. Users are able to sign in on Microsoft 365 Apps, eg. Word, Outlook, etc. though.
Errors:
Users are hit with a Workspace ONE UEM error: User not found. Upon mousing over Enrollment Support, these are generic support values for email and phone, eg. company@company.com
Upon clicking Exit, users are met with a Microsoft error: It looks like we can't connect to the URL for your organisation's MDM terms of use. Error: unauthorized_client.
Troubleshooting steps taken:
1. Triple-checked I have the Mobility App AirWatch by VMware has the correct values in MDM discovery URL and MDM terms of use URL respectively.
2. Checked the immutable ID - ObjectGUID is correctly defined across Active Directory, Workspace ONE UEM and Workspace ONE Access.
3. Verify setup as per the documentation: https://techzone.omnissa.com/enrolling-windows-devices-using-azure-ad-workspace-one-uem-operational-tutorial
I do not have premises MDM application under Add Application.
3. Checked device registration limits in Intune + Workspace ONE UEM.
4. Checked the succesful login logs from Workspace ONE Access and Microsoft Entra ID. Both reporting success.
To me, it seems like the final registration of the device in Workspace ONE UEM; but I'm lost here... And don't know how to confirm that?
Hi, Problem statement: Autopilot or Microsoft Entra Enrollment, are not working. Users are able to sign in on Microsoft 365 Apps, eg. Word, Outlook, etc. though. Errors: Users are hit with a Workspace ONE UEM error: User not found. Upon mousing over Enrollment Support, these are generic support values for email and phone, eg. company@company.com Upon clicking Exit, users are met with a Microsoft error: It looks like we can't connect to the URL for your organisation's MDM terms of use. Error: unauthorized_client. Troubleshooting steps taken: 1. Triple-checked I have the Mobility App AirWatch by VMware has the correct values in MDM discovery URL and MDM terms of use URL respectively. 2. Checked the immutable ID - ObjectGUID is correctly defined across Active Directory, Workspace ONE UEM and Workspace ONE Access. 3. Verify setup as per the documentation: https://techzone.omnissa.com/enrolling-windows-devices-using-azure-ad-workspace-one-uem-operational-tutorial I do not have premises MDM application under Add Application. 3. Checked device registration limits in Intune + Workspace ONE UEM. 4. Checked the succesful login logs from Workspace ONE Access and Microsoft Entra ID. Both reporting success. To me, it seems like the final registration of the device in Workspace ONE UEM; but I'm lost here... And don't know how to confirm that?