Roll Out Microsoft Defender Attack Surface Reduction Rules from Audit to Block Without Breaking Business Apps
Move Defender ASR rules from Audit to Block one ring and one rule at a time, with per-rule exclusions, event checks and a clean rollback.

Advertising disclosure: this article includes partner links. KBY may earn a commission if you sign up or buy through one, at no extra cost to you. How we make money.
Move Microsoft Defender attack surface reduction (ASR) rules to Block in stages. Put the rules in Audit on a small ring of devices, read what they would have stopped, add narrow per-rule exclusions for the business apps they catch, then switch one rule at a time to Warn or Block, starting with the rule that fired least. Repeat for each wider ring. Microsoft says the three standard protection rules can usually go straight to Block or Warn; test every other rule in Audit first. The key constraint in Intune is that each device should get one mode per rule. When two ASR policies give the same device conflicting values for a rule, Intune holds that setting back, so overlapping ring groups can leave a rule applied in neither mode.
#Why this needs an audit phase first
ASR rules block behaviour malware relies on, such as Office apps starting child processes or scripts launching downloaded executables. Line-of-business software does some of the same things: Microsoft’s own example for the Office child-process rule is an app that spawns a Command Prompt or uses PowerShell to set registry values. Block that rule across the estate and such an app stops working, with at most a pop-up to tell the user why.
A rule in Audit is evaluated as if it were in Block, but nothing is stopped. Each would-be block is logged as event 1122 in the Windows Defender Operational log, as an Audited action type in advanced hunting, and in the ASR rules report. Microsoft suggests auditing all the non-standard rules at once on the first ring.
The standard protection rules are Block abuse of exploited vulnerable signed drivers, Block credential stealing from the Windows local security authority subsystem, and Block persistence through WMI event subscription. Microsoft recommends Block for them, with two documented exceptions. If Configuration Manager manages the device, test the WMI persistence rule in Audit first, because the Configuration Manager client relies heavily on WMI. If Local Security Authority protection is already on, the LSASS rule adds nothing.
#How the pieces fit between Intune, Defender Antivirus and the device
Defender for Endpoint doesn’t deploy ASR rules itself. An Intune endpoint security policy (Microsoft’s recommended route), the Defender portal, the Policy CSP, Configuration Manager, Group Policy or PowerShell sets the mode on each device. Use the same method later for exclusions and rollback.
On the device, the rules are part of Microsoft Defender Antivirus, so the prerequisites are Defender’s. It must be the primary antivirus in Active mode (not Passive, limited periodic scanning or Off), with real-time protection on, cloud-delivered protection reachable, and platform and engine no more than two versions behind current. Two rules, the prevalence-and-age rule and the obfuscated-script rule, need cloud-delivered protection to work at all.
Each rule has a GUID and a mode code: 0 Off, 1 Block, 2 Audit, 5 Not configured, 6 Warn. Prefer 5 to 0: an explicit Off can conflict with another policy assigning the same rule, while Not configured has the same effect without that risk. Warn behaves like Block, but the user can choose Unblock for 24 hours. Since platform version 4.18.26060 that override needs administrator approval. Two rules don’t support Warn at all: the LSASS credential rule and Block Office applications from injecting code into other processes.
Intune merges the ASR settings from every ASR rules policy and Defender for Endpoint security baseline targeting a device. A conflicting setting, such as one rule in Audit from one policy and Block from another, isn’t applied at all, which is why the rings below never overlap.
Rendering diagram...

#Rolling it out ring by ring in Intune
These steps assume Intune-managed Windows devices onboarded to Defender for Endpoint. Configuration Manager has no Warn mode.
- Record what is there now. On two or three devices from each ring, run the read-only listing below from an elevated PowerShell session and save the output with the device name. It shows each configured rule GUID and its action. In the Defender portal, the Configuration tab of the ASR rules report (
https://security.microsoft.com/asr?viewid=configuration) gives the same picture per device. The test guidance asks you to switch off related rules already in Block or Warn before testing, so note any you find.$p = Get-MpPreference;0..([math]::Min($p.AttackSurfaceReductionRules_Ids.Count,$p.AttackSurfaceReductionRules_Actions.Count)-1) | % {[pscustomobject]@{Id=$p.AttackSurfaceReductionRules_Ids[$_];Action=$p.AttackSurfaceReductionRules_Actions[$_]}} | Format-Table -AutoSizeThe output is one row per rule, for example
d4f940ab-401b-4efc-aadc-ad5f3c50688a 2: the GUID of Block all Office applications from creating child processes, in Audit. - Create one Entra device group per ring. Defender for Endpoint management supports device objects only, so assign to device groups, never user groups. Keep ring membership exclusive. A device in two rings can get two modes for one rule, and Intune then holds that rule back.
- Back up any policy before you edit it. In the Intune admin center, select the existing ASR policy, then the ellipsis and Duplicate. The copy keeps the settings but not the assignments, so it changes nothing on devices and preserves the previous configuration.
- Create the ring 1 policy in Audit. Go to Endpoint security, then Attack surface reduction, then Create policy. Choose Platform: Windows and Profile: Attack Surface Reduction Rules. Set the standard protection rules to Block (subject to the two exceptions above) and the other rules you plan to use to Audit. Assign the policy only to the ring 1 device group. Precondition: Defender Antivirus is active on ring 1. Stop if a device reports Passive mode.
- Collect audit data during normal working days. Read it in the ASR rules report, with the advanced hunting query below, or on the device in Event Viewer. Advanced hunting keeps 30 days of data and throttles ASR events to unique processes each hour, so a count is a lower bound on how often something ran, not an exact tally.
1DeviceEvents 2| where Timestamp > ago(30d) 3| where ActionType startswith "Asr" 4| where ActionType endswith "Audited" 5| summarize EventCount=count() by ActionTypeEach
ActionTypenames a rule and outcome, such asAsrOfficeChildProcessAudited. To see which files and processes are behind one rule, filter on its action type and project the detail columns:1DeviceEvents 2| where (ActionType startswith "AsrOfficechild") 3| extend RuleId=extractjson("$Ruleid", AdditionalFields, typeof(string)) 4| project DeviceName, FileName, FolderPath, ProcessCommandLine, InitiatingProcessFileName, InitiatingProcessCommandLine - Add exclusions per rule, not globally. When a rule is set to anything other than Not configured, Intune shows ASR Only Per Rule Exclusions for that rule. Use it with the narrowest path and file name, such as
%ProgramFiles%\folder\file.exe. Avoid the global Attack Surface Reduction Only Exclusions list. If any policy assigned to a device sets it, those paths are excluded from every ASR rule on that device. Excluded files run with no event recorded, so each exclusion is a blind spot. - Move one rule to Warn or Block. Microsoft’s order is to start with the rule that triggered the fewest events. Change its mode in the ring 1 policy and leave the others in Audit. Rollback: set the same rule back to Audit in the same policy.
- Expand. When ring 1 runs cleanly in Block, give ring 2 its own policy in Audit and repeat. No ring goes straight to Block.
#Check it worked on the device and in the portal
First, the device’s own configuration. The listing from step 1 should now show action 2 for audited rules and 1 for blocked ones. A missing GUID usually means the policy hasn’t arrived or Intune held the rule back as a conflict. The Effective settings tab on the device page in the Defender portal shows each rule’s value and the source that set it.
Second, the events in the Windows Defender Operational log: 5007 is a settings change, 1122 an audited rule firing, 1121 a block, and 1129 a user overriding a Warn-mode block. The read-only query below pulls the last week of all four.
Get-WinEvent -FilterHashtable @{ LogName='Microsoft-Windows-Windows Defender/Operational'; Id=1121,1122,1129,5007; StartTime=(Get-Date).AddDays(-7) } | Select-Object TimeCreated, Id, MessageThird, the estate view. In the Defender portal, go to Reports, then the Endpoints tab, then Attack surface reduction rules. The Detections tab lists audit and block detections for the last 30 days. The Add exclusions tab shows how many detections and devices an exclusion would remove, and can download the paths as AsrExclusionPaths.csv for review. The report and device timeline need Defender for Endpoint Plan 2 or Defender for Business. Advanced hunting needs Plan 2. Without them, Event Viewer on each device is the record.
A ring is ready for the next step when audit events for the rule you plan to block come only from processes you have either excluded or decided to stop, and the listing matches the policy on every sampled device.
#What goes wrong in an ASR rollout
- A rule never appears on the device. Two policies, or a policy and a Defender for Endpoint security baseline, give the device different modes for the same rule. Intune drops the conflicting setting and applies the rest. Remove the overlap in group membership.
- Group Policy wins over Intune. When both configure the same rule, Group Policy takes precedence by default unless the
MDMWinsOverGPPolicy CSP setting is 1. Configure each rule in one place only. - Local PowerShell changes vanish. Settings made with
Set-MpPreferencehave the lowest precedence and any policy-based method overwrites them at startup. - An exclusion doesn’t take effect. Exclusions apply when the application or service starts. A service that was running when you added the exclusion keeps triggering the rule until it restarts. Some rules also ignore Defender Antivirus file and folder exclusions and honour only ASR exclusions.
- The Office child-process rule seems to do nothing. It’s enforced only when Office is installed under
%ProgramFiles%or%ProgramFiles(x86)%. - Servers report compliant but aren’t enforcing. Microsoft lists a known issue where attack surface reduction on Server operating systems shows as compliant without being enforced, with no fix date. Confirm server rings from events, not from compliance status.

#Permissions for changing and reading ASR policy
Changing ASR rules policies in Intune needs the granular Attack surface reduction permission; the built-in Endpoint Security Manager role has full management of endpoint security policies. Read Only Operator gives view-only access to policies and reports, which suits whoever reviews the audit data. Reading the ASR rules report in the Defender portal needs Security data basics (read) under Defender XDR unified RBAC, or one of Security Administrator, Global Reader or Security Reader. Microsoft says Global Administrator should be kept for emergencies.
Warn-mode Unblock now needs administrator approval and lasts 24 hours. Microsoft calls it temporary suppression, not a durable exclusion, so a recurring need belongs in a reviewed per-rule exclusion, with a record of who approved it and why.
#Roll back a rule without losing the rest
Microsoft’s guidance is that an exclusion is better than turning a rule off or returning it to Audit. When a blocked rule is stopping real work and the cause isn’t yet clear, though, returning that one rule to Audit is the documented fallback:
- In the same Intune policy that set Block, change only the affected rule to Audit. Leave other rules and other rings alone.
- Confirm event 5007 and action
2for that GUID, then reproduce the task: it should complete and log 1122 instead of 1121. - Use the audit events to write a per-rule exclusion, then move the rule back to Block.
- If the whole edit was wrong, set the policy back to the values kept in the duplicate you made before editing, rather than assigning both policies to the same devices.
Don’t switch a rule to Off (0) to roll it back while another policy still assigns it. That creates the conflict the merge logic holds back. Use Audit, or Not configured (5) if the rule really is leaving the estate.
#Keeping the rules in Block after the rollout
Once every ring is in Block, review ASR events as often as they arrive, hourly to daily depending on size. Watch three things. 1121 events from a new process need a decision: a new or updated business app to exclude, or exactly what the rule should stop. 1129 events show where users click through Warn and where that rule may need an exclusion or a firmer Block. Unplanned 5007 events mean a Defender setting changed, possibly a rule mode altered by a script or a forgotten test, which is how rules end up stuck in Audit. A device that stops reporting to Defender for Endpoint drops out of this view; the guide to a Defender for Endpoint device stuck onboarding or inactive covers that case. ASR rules limit what a compromised process can do on the endpoint. They sit alongside network detections such as spotting DNS tunnelling from resolver entropy.
About this page
Credited to
Dates
Published
Sources
Corrections
No corrections are listed for this page. Some review sweeps corrected pages without naming each one; those are in the corrections log.
Related labs
Calculators and what-if tools that go with this article.
Discover more
Graduate Learning
Ops Playbook
- PlaybookSet Up Windows Autopilot Device Preparation With Enrollment Time Grouping in Intune
- PlaybookConfigure the Autopilot Enrollment Status Page to Block Desktop Use Until Required Apps Install
- PlaybookRun Intune Remediations On Demand to Fix One Windows Device Without Waiting
- PlaybookRoute Windows Autopilot Profiles With Group Tags and Dynamic Device Groups
Was this useful?
Reports go to the site owner and are used to correct pages. Corrections are listed at /corrections.
Engineering insights, direct to you.
Receive the latest Systems Engineering tutorials, production guides, Engineering Labs and operational best practices.
Comments
Add a thoughtful note on Roll Out Microsoft Defender Attack Surface Reduction Rules from Audit to Block Without Breaking Business Apps. Comments are checked for spam and held for moderation before appearing.