conflicting settings Defender Firewall

Question

We enabled a Intune policy for Defender with some basic settings.

Some settings come back reported with a conflict. When investigating the conflict it's reported back as applied in only one rule so how can there be a conflict some would presume....

For example at the firewall policy "Allow Local Ipsec Policy Merge" is set at the default "True" and is reported back 3 times, ones as "Success" and twice as "Conflict" And when opening the setting details its showing that its only set in one source profile.

The same can be told for some other setting as "Allow Local Policy Merge" and "Disable inbound Notifications".

Does anyone have a better way of investigating conflicting settings instead of clicking and guessing around until the conflicts hopefully disappear?

Answer 1

@wim duizer, Thanks for sharing the solution. I am glad the issue is resolved. Here, please let me write a brief summary to help others quickly find the solution:

Issue:

Conflicting settings Defender Firewall

Resolution:

Have a nice day!

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

@wim duizer, Thanks for posting in Q&A. From your description, I find many settings in one policy conflict with its own policy. That's strange. I suggest open case to check if there's any conflict in the background.

https://learn.microsoft.com/en-us/mem/get-support

Thanks for your understanding.

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 3

we ended up setting the merge settings in some baselines to not configured and that solved the majority of our conflicts