Skip to content

Commit a378137

Browse files
authored
Merge pull request #206924 from bmansheim/tww-review-exclude-storage-account
Improve Exclude storage account article based on TW workshop
2 parents 1389424 + 26b62a0 commit a378137

File tree

1 file changed

+13
-26
lines changed

1 file changed

+13
-26
lines changed

articles/defender-for-cloud/defender-for-storage-exclude.md

Lines changed: 13 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -1,27 +1,21 @@
11
---
2-
title: Microsoft Defender for Storage - excluding a storage account
3-
description: Excluding a specific storage account from a subscription with Microsoft Defender for Storage enabled.
4-
ms.date: 02/06/2022
2+
title: Exclude storage accounts from Microsoft Defender for Storage
3+
description: Learn how to exclude specific Azure Storage accounts from Microsoft Defender for Storage protections.
4+
ms.date: 08/04/2022
55
ms.topic: how-to
66
ms.author: benmansheim
77
author: bmansheim
88
---
9-
# Exclude a storage account from Microsoft Defender for Storage protections
10-
11-
> [!CAUTION]
12-
> Excluding resources from advanced threat protection is not recommended and leaves your cloud workload exposed.
13-
14-
When you [enable Microsoft Defender for Storage](../storage/common/azure-defender-storage-configure.md#set-up-microsoft-defender-for-cloud) on a subscription, all existing Azure Storage accounts will be protected and any storage resources added to that subscription in the future will also be automatically protected.
159

16-
If you need to exempt a specific Azure Storage account from this Defender plan, use the instructions on this page.
10+
# Exclude a storage account from Microsoft Defender for Storage protections
1711

18-
> [!TIP]
19-
> We recommend enabling [Microsoft Defender for Resource Manager](defender-for-resource-manager-introduction.md) for any accounts with unprotected Azure Storage resources. Defender for Resource Manager automatically monitors your organization's resource management operations, whether they're performed through the Azure portal, Azure REST APIs, Azure CLI, or other Azure programmatic clients.
12+
When you [enable Microsoft Defender for Storage](../storage/common/azure-defender-storage-configure.md#set-up-microsoft-defender-for-cloud) on a subscription, all current and future Azure Storage accounts in that subscription are protected. If you have specific accounts that you want to exclude from the Defender for Storage protections, you can exclude them using the Azure portal, PowerShell, or the Azure CLI.
2013

14+
We don't recommend that you exclude storage accounts from Defender for Storage because attackers can use any opening in order to compromise your environment. If you want to optimize your Azure costs and remove storage accounts that you feel are low risk from Defender for Storage, you can use the [Price Estimation Workbook](https://ms.portal.azure.com/#view/Microsoft_Azure_Security/SecurityMenuBlade/~/28) in the Azure portal to evaluate the cost savings.
2115

22-
## Exclude a specific storage account
16+
## Exclude an Azure Storage account
2317

24-
To exclude specific storage accounts from Microsoft Defender for Storage when the plan is enabled on a subscription:
18+
To exclude an Azure Storage account from Microsoft Defender for Storage:
2519

2620
### [**PowerShell**](#tab/enable-storage-protection-ps)
2721

@@ -114,35 +108,28 @@ To exclude specific storage accounts from Microsoft Defender for Storage when th
114108
115109
Microsoft Defender for Storage can exclude specific active Databricks workspace storage accounts, when the plan is already enabled on a subscription.
116110
117-
**To exclude an active Databricks workspace**:
111+
**To exclude an active Databricks workspace**:
118112
119113
1. Sign in to the [Azure portal](https://portal.azure.com).
120-
121114
1. Navigate to **Azure Databricks** > **`Your Databricks workspace`** > **Tags**.
122-
123115
1. In the Name field, enter `AzDefenderPlanAutoEnable`.
124-
125116
1. In the Value field, enter `off`.
126-
127117
1. Select **Apply**.
128118
129119
:::image type="content" source="media/defender-for-storage-exclude/workspace-exclude.png" alt-text="Screenshot showing the location, and how to apply the tag to your Azure Databricks account.":::
130120
131121
1. Navigate to **Microsoft Defender for Cloud** > **Environment settings** > **`Your subscription`**.
132-
133122
1. Toggle the Defender for Storage plan to **Off**.
134123
135124
:::image type="content" source="media/defender-for-storage-exclude/storage-off.png" alt-text="Screenshot showing how to switch the Defender for Storage plan to off.":::
136125
137126
1. Select **Save**.
138-
139127
1. Toggle the Defender for Storage plan to **On**.
140-
141128
1. Select **Save**.
142129
143130
The tags will be inherited by the Storage account of the Databricks workspace and prevent Defender for Storage from turning on.
144131
145-
> [!Note]
132+
> [!Note]
146133
> Tags can't be added directly to the Databricks Storage account, or its Managed Resource Group.
147134
148135
### Prevent auto-enabling on a new Databricks workspace storage account
@@ -151,11 +138,11 @@ When you create a new Databricks workspace, you have the ability to add a tag th
151138
152139
**To prevent auto-enabling on a new Databricks workspace storage account**:
153140
154-
1. Follow [these steps](/azure/databricks/scenarios/quickstart-create-Databricks-workspace-portal?tabs=azure-portal) to create a new Azure Databricks workspace.
141+
1. Follow [these steps](/azure/databricks/scenarios/quickstart-create-Databricks-workspace-portal?tabs=azure-portal) to create a new Azure Databricks workspace.
155142
156-
1. In the Tags tab, enter a tag named `AzDefenderPlanAutoEnable`.
143+
1. In the Tags tab, enter a tag named `AzDefenderPlanAutoEnable`.
157144
158-
1. Enter the value `off`.
145+
1. Enter the value `off`.
159146
160147
:::image type="content" source="media/defender-for-storage-exclude/tag-off.png" alt-text="Screenshot that shows how to create a tag in the Databricks workspace.":::
161148

0 commit comments

Comments
 (0)