OOBE enrollment issue at first time configuration

[Ruhul Azad]

I would like to bring to your attention an issue we have encountered with the OOBE configuration. Although we followed the documentation provided, it appears that the requests are not reaching the DS server, and the device is not being enrolled in UEM.

Upon consulting with MSFT, we were informed that there is a stale entry for a second app in Azure, which is preventing the requests from being sent. To verify if there are any stale entries, you may use the following URL in the graph explorer:

GET https://graph.microsoft.com/beta/policies/mobileDeviceManagementPolicies

If you come across any apps with blank or false values in the Discovery URL and Terms and Conditions URL fields, it suggests that these are stale entries.

To delete these entries, please use the following command in the graph explorer. Before proceeding, please ensure that you have the necessary access to modify the policy. If not, please make the required modifications:

DELETE https://graph.microsoft.com/beta/policies/mobileDeviceManagementPolicies/APP ID