Forum Discussion
Antony1108
May 01, 2024Copper Contributor
Conflict status after having 2 Local user group membership Policy
Hello, I have an issue with applying two "Local User Group Membership" policies on a PC. The Intune policy report shows a conflict between having two "Local User Group Membership" policies despite...
RobinWulz
Jun 12, 2024Copper Contributor
We have two separate account protection policies 🙂
NicklasOlsen
Jun 12, 2024Iron Contributor
Hi RobinWulz,
Sorry for the late response. 🙂
I have tested it myself with two separate policies, and I get a conflict as well.
I've been looking in the docs, and from what I can read in the "caution" box, this scenario will cause a conflict with the policies. I can be wrong, but that's how I understand it. 🙂
https://learn.microsoft.com/en-us/mem/intune/protect/endpoint-security-account-protection-policy#configure-the-profile
Sorry for the late response. 🙂
I have tested it myself with two separate policies, and I get a conflict as well.
I've been looking in the docs, and from what I can read in the "caution" box, this scenario will cause a conflict with the policies. I can be wrong, but that's how I understand it. 🙂
https://learn.microsoft.com/en-us/mem/intune/protect/endpoint-security-account-protection-policy#configure-the-profile
- itwamanSep 19, 2024Copper Contributor
Hi everyone
we do have the same issue in my company
did anyone find the solution or the root cause of the conflict?
- NicklasOlsenJun 13, 2024Iron ContributorHi RobinWulz,
I've been a little bit curious about this issue, and I tried to deploy two separate policies again with two different actions (update/replace). This will also cause a conflict, in my case.
Lastly, I have tried to combine the policies with the same action (update/update) into one policy that works without problems. If I were you, I would probably reach out to Intune support team on Twitter to get an answer from MS. 🙂 - RobinWulzJun 13, 2024Copper Contributor
Well, the caution box is about a combination of replace and update rules which, according to the box, are not considered a conflict. The second sentence just explains the first one; you may have multiple policies assigned and they are not considered as conflicting if one updates the e.g. Administrators group and the second rule then replaces the Administrators group.
Solely from this documentation, it says the exact opposite of what we are experiencing. Would be nice to know if this is a bug or actually expected behavior, confirmed by MS itself 🙂