Security Policy Errors

How to Resolve Microsoft Defender Policy and Baseline Conflicts

Amos GikundaAmos Gikunda Oct 22, 2026 869 views

Question details

Administrators encounter configuration conflicts when managing endpoint security settings across multiple policy sources.

How to Resolve Microsoft Defender Policy and Baseline Conflicts
Product
Microsoft Defender
Device & OS
not provided
Scenario
Managing enterprise security settings, specifically when the 'Scan Network Files' setting is configured differently across policies and security baselines.
Observed behavior
A conflict occurs when a specific setting is configured in one policy but is set to 'Not Configured' in an overlapping security baseline, causing inconsistent application.
Before you start

Ensure you have administrator access to your endpoint management portal (such as Microsoft Intune) before modifying configuration policies or security baselines.

Solution 1Recommended

Unify Configuration Sources

Align settings across all policy sources to prevent conflicting states.

The most effective way to prevent policy conflicts is to avoid configuring the same setting inconsistently in multiple policy sources. You must designate a primary source for specific configurations.

1
Identify the conflict

Locate the conflicting setting, such as 'Scan Network Files', within your endpoint management console.

2
Determine the primary policy

Decide whether the security baseline or the standalone Defender policy should manage this specific setting.

3
Update the secondary source

Change the setting in the non-primary policy source to 'Not Configured' so it no longer attempts to enforce a state.

4
Verify the effective setting

Check the device status in the management system to ensure the conflict is resolved, rather than relying solely on policy priority rules.

Unify Configuration Sources
Configuration Tip: Regularly auditing your security baselines against custom policies can proactively prevent these overlaps.
Free Microsoft Office alternative

Looking for a Secure and Lightweight Office Suite?

While troubleshooting enterprise system policies, you may also be evaluating your software ecosystem. WPS Office provides a highly compatible, secure, and lightweight alternative to Microsoft Office that deploys easily across enterprise environments.

  1. 1. Visit the official website: Go to the WPS Office official website to access the enterprise or free versions.
  2. 2. Download the installer: Select the appropriate version for your operating system and download the lightweight installer.
  3. 3. Install and deploy: Follow the straightforward installation steps to deploy the suite alongside your existing security infrastructure.
Fully compatible with Microsoft Office formats (Word, Excel, PowerPoint).Lightweight installation with minimal impact on system resources.Operates seamlessly alongside enterprise endpoint security solutions.Familiar user interface requiring zero learning curve for seamless migration.
microsoft office alternative - wps office

Frequently Asked Questions

What does 'Not Configured' mean in a Microsoft Defender security baseline?

The 'Not Configured' state means the policy does not enforce a specific action for that setting. It allows other targeted policies or local device settings to dictate the final configuration without triggering a direct clash.

Why doesn't policy priority automatically resolve Defender conflicts?

While policy priority handles general overlaps, explicitly conflicting configurations across different policy types (like baseline profiles vs. custom configuration policies) can result in an error state. Administrators must manually verify the effective setting rather than assuming priority resolves it.

Can I modify default security baselines in Microsoft Intune?

Yes, you can customize the specific settings within a baseline profile when you deploy it to a group. However, if your organizational compliance restricts modifying the baseline, creating a targeted custom configuration policy is the recommended alternative.