update defender procedure & screenshots

Author: tamram

articles/storage/blobs/lifecycle-management-overview.md

@@ -5,7 +5,7 @@ description: Use Azure Storage lifecycle management policies to create automated
 author: tamram
 
 ms.author: tamram
-ms.date: 05/05/2022
+ms.date: 05/09/2022
 ms.service: storage
 ms.subservice: common
 ms.topic: conceptual
@@ -378,7 +378,7 @@ This table shows how this feature is supported in your account and the impact on
 
 The lifecycle management feature is available in all Azure regions.
 
-Lifecycle management policies are free of charge. Customers are billed for standard operation costs for the [Set Blob Tier](/rest/api/storageservices/set-blob-tier) API calls. Delete operations are free.
+Lifecycle management policies are free of charge. Customers are billed for standard operation costs for the [Set Blob Tier](/rest/api/storageservices/set-blob-tier) API calls. Delete operations are free. However, other Azure services and utilities such as [Microsoft Defender for Storage](../../defender-for-cloud/defender-for-storage-introduction.md) may charge for operations that are managed through a lifecycle policy.
 
 Each update to a blob's last access time is billed under the [other operations](https://azure.microsoft.com/pricing/details/storage/blobs/) category.
 

articles/storage/blobs/storage-blob-customer-provided-key.md

@@ -6,7 +6,7 @@ author: tamram
 
 ms.service: storage
 ms.topic: how-to
-ms.date: 12/18/2020
+ms.date: 05/09/2022
 ms.author: tamram
 ms.reviewer: ozgun
 ms.subservice: common

articles/storage/common/azure-defender-storage-configure.md

@@ -8,7 +8,7 @@ author: tamram
 ms.service: storage
 ms.subservice: common
 ms.topic: conceptual
-ms.date: 03/30/2021
+ms.date: 05/09/2022
 ms.author: tamram
 ms.reviewer: ozgun 
 ms.custom: devx-track-azurepowershell
@@ -79,17 +79,15 @@ Use an Azure Resource Manager template to deploy an Azure Storage account with M
 Use an Azure Policy to enable Microsoft Defender for Cloud across storage accounts under a specific subscription or resource group.
 
 1. Launch the Azure **Policy - Definitions** page.
-1. Search for the **Deploy Microsoft Defender for Storage accounts** policy.
+1. Search for the **Azure Defender for Storage should be enabled** policy, then select the policy to view the policy definition page.
 
-    :::image type="content" source="media/azure-defender-storage-configure/storage-atp-policy-definitions.png" alt-text="Apply policy to enable Microsoft Defender for Storage accounts":::
+    :::image type="content" source="media/azure-defender-storage-configure/storage-defender-policy-definitions.png" alt-text="Locate built-in policy to enable Microsoft Defender for Storage for your storage accounts.":::
 
-1. Select an Azure subscription or resource group.
+1. Select the **Assign** button for the built-in policy, then specify an Azure subscription. You can also optionally specify a  resource group to further scope the policy assignment.
 
-    :::image type="content" source="media/azure-defender-storage-configure/storage-atp-policy2.png" alt-text="Select subscription or resource group for scope of policy ":::
+    :::image type="content" source="media/azure-defender-storage-configure/storage-defender-policy-assignment.png" alt-text="Select subscription and optionally resource group to scope the policy assignment.":::
 
-1. Assign the policy.
-
-    :::image type="content" source="media/azure-defender-storage-configure/storage-atp-policy1.png" alt-text="Assign policy to enable Microsoft Defender for Storage":::
+1. Select **Review + create** to review the policy and then create it.
 
 ### [PowerShell](#tab/azure-powershell)
 

articles/storage/common/media/azure-defender-storage-configure/storage-atp-policy-definitions.png

@@ -7,7 +7,7 @@ author: tamram
 
 ms.service: storage
 ms.topic: conceptual
-ms.date: 10/04/2021
+ms.date: 05/09/2022
 ms.author: tamram
 ms.subservice: common
 ---

articles/storage/common/media/azure-defender-storage-configure/storage-atp-policy1.png

@@ -5,7 +5,7 @@
  author: tamram
  ms.service: storage
  ms.topic: include
- ms.date: 10/04/2021
+ ms.date: 05/09/2022
  ms.author: tamram
  ms.custom: include file, references_regions
 ---
@@ -30,13 +30,9 @@ Microsoft recommends that you use a GPv2 storage account for most scenarios. You
 | Default maximum egress for general-purpose v2 and Blob storage accounts in the following regions (LRS/GRS):<br /><ul><li>Australia East</li><li>Central US</li><li>East Asia</li><li>East US 2</li><li>Japan East</li><li>Korea Central</li><li>North Europe</li><li>South Central US</li><li>Southeast Asia</li><li>UK South</li><li>West Europe</li><li>West US</li></ul> | 120 Gbps<sup>1</sup> |
 | Default maximum egress for general-purpose v2 and Blob storage accounts in the following regions (ZRS): <ul><li>Australia East</li><li>Central US</li><li>East US</li><li>East US 2</li><li>Japan East</li><li>North Europe</li><li>South Central US</li><li>Southeast Asia</li><li>UK South</li><li>West Europe</li><li>West US 2</li></ul> | 120 Gbps<sup>1</sup> |
 | Default maximum egress for general-purpose v2 and Blob storage accounts in regions that aren't listed in the previous row. | 50 Gbps<sup>1</sup> |
-| Maximum egress for general-purpose v1 storage accounts (US regions) | 20 Gbps if RA-GRS/GRS is enabled, 30 Gbps for LRS/ZRS<sup>2</sup> |
-| Maximum egress for general-purpose v1 storage accounts (non-US regions) | 10 Gbps if RA-GRS/GRS is enabled, 15 Gbps for LRS/ZRS<sup>2</sup> |
 | Maximum number of IP address rules per storage account | 200 |
 | Maximum number of virtual network rules per storage account | 200 |
 | Maximum number of resource instance rules per storage account | 200 |
 | Maximum number of private endpoints per storage account | 200 |
 
 <sup>1</sup> Azure Storage standard accounts support higher capacity limits and higher limits for ingress and egress by request. To request an increase in account limits, contact [Azure Support](https://azure.microsoft.com/support/faq/).
-
-<sup>2</sup> If your storage account has read-access enabled with geo-redundant storage (RA-GRS) or geo-zone-redundant storage (RA-GZRS), then the egress targets for the secondary location are identical to the egress targets of the primary location. For more information, see [Azure Storage replication](../articles/storage/common/storage-redundancy.md).