Windows 10: How can I comfirm if i enrolled my device to MDM ?

How can I comfirm if i enrolled my device to MDM ?If so, then can I remove the enrollment by unconnecting the work account that tied to the MDM?Or how could i remove the device enrollment? Thank you so much!

:)

 

Enrolling end users in MDM

Hi,



Thank you for posting in Microsoft Community.

I understand that you are trying to enroll users in Intune MDM.

However, for issues related to Microsoft Intune, let me help to point you in the right direction. I would suggest you to post your query in
TechNet Forums where you will find professionals with expertise on Microsoft Intune in
Windows 10 and that would be the appropriate forum.



References:
Troubleshoot device enrollment in Microsoft Intune

MDM enrollment of Windows-based devices

 

Enrolling end users in MDM

I have about 150 users that I need to enrol in Intune MDM, however this requires the user to be local admin. Is there a way around this?

I cannot enrol via group policy as no one is in the office and the majority of users do not have a VPN setup, the devices are also Azure registered, not joined.

 

Unable to enroll Device into Azure AD using 3rd Party On-Premise MDM

Turns out this is a known bug by the 3rd Party MDM provider (mobileiron) and there is a simple fix for it. These are a combination of regex entries[0-9] appended to URI parameters. This fix applies only to the latest Windows 10 Builds i.e from 1809, 1903 upwards that were impacted. So anyone enrolling with the latest builds (i.e 1809 updwards)should get in touch with their mobileiron provider for this fix immediately.

The temporal workaround in my case was to roll back to 17134 and earllier windows builds, tested and finally works as expected. I am in touch with Mobileiron regarding these Regex entries.

Follow this link for further details -> https://social.msdn.microsoft.com/F...-3rd-party-onpremise-mdm?forum=WindowsAzureAD for solution.

in a nutshell if you want to avoid this error message in your test environment whiles waiting for the permanent fix from Mobileiron just roll back to the earlier windows version as stated above and go through the configuration and enrollment steps once again as a workaround. Should work.