Defender vulnerability shielding on by default (preview)¶
Microsoft announced on 17 November 2026 that vulnerability shielding in Microsoft Defender, "now in preview", is on by default and, during an active attack, "acts autonomously" with protections that "reduce network reachability, restrict access paths, and tighten permissions" on exposed systems. Defender and Intune admins should decide now which servers must never get automatic changes and exclude them, and check whether preview features are on in their tenant.
Runbook card
What changes: attack disruption in Microsoft Defender now also shields systems during an attack. Microsoft: "On by default, attack disruption now automatically contains the exploited path and shields new routes the attacker could use", with "precise protections that reduce network reachability, restrict access paths, and tighten permissions. It acts autonomously". Proactive shields before an attack work differently: "Nothing is implemented without your approval."
Who: Defender admins, SOC teams and Intune admins of tenants that use Microsoft Defender. The feature is in preview; Microsoft does not say whether the default reaches tenants that have not turned on Defender preview features.
By when: now (announced 17 November 2026). Microsoft hasn't published a date for general availability.
Do this: 1. List the servers and apps that must never get automatic network or permission changes (for example line-of-business database servers or OT gateways). 2. Put them in the shielding exclusions, which Microsoft says are "managed through Microsoft Intune". 3. Check whether preview features are on in the Defender portal (check below). 4. Tell the SOC that a shield can be rolled back "with one click".
Check: Defender portal > Settings > Microsoft Defender XDR > General > Preview features, and Settings > Microsoft Defender XDR > Automated response (read-only view).
Source: Vulnerability shielding: Protect the time before the patch (Microsoft Defender Blog, 17 November 2026).
What Microsoft says¶
Microsoft introduced vulnerability shielding at Ignite as a way to cover the time between a vulnerability becoming known and the patch being installed. Microsoft's Ignite summary says it "applies targeted, temporary protection to vulnerable systems" and "During an active attack, it applies controls autonomously, cutting off new attack paths for adversaries."
Two modes, in Microsoft's words:
- During an attack (automatic): "On by default, attack disruption now automatically contains the exploited path and shields new routes the attacker could use". This mode "acts autonomously".
- Before an attack (proactive): shields are proposed by the Risk Reduction Agent for approval. "Nothing is implemented without your approval." For the public preview, Microsoft says the agent covers "server-side RCE vulnerabilities".
Microsoft describes shields as temporary and says "Every active shield is listed with the vulnerability it covers, the devices it applies to and why it was applied." Guardrails Microsoft names: "Exclusions are managed through Microsoft Intune to keep critical devices and apps out of scope", and "You set the guardrails: exclude devices or apps that must never be touched, roll back any shield in one click, or turn shielding off."
What is not known¶
- Microsoft does not say whether "on by default" applies only to tenants with Defender preview features turned on, or to every Defender tenant.
- The posts give no portal path for the shielding on/off switch and no Intune path for the exclusions.
- Microsoft hasn't published a date for general availability or a licence statement for shielding.
- The Learn page on attack disruption exclusions (last updated 4 October 2026) does not mention shielding, so do not assume an exclusion there also covers shielding.
Microsoft's Ignite post points to aka.ms/vulnerabilityshielding for more. We will add an "Updated" note here when Microsoft publishes a Learn page with the settings.
How to check¶
Read-only. Nothing below changes your tenant. A Security Reader can view these settings.
- Preview features: Defender portal > Settings > Microsoft Defender XDR > General > Preview features. If preview features are on, assume shielding can act in your tenant. Only a Global Administrator, Security Administrator or Security Operator can change this setting. (Path from Microsoft Learn, Defender XDR preview features; that page was last updated in May 2025.)
- Existing automated response exclusions: Defender portal > Settings > Microsoft Defender XDR > Automated response > Devices and Identities. Compare the list with the servers you wrote down in step 1 of the card. Microsoft notes that "A Security Reader can view exclusions and tags but can't edit them."
- Remediation level of device groups: System > Settings > Endpoints > Device groups (under Permissions), column Remediation level (for example "Full - remediate threats automatically"). This shows how much Defender may do on its own per group today (Configure automatic attack disruption).
Microsoft's guidance on the existing exclusions is cautious: "Excluding assets from automated responses isn't recommended." Exclude only the systems where an automatic network or permission change would cause more harm than the attack it stops, and write down why.
Next step: more read-only checks for Defender for Endpoint and ASR, with a Jira import, in the free Defender for Endpoint and ASR Kit Top 5; or get the Friday mail with the week's changes and what to check.
How to verify¶
- Your list of excluded servers matches what is configured as exclusions once Microsoft publishes the Intune path.
- The SOC runbook says how to read the list of active shields and how to roll one back.
- After a test incident or a real one, the incident shows which shields were applied, and an excluded server shows none.
Impact and rollback¶
A shield changes network reachability, access paths or permissions on a live system, so a business app can lose a connection during an incident. Microsoft says any shield can be rolled back "in one click", and shielding can be turned off. Excluding a server keeps it out of scope, but it also leaves that server without this protection during an attack.
Related: the Defender for Endpoint and ASR Kit, Defender RBAC auto-enable from December (MC1537494), Defender for Identity retires 2 classic alerts (MC1552387), every dated action on Microsoft 365 security deadlines and more Endpoint & devices news.
Sources¶
- Vulnerability shielding: Protect the time before the patch (Microsoft Defender Blog, 17 November 2026; read 17 November 2026)
- Ignite 2026: What's new in Microsoft Defender & Sentinel (Microsoft, 17 November 2026; read 17 November 2026)
- Exclude assets from automated response in attack disruption (Microsoft Learn, last updated 4 October 2026; read 17 November 2026)
- Configure automatic attack disruption in Microsoft Defender XDR (Microsoft Learn, last updated 7 August 2026; read 17 November 2026)
- Microsoft Defender XDR preview features (Microsoft Learn, last updated May 2025; read 17 November 2026)
Last reviewed: 17 November 2026. Runbook Lab is not affiliated with Microsoft.