Merge branch 'main' into docs-editor/migrate-devices-streamlined-1741343630

Author: emmwalshh

.openpublishing.redirection.defender-xdr.json

@@ -304,6 +304,11 @@
       "source_path": "defender-xdr/feedback.md",
       "redirect_url": "/defender-xdr/m365d-enable-faq",
       "redirect_document_id": false
-    },                                       
+    },
+    {
+      "source_path": "defender-xdr/microsoft-365-defender-integration-with-azure-sentinel.md",
+      "redirect_url": "/azure/sentinel/microsoft-365-defender-sentinel-integration",
+      "redirect_document_id": false
+    }                                            
   ]
 }

defender-endpoint/troubleshoot-asr.md

@@ -4,9 +4,9 @@ description: Resources and sample code to troubleshoot issues with attack surfac
 ms.service: defender-endpoint
 ms.localizationpriority: medium
 audience: ITPro
-author: denisebmsft
-ms.author: deniseb
-ms.date: 02/24/2025
+author: emmwalshh
+ms.author: ewalsh
+ms.date: 03/11/2025
 ms.reviewer:
 manager: deniseb
 ms.custom: asr
@@ -28,17 +28,21 @@ search.appverid: met150
 - [Microsoft Defender for Endpoint Plan 1 and 2](microsoft-defender-endpoint.md)
 - [Microsoft Defender XDR](/defender-xdr)
 
+The first and most immediate way is to check locally, on a Windows device, which attack surface reduction rules are enabled (and their configuration) is by using the PowerShell cmdlets.
+
+Here are a few other sources of information that Windows offers, to troubleshoot attack surface reduction rules' impact and operation.
+
 When you use [attack surface reduction rules](attack-surface-reduction.md) you might run into issues, such as:
 
 - A rule blocks a file, process, or performs some other action that it shouldn't (false positive); or
 - A rule doesn't work as described, or doesn't block a file or process that it should (false negative).
 
 There are four steps to troubleshooting these problems:
 
-1. [Confirm prerequisites](#confirm-prerequisites)
-2. [Use audit mode to test the rule](#use-audit-mode-to-test-the-rule)
-3. [Add exclusions for the specified rule](#add-exclusions-for-a-false-positive) (for false positives)
-4. [Submit support logs](#collect-diagnostic-data-for-file-submissions)
+1. [Confirm prerequisites](#confirm-prerequisites).
+2. [Use audit mode to test the rule](#use-audit-mode-to-test-the-rule).
+3. [Add exclusions for the specified rule](#add-exclusions-for-a-false-positive) (for false positives).
+4. [Collect and submit support logs](#collect-microsoft-defender-anti-malware-protection-diagnostic-data-for-file-submissions).
 
 ## Confirm prerequisites
 
@@ -59,6 +63,36 @@ When setting up the attack surface reduction rules by using Group Policy, here a
 
 2. Make sure that there are **no spaces** at the beginning or at the end when adding the GUID for attack surface reduction rules.
 
+### Querying which rules are active
+
+One of the easiest ways to determine if attack surface reduction rules are already enabled is through a PowerShell cmdlet, Get-MpPreference.
+
+Here's an example:
+
+:::image type="content" source="media/getmpreferencescriptnew.png" alt-text="Screenshot showing the get mppreference script." lightbox="media/getmpreferencescriptnew.png":::
+
+There are multiple attack surface reduction rules active, with different configured actions.
+
+To expand information on attack surface reduction rules, you can use the properties `AttackSurfaceReductionRules_Ids` and/or `AttackSurfaceReductionRules_Actions`.
+
+Example:
+
+```powershell
+Get-MPPreference | Select-Object -ExpandProperty AttackSurfaceReductionRules_Ids
+```
+
+:::image type="content" source="media/getmpref-examplenew.png" alt-text="Screenshot showing the get mpreference example." lightbox="media/getmpref-examplenew.png":::
+
+The preceding image shows all the IDs for attack surface reduction rules that have a setting different from 0 (Not Configured).
+
+The next step is then to list the actual actions (Block or Audit) that each rule is configured with.
+
+```powershell
+Get-MPPreference | Select-Object -ExpandProperty AttackSurfaceReductionRules_Actions
+```
+
+:::image type="content" source="media/getmpref-example2new.png" alt-text="Screenshot that shows the get mppreference example2." lightbox="media/getmpref-example2new.png":::
+
 ## Use audit mode to test the rule
 
 Follow these instructions in [Use the demo tool to see how attack surface reduction rules work](attack-surface-reduction-rules-deployment-test.md) to test the specific rule you're encountering problems with.
@@ -71,10 +105,18 @@ Follow these instructions in [Use the demo tool to see how attack surface reduct
 
 If a rule isn't blocking a file or process that you're expecting it should block, first check to see if audit mode is enabled. Audit mode might be enabled for testing another feature, or by an automated PowerShell script, and might not be disabled after the tests were completed. 
 
-If you've tested the rule with the demo tool and with audit mode, and attack surface reduction rules are working on preconfigured scenarios, but the rule isn't working as expected, proceed to either of the following sections based on your situation:
+If you tested the rule with the demo tool and with audit mode, and attack surface reduction rules are working on preconfigured scenarios, but the rule isn't working as expected, proceed to either of the following sections based on your situation:
 
 - If the attack surface reduction rule is blocking something that it shouldn't block (also known as a false positive), you can [first add an attack surface reduction rule exclusion](#add-exclusions-for-a-false-positive).
-- If the attack surface reduction rule isn't blocking something that it should block (also known as a false negative), you can proceed immediately to the last step, [collecting diagnostic data and submitting the issue to us](#collect-diagnostic-data-for-file-submissions).
+- If the attack surface reduction rule isn't blocking something that it should block (also known as a false negative), you can proceed immediately to the last step, [collecting diagnostic data and submitting the issue to us](#collect-microsoft-defender-anti-malware-protection-diagnostic-data-for-file-submissions).
+
+### Querying blocking and auditing events
+
+Attack surface reduction rule events can be viewed within the Windows Defender log.
+
+To access it, open Windows Event Viewer, and browse to **Applications and Services Logs** \> **Microsoft** \> **Windows** \> **Windows Defender** \> **Operational**.
+
+:::image type="content" source="media/eventviewerscrnew.png" alt-text="Screenshot that shows the Event Viewer page." lightbox="media/eventviewerscrnew.png":::
 
 ## Add exclusions for a false positive
 
@@ -84,13 +126,13 @@ To add an exclusion, see [Customize attack surface reduction](attack-surface-red
 
 > [!IMPORTANT]
 > You can specify individual files and folders to be excluded, but you can't specify individual rules.
-> This means any files or folders that are excluded are excluded from all ASR rules.
+> This means any files or folders that are excluded from all ASR rules.
 
 ## Report a false positive or false negative
 
 Use the [Microsoft Security Intelligence web-based submission form](https://www.microsoft.com/wdsi/support/report-exploit-guard) to report a false negative or false positive for network protection. With a Windows E5 subscription, you can also [provide a link to any associated alert](alerts-queue.md).
 
-## Collect diagnostic data for file submissions
+## Collect Microsoft Defender Anti-malware Protection diagnostic data for file submissions
 
 When you report a problem with attack surface reduction rules, you're asked to collect and submit diagnostic data for Microsoft support and engineering teams to help troubleshoot issues.
 
@@ -108,6 +150,23 @@ When you report a problem with attack surface reduction rules, you're asked to c
 
 3. By default, they're saved to `C:\ProgramData\Microsoft\Windows Defender\Support\MpSupportFiles.cab`. Attach the file to the submission form.
 
+
+You can also view rule events through the Microsoft Defender Antivirus dedicated command-line tool, called `*mpcmdrun.exe*`, that can be used to manage and configure, and automate tasks if needed.
+
+You can find this utility in *%ProgramFiles%\Windows Defender\MpCmdRun.exe*. You must run it from an elevated command prompt (that is, run as Admin).
+
+To generate the support information, type `MpCmdRun.exe -getfiles`. After a while, several logs will be packaged into an archive (MpSupportFiles.cab) and made available at `C:\ProgramData\Microsoft\Windows Defender\Support`.
+
+:::image type="content" source="media/malware-prot-logsnew.png" alt-text="Screenshot that shows the malware protection logs." lightbox="media/malware-prot-logsnew.png":::
+
+Extract that archive and you have many files available for troubleshooting purposes.
+
+The most relevant files are as follows:
+
+- `MPOperationalEvents.txt`: This file contains same level of information found in Event Viewer for Windows Defender's Operational log.
+- `MPRegistry.txt`: In this file you can analyze all the current Windows Defender configurations, from the moment, the support logs were captured.
+- `MPLog.txt`: This log contains more verbose information about all the actions/operations of the Windows Defender.
+
 ## Related articles
 
 - [Attack surface reduction rules](attack-surface-reduction.md)