Exempt Resource
In brief
The page now includes an Important notice, a link to Azure preview terms, and screenshots covering the Exemptions tab, unified RBAC permissions, exemption creation, and management actions.
What Defender admins need to know
Administrators can use the new visuals to locate exemption controls, verify permissions, and follow the creation workflow.
Summaries are generated from the documentation change itself.
Documentation change
The comparison below shows only the changed extract. Use the full-page view for complete context.
::: zone pivot="defender-portal"
Important
This feature is currently in Public Preview in the Microsoft Defender portal. For more information, see Supplemental Terms of Use for Microsoft Azure Previews.
Exemptions help security teams focus on the risks that require action while maintaining a governed record of findings that don't require remediation. Use an exemption when a finding has been reviewed and determined to be a false positive, covered by another control, temporarily deferred, or accepted as risk. Each exemption records its scope, matching conditions, justification, and review period, helping your organization reduce operational noise without losing visibility or accountability.
Why use exemptions?
Exemptions provide a structured alternative to informally suppressing a security finding. They help organizations:
To delegate exemption management, go to System > Permissions > Microsoft Defender XDR > Roles in the Microsoft Defender portal and create or update a role with the required permission and scope.
Create an exemption
Go to Exposure Management > Policies > Exemption, and then select Create Exemption. The creation process includes four decisions:
After the exemption is submitted, Microsoft Defender processes the exemption and updates matching findings. Changes to finding status, exposure calculations, and related posture metrics might not be reflected immediately.
Create an exemption from a recommendation
You can also create an exemption directly from a recommendation. When launched from a recommendation, Defender automatically prepopulates the exemption conditions based on the selected recommendation to reduce configuration effort and ensure the exemption targets the intended finding:
What is prepopulated?
- The exemption condition is automatically set to By recommendation and is based on the recommendation from which the exemption was created. This condition can't be changed during the creation flow.
@@ -16,7 +16,7 @@ manager: orspodek ms.service: defender-for-cloud description: Create exemption rules to remove resources or recommendations from secure score impact in Microsoft Defender for Cloud. ms.topic: how-to-ms.custom: ignite-2023, msecd-doc-authoring-1030+ms.custom: ignite-2023, msecd-doc-authoring-1032 ms.date: 2026-10-28T00:00:00.0000000Z zone_pivot_groups: defender-portal-experience ai-usage: ai-assisted@@ -187,8 +187,14 @@ If the recommendation still shows resources as unhealthy after 24 hours, see [Re
::: zone pivot="defender-portal"
+Important
+
+This feature is currently in Public Preview in the Microsoft Defender portal. For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
+
Exemptions help security teams focus on the risks that require action while maintaining a governed record of findings that don't require remediation. Use an exemption when a finding has been reviewed and determined to be a false positive, covered by another control, temporarily deferred, or accepted as risk. Each exemption records its scope, matching conditions, justification, and review period, helping your organization reduce operational noise without losing visibility or accountability.
+[](media/exempt-resource/manage-exemptions.png#lightbox)
+
## Why use exemptions?
Exemptions provide a structured alternative to informally suppressing a security finding. They help organizations:
@@ -245,6 +251,8 @@ If a finding affects assets managed in Azure, you have two options:
To delegate exemption management, go to **System** > **Permissions** > **Microsoft Defender XDR** > **Roles** in the Microsoft Defender portal and create or update a role with the required permission and scope.
+[](media/exempt-resource/exemption-permissions.png#lightbox)
+
## Create an exemption
Go to **Exposure Management** > **Policies** > **Exemption**, and then select **Create Exemption**. The creation process includes four decisions:
@@ -258,10 +266,14 @@ Go to **Exposure Management** > **Policies** > **Exemption**, and then sel
After the exemption is submitted, Microsoft Defender processes the exemption and updates matching findings. Changes to finding status, exposure calculations, and related posture metrics might not be reflected immediately.
+[](media/exempt-resource/create-exemption-name-scope.png#lightbox)
+
## Create an exemption from a recommendation
You can also create an exemption directly from a recommendation. When launched from a recommendation, Defender automatically prepopulates the exemption conditions based on the selected recommendation to reduce configuration effort and ensure the exemption targets the intended finding:
+[](media/exempt-resource/create-exemption-from-recommendation.png#lightbox)
+
### What is prepopulated?
- The exemption condition is automatically set to **By recommendation** and is based on the recommendation from which the exemption was created. This condition can't be changed during the creation flow.




