Forum Discussion
DanWheeler
Apr 28, 2022Brass Contributor
Intune Firewall Policies Left Behind - Creation but No Deletion
I've been building out firewall policies for our device types and through some accidental experimentation, found that firewall policies never seem to be removed from the firewall once the Intune conf...
May 02, 2022
I am explaining how you could check out if those firewall rules were removed as it should in this blog
https://call4cloud.nl/2020/07/the-windows-firewall-rises/#part7
https://call4cloud.nl/2020/07/the-windows-firewall-rises/#part7
- DanWheelerMay 02, 2022Brass Contributor
Rudy_Ooms_MVP thanks, Rudy. I'm setting them through Endpoint Security > Microsoft Defender Firewall rules.
I assigned a test rule this morning, it synced to the firewall then I removed it but it's still in the firewall.
I'm using Windows 10 LTSC 1809. Wonder if this is an issue that was fixed in later builds?
- May 02, 2022
Hi... So far as I know the tattoeing issue changed with version 1903...
Intune and the Device Configuration Profile Tattooing issue (call4cloud.nl)
So .... I guess ltsc 1903 isn't going to work- ghostwriter_82hotmailcomMay 09, 2024Copper ContributorFound this because I ran into the same problem. The test machine is a Windows 11 23H2.
Created a test rule to block Firefox outbound traffic. It worked.
Changed the rule to allow and it did what it was supposed to.
Deleted the rule from Intune, it's still tattooed in the Defender firewall.
Possible something else changed? this is going to make it a bit more difficult to test rules before deploying them to production.