Skip to Content

An Empty Defender Firewall Policy Shouldn't Be Able to Take a Device Offline (Let a lone your whole organisation)

20 November 2026 by
Ben Cole
| No comments yet

Intune will let you save a Microsoft Defender Firewall Rules policy containing a rule that has nothing but a name. Assign it, and the device cuts itself off the network. No warning, no validation error, no "are you sure?" — just a laptop that can no longer reach anything, including Intune.

I hit this recently on a customer engagement. This post covers what happened, why it happens, how to get the devices back, and the guardrails I now put around firewall policy.

What happened

A new firewall rules policy was created under Endpoint security > Firewall > Create policy > Windows > Microsoft Defender Firewall Rules. A rule was added and given a name. Nothing else was set: no direction, no action, no application, no ports, no remote addresses, no network profiles.

The portal accepted it. Review + create showed the rule name and very little else, which looked harmless. The policy was assigned.

On the next check-in, affected devices lost all network connectivity. Browsing failed, Teams dropped, and the devices stopped checking in to Intune — so the obvious fix (unassign the policy) did nothing for machines already hit. In the portal the policy reported as successfully applied.

Why it happens

A firewall rule is a filter plus an action. Every condition you leave blank — application, protocol, local and remote ports, local and remote addresses, interface type, network profile — means "any". A rule with only a name has no conditions at all, so it matches every packet on every profile.

That leaves direction and action. In the Firewall CSP, an unset direction defaults to outbound. Once that rule is delivered with a block action, you have an any-to-any outbound block, and outbound block rules take precedence over allow rules in Windows Defender Firewall. DNS, DHCP renewals, the MDM channel, Entra sign-in: all gone.

The rule lands in the MDM policy store, not the local store:

HKLM\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\Mdm\FirewallRules

So a local admin opening wf.msc and trying to disable it from the UI will find it greyed out or reasserted. You can see what Intune has pushed with:

Get-NetFirewallRule -PolicyStore ActiveStore |
    Where-Object PolicyStoreSourceType -eq 'MDM' |
    Select-Object DisplayName, Direction, Action, Enabled, Profile

This is not the first time Intune firewall rules have produced a block-everything outcome. During service incident IT1214934 earlier this year, Rudy Ooms at Patch My PC documented existing rules being rewritten into an any-to-any outbound block after policy changes. Different trigger, same failure mode: a rule with no effective scope and a block action.

This is a product problem, not just admin error

Yes, someone saved an incomplete rule. But a management plane that can isolate every device in a tenant from a single click should not accept a rule that has no scope and no explicit action.

Intune already validates far less dangerous things: plenty of Settings Catalog entries become mandatory once a parent setting is enabled. A firewall rule with no direction, no action and no conditions is not a meaningful configuration in any environment I can think of. There is no legitimate reason to allow it.

What I would expect instead:

  • Direction and action mandatory on every rule, with no silent default.
  • A hard warning when a block rule has no application, port or address conditions — effectively "this rule will block all outbound traffic".
  • Review + create showing the effective rule, including defaults, not just the fields you typed.

None of that is difficult, and any one of them would have stopped this.

Getting the devices back

The order matters. Fix Intune first, or the rule will come straight back the moment a device checks in.

  1. Stop the bleeding. Remove the assignment (or delete the rule from the policy) so no further devices pick it up.
  2. Get local admin on an affected device. With Windows LAPS backed up to Entra ID, the password is in the Intune or Entra portal under the device's Local admin password — you will not be retrieving it on the device itself.
  3. Remove the MDM rule. From an elevated prompt, find the offending value under the MDM FirewallRules key above and delete it. If you are not sure which value it is, export the key first, then compare against the rule names in the policy.
  4. Restart the firewall service or reboot. Restart-Service mpssvc -Force usually does it; a reboot is the safe option.
  5. Confirm and sync. Check connectivity, re-run the Get-NetFirewallRule query above to confirm the rule is gone, then trigger a sync from Settings > Accounts > Access work or school.

For remote users this means a call, a talk-through or a courier. Defender for Endpoint live response and remote tools won't help: the device can't reach them either.

Guardrails I now use for firewall policy

Until Intune validates this properly, the protection has to come from process.

  • Ring every firewall change. New or edited firewall rule policies go to a pilot group first — ideally including a device you can physically reach — and sit there through at least one check-in before wider assignment.
  • Never leave direction or action blank. Set both explicitly on every rule, even where the default is what you want. Treat a rule with no application, port or address condition as a defect.
  • Keep one rule per purpose, and name it for what it does. "Block outbound – notepad.exe" is reviewable; "Rule 1" is not.
  • Use reusable settings for address groups so the same scope isn't retyped (or missed) across policies.
  • Get a second pair of eyes. Peer review firewall rule policies before assignment, the same way you would a Conditional Access change.
  • Keep Windows LAPS working. If it isn't backing up to Entra ID today, recovery from this becomes a reimage job.
  • Check what actually landed. The portal reporting success means the CSP accepted the rule, not that the rule is sensible. Spot-check the MDM store on a pilot device.

Closing thoughts

Firewall policy is one of the few Intune workloads that can take a device completely out of management in one step. That deserves more validation than a free-text name field and a Create button.

I've raised this as feedback with Microsoft. If you've seen the same behaviour, add your voice — and in the meantime, pilot your firewall rules and set direction and action on every one of them.

Sources

Ben Cole 20 November 2026
Share this post
Archive
Sign in to leave a comment
Microsoft 365 E7 Explained
Why its an easier sell to your SLT than E5