Microsoft Defender for Cloud

Disable Vulnerability Findings for Virtual Machines - Microsoft Defender for Cloud | Microsoft Learn

29 September 2026Doc update+11 / −11 lines

In brief

The article updates heading capitalization, link and emphasis formatting, and punctuation in the filtering option descriptions.

What Defender admins need to know

No administrator action is required; the existing guidance remains easier to scan.

Summaries are generated from the documentation change itself.

Documentation change

View full page diff

View on Microsoft Learn

The comparison below shows only the changed extract. Use the full-page view for complete context.

Disable vulnerability findingsVulnerability Findings for virtual machinesVirtual Machines - Microsoft Defender for Cloud | Microsoft Learn

Important

Vulnerabilities with a severity less than medium
Unpatchable vulnerabilities
Vulnerabilities with CVSS score less than 6.5
Findings with specific text in the security check or ~~category (for~~category, for example, ~~“Red Hat”)~~Red Hat

Prerequisites

Sign in to the Azure portal.
Go to Defender for Cloud > Recommendations.
Find the recommendation Machines should have vulnerability findings resolved.
On the recommendation details page, select the Take action tab, and then select Disable rule.
In the Disable rule pane, specify the criteria for the findings you want to disable. You can specify:
- IDs –. Enter one or more finding ~~IDs (separate~~IDs. Separate multiple IDs with ~~semicolons).~~semicolons.
- CVEs –. Enter CVE identifiers for the findings you want to disable.
- Categories –. Enter the categories of findings to disable.
- Security checks –. Enter text from the security check name for findings to disable.
- CVSS2 and CVSS3 scores –. To filter by score, enter a value between 1 and 10.
- Minimum severity –. Select Medium or High to exclude findings with a lower severity.
- Patchable status –. Select this option to exclude findings that can't be patched.
Optionally, add a justification, and then select Apply rule. The rule might take up to 24 hours to take effect.

@@ -1,6 +1,6 @@ --- layout: Conceptual-title: Disable vulnerability findings for virtual machines - Microsoft Defender for Cloud | Microsoft Learn+title: Disable Vulnerability Findings for Virtual Machines - Microsoft Defender for Cloud | Microsoft Learn canonicalUrl: https://learn.microsoft.com/en-us/azure/defender-for-cloud/disable-vulnerability-findings breadcrumb_path: /azure/breadcrumb/defender-for-cloud/toc.json feedback_help_link_url: https://techcommunity.microsoft.com/t5/microsoft-defender-for-cloud/bd-p/MicrosoftDefenderCloud@@ -41,7 +41,7 @@ spProducts: platformId: 2c36e4dd-e1a3-6100-8a86-396907780006 --- -# Disable vulnerability findings for virtual machines - Microsoft Defender for Cloud | Microsoft Learn+# Disable Vulnerability Findings for Virtual Machines - Microsoft Defender for Cloud | Microsoft Learn  Important
 
@@ -58,7 +58,7 @@ You might disable findings for: - Vulnerabilities with a severity less than medium
 - Unpatchable vulnerabilities
 - Vulnerabilities with CVSS score less than 6.5
-- Findings with specific text in the security check or category (for example, “Red Hat”)
+- Findings with specific text in the security check or category, for example, *Red Hat*
 
 ## Prerequisites
 
@@ -72,17 +72,17 @@ To disable specific vulnerability findings, follow these steps: 
 1. Sign in to the [Azure portal](https://portal.azure.com/).
 2. Go to **Defender for Cloud** &gt; **Recommendations**.
-3. Find the recommendation **[Machines should have vulnerability findings resolved](https://portal.azure.com/#blade/Microsoft_Azure_Security/RecommendationsBlade/assessmentKey/1195afff-c881-495e-9bc5-1486211ae03f)**.
+3. Find the recommendation [Machines should have vulnerability findings resolved](https://portal.azure.com/#blade/Microsoft_Azure_Security/RecommendationsBlade/assessmentKey/1195afff-c881-495e-9bc5-1486211ae03f).
 4. On the recommendation details page, select the **Take action** tab, and then select **Disable rule**.
 5. In the **Disable rule** pane, specify the criteria for the findings you want to disable. You can specify:
 
-    - **IDs** – Enter one or more finding IDs (separate multiple IDs with semicolons).
-    - **CVEs** – Enter CVE identifiers for the findings you want to disable.
-    - **Categories** – Enter the categories of findings to disable.
-    - **Security checks** – Enter text from the security check name for findings to disable.
-    - **CVSS2 and CVSS3 scores** – To filter by score, enter a value between 1 and 10.
-    - **Minimum severity** – Select *Medium* or *High* to exclude findings with a lower severity.
-    - **Patchable status** – Select this option to exclude findings that can't be patched.
+    - **IDs**. Enter one or more finding IDs. Separate multiple IDs with semicolons.
+    - **CVEs**. Enter CVE identifiers for the findings you want to disable.
+    - **Categories**. Enter the categories of findings to disable.
+    - **Security checks**. Enter text from the security check name for findings to disable.
+    - **CVSS2 and CVSS3 scores**. To filter by score, enter a value between 1 and 10.
+    - **Minimum severity**. Select *Medium* or *High* to exclude findings with a lower severity.
+    - **Patchable status**. Select this option to exclude findings that can't be patched.
 6. Optionally, add a justification, and then select **Apply rule**. The rule might take up to 24 hours to take effect.
 
     [![Screenshot of creating a rule to disable VM vulnerability findings in Defender for Cloud.](media/remediate-vulnerability-findings-vm/new-disable-rule-for-finding.png)](media/remediate-vulnerability-findings-vm/new-disable-rule-for-finding.png#lightbox)