Problem

After using the Microsoft Entra admin center to reset the Microsoft Intune MDM and WIP scopes to None, Windows computers may temporarily fail to join Microsoft Entra ID with:

Error 80180018

This can occur even though the intention is to perform a normal Microsoft Entra Join without enrolling the computer into Microsoft Intune.

When This Can Happen

In a Microsoft 365 tenant that does not have the licensing required for automatic Microsoft Intune enrollment, the following warning may appear under:

Microsoft Entra admin center > Entra ID > Mobility (MDM and MAM) > Microsoft Intune

The warning states:

“The Intune app is enabled. Click here to reset the MDM and WIP scopes for Intune to None. It does not delete the Intune app itself.”

Selecting the link corrects the configuration by resetting the Microsoft Intune MDM and WIP scopes to None.

However, the change may not immediately take effect throughout Microsoft's backend services.

Temporary Error After Applying the Fix

After selecting the Microsoft-provided remediation, an attempt to Microsoft Entra join a Windows computer may fail with:

0x80180018

This error is also known as:

MENROLLEUSERLICENSE

The error indicates that Windows attempted MDM enrollment but the user does not have the necessary MDM/Intune license.

This may be a temporary condition while the changed Microsoft Intune Mobility configuration propagates through Microsoft's services.

Resolution

If error 80180018 appears shortly after selecting the Entra option to reset the Microsoft Intune MDM and WIP scopes to None:

1. Do not immediately purchase or assign an Intune license if the organization does not intend to use Microsoft Intune.
2. Verify that the Microsoft-provided remediation to reset the scopes to None was completed.
3. Allow time for the tenant-side configuration change to propagate.
4. Try the Microsoft Entra Join again later.

In our case, the problem continued for several hours after applying the remediation.

When tested approximately 24 hours later, the same Windows computer was able to Microsoft Entra join normally without an Intune license.

The configuration may propagate sooner. The 24-hour period is an observed troubleshooting result, not a documented Microsoft propagation time.

Optional: Verify the MDM Scope with PowerShell

The effective Microsoft Intune Mobility policy can be checked using Microsoft Graph PowerShell.

Connect to Microsoft Graph:

Connect-MgGraph -Scopes "Policy.Read.All"

Then run:

Invoke-MgGraphRequest -Method GET -Uri "https://graph.microsoft.com/beta/policies/mobileDeviceManagementPolicies"

Look for the Microsoft Intune policy.

After applying the Entra remediation, the important value should be:

"appliesTo": "none"

The appliesTo property represents the MDM user scope. A value of none indicates that automatic MDM enrollment is disabled for users.

What We Observed

During troubleshooting, Microsoft Graph showed:

displayName : Microsoft Intune

appliesTo : none

isValid : true

Despite the MDM scope already reporting None, Windows Entra Join continued to return 80180018 shortly after the configuration change.

No additional configuration changes were made.

When the join was attempted again the following day, it completed successfully.

This suggests that resetting the Intune MDM/WIP scope can require time to propagate through the Microsoft 365/Entra backend before Windows clients see the effective configuration.

Key Takeaway

If Windows starts returning 80180018 immediately after using Microsoft's Entra remediation to reset the Intune MDM/WIP scopes to None, the remediation itself may already be correct.

Verify that the MDM policy reports appliesTo: none, then allow time for the change to propagate before making additional tenant configuration changes or purchasing Intune licensing.