Deleting Intune Policies
Deleted an Intune policy. Settings reverted. Right? Not necessarily.
11/19/20263 min read


Intune Misunderstanding #4: “Deleting an Intune Policy Reverts Its Settings”
You deploy a configuration policy through Microsoft Intune. The policy applies successfully to your Windows devices.
A few weeks later, you delete the policy.
So the devices automatically return to their previous configuration, right?
Not necessarily.
One common misunderstanding about Intune is that removing a policy automatically reverses the settings it applied. In reality, the outcome depends on the setting, the configuration mechanism, and how Windows handles policy removal.
What happens when Intune applies a policy?
When a Windows device receives a native MDM configuration policy, the Windows MDM client processes the instructions through the appropriate Configuration Service Provider (CSP). Depending on the setting, Windows stores configuration information in PolicyManager, the registry, or other component-specific locations.
Once a setting is applied, its behavior is determined by the Windows component responsible for it.
This becomes particularly important when the policy is removed.
Deleting a policy vs. removing its assignment
These are two different administrative actions.
Deleting a policy removes the configuration profile from Intune. It is no longer available for management or assignment, and Intune generally attempts to remove the associated managed configuration from affected devices during subsequent check-ins, where supported.
Removing an assignment leaves the policy in Intune but removes its targeting from selected devices or users. Devices that are no longer targeted can receive instructions to remove the associated configuration.
In both cases, the device must communicate with Intune to process applicable changes. However, neither action guarantees that every setting returns to its previous value.
Deleting or unassigning a policy changes its management state. It does not guarantee restoration of the device's original configuration.
Removing a policy doesn't guarantee rollback
When a device processes policy removal, the outcome depends on the specific setting and its Configuration Service Provider (CSP). Some settings return to their default behavior. Others may retain their configured values or require an explicit change. And returning to a default value is not necessarily the same as restoring the configuration that existed before Intune applied the policy.
Intune does not maintain a universal backup of previous device settings for automatic restoration.
Understanding tattooed settings
The term tattooing describes a configuration that remains on a device after the management mechanism responsible for applying it has been removed.Consider a PowerShell script deployed through Intune that modifies a Windows registry value.The script runs successfully and changes the setting.
Later, the administrator removes the script assignment.
Does Windows automatically restore the original registry value? No. Removing the script assignment does not reverse the change. However, native MDM policies behave differently from scripts. Many CSP-backed settings support policy removal, while others have specific persistence behaviors.
Not every Intune setting is tattooed, and removal behavior must be evaluated individually.
Why settings sometimes remain
A setting that remains after policy removal isn't necessarily tattooed.
Another configuration source may still be controlling it, such as:
Another Intune configuration profile.
An Endpoint Security policy or security baseline.
Group Policy.
A local configuration or script.
This makes it important to identify all configuration sources before concluding that policy removal failed.
How do you verify the actual configuration?
The Intune admin center provides policy deployment information, but the actual Windows configuration is what matters.
For native MDM settings, useful troubleshooting tools include:
MDM diagnostics: Use MdmDiagnosticsTool.exe to collect management information.
Event Viewer: Review the DeviceManagement-Enterprise-Diagnostics-Provider logs for MDM processing events.
PolicyManager: Inspect locally stored policy information for applicable Policy CSP settings.
Windows configuration: Verify the effective setting directly in the relevant Windows component.
Before removing policies from production devices, test the removal behavior on a representative device and verify the result.
Key takeaways
Deleting a policy removes it from Intune; unassigning it removes its targeting.
Neither action guarantees that settings revert to their previous values.
Some configurations persist after management is removed.
Another policy may still be enforcing the same setting.
Always verify the actual configuration on the endpoint.