Skip to main content
All CollectionsFAQ
How does Swif detect MDM exists in the Windows installer even if there is no MDM?
How does Swif detect MDM exists in the Windows installer even if there is no MDM?
Updated over 10 months ago

Question: When you run the Swif installer for Windows, and on the Welcome to the Swif Installer screen that shows the 3 steps, I clicked Next and surprisingly it says it detected an old MDM profile on our system. This was after I erased the device, and I checked accounts to see if there were any other accounts except for the Azure AD account I signed into because of Autopilot. This doesn't *feel* right to me.

*Note, the screenshot is just an example on macOS. Windows installer would have a similar message.

Answer: Even if you are not connected to an MDM; If you are connected to Intune, the enrollment check detects that. When you say Remove on the Swif installer, Azure removes the MDM part that is linked to Intune, not to Entre ID. If you are connected only with Entre ID as an AD user, the MDM check detects it again but does not take any action when you say Remove.

You can confirm an existing Windows device enrollment here:

You can look at "Devices->Windows" before Swif enrollment to see if there is an existing MDM.

But if "MDM user scope" is "All" or "Some" in "Devices->Windows->Windows Enrollment->Automatic Enrollment", it registers to Intune under AutoPilot. In this case, after wiping, it would automatically connect to Intune by default.

Did this answer your question?