Merge pull request #197310 from tamram/tamram22-0505a

clarify behavior on LCM delete action for HNS accounts

Author: PRMerger19

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: 04/18/2022
+ms.date: 05/05/2022
 ms.service: storage
 ms.subservice: common
 ms.topic: conceptual
@@ -150,7 +150,9 @@ Lifecycle management supports tiering and deletion of current versions, previous
 | tierToCool                  | Supported for `blockBlob`                  | Supported     | Supported     |
 | enableAutoTierToHotFromCool | Supported for `blockBlob`                  | Not supported | Not supported |
 | tierToArchive               | Supported for `blockBlob`                  | Supported     | Supported     |
-| delete                      | Supported for `blockBlob` and `appendBlob` | Supported     | Supported     |
+| delete<sup>1</sup>          | Supported for `blockBlob` and `appendBlob` | Supported     | Supported     |
+
+<sup>1</sup> When applied to an account with a hierarchical namespace enabled, a delete action removes empty directories. If the directory is not empty, then the delete action removes objects that meet the policy conditions within the first 24-hour cycle. If that action results in an empty directory that also meets the policy conditions, then that directory will be removed within the next 24-hour cycle, and so on.
 
 > [!NOTE]
 > If you define more than one action on the same blob, lifecycle management applies the least expensive action to the blob. For example, action `delete` is cheaper than action `tierToArchive`. Action `tierToArchive` is cheaper than action `tierToCool`.

articles/storage/blobs/object-replication-configure.md

@@ -7,7 +7,7 @@ author: tamram
 
 ms.service: storage
 ms.topic: how-to
-ms.date: 05/02/2022
+ms.date: 05/05/2022
 ms.author: tamram
 ms.subservice: blobs
 ms.custom: devx-track-azurecli, devx-track-azurepowershell
@@ -21,7 +21,7 @@ This article describes how to configure an object replication policy by using th
 
 ## Prerequisites
 
-Before you configure object replication, create the source and destination storage accounts if they do not already exist. The source and destination accounts can be either general-purpose v2 storage accounts or premium block blob accounts. For more information, see [Create an Azure Storage account](../common/storage-account-create.md).
+Before you configure object replication, create the source and destination storage accounts if they don't already exist. The source and destination accounts can be either general-purpose v2 storage accounts or premium block blob accounts. For more information, see [Create an Azure Storage account](../common/storage-account-create.md).
 
 Object replication requires that blob versioning is enabled for both the source and destination account, and that blob change feed is enabled for the source account. To learn more about blob versioning, see [Blob versioning](versioning-overview.md). To learn more about change feed, see [Change feed support in Azure Blob Storage](storage-blob-change-feed.md). Keep in mind that enabling these features can result in additional costs.
 
@@ -47,7 +47,7 @@ To create a replication policy in the Azure portal, follow these steps:
 
     :::image type="content" source="media/object-replication-configure/configure-replication-policy.png" alt-text="Screenshot showing replication rules in Azure portal":::
 
-1. If desired, specify one or more filters to copy only blobs that match a prefix pattern. For example, if you specify a prefix `b`, only blobs whose name begin with that letter are replicated. You can specify a virtual directory as part of the prefix. The prefix string does not support wildcard characters.
+1. If desired, specify one or more filters to copy only blobs that match a prefix pattern. For example, if you specify a prefix `b`, only blobs whose name begin with that letter are replicated. You can specify a virtual directory as part of the prefix. You can add a maximum of up to five prefix matches. The prefix string doesn't support wildcard characters.
 
     The following image shows filters that restrict which blobs are copied as part of a replication rule.
 
@@ -85,30 +85,30 @@ $srcContainerName2 = "source-container2"
 $destContainerName2 = "dest-container2"
 
 # Enable blob versioning and change feed on the source account.
-Update-AzStorageBlobServiceProperty -ResourceGroupName $rgname `
+Update-AzStorageBlobServiceProperty -ResourceGroupName $rgName `
     -StorageAccountName $srcAccountName `
     -EnableChangeFeed $true `
     -IsVersioningEnabled $true
 
 # Enable blob versioning on the destination account.
-Update-AzStorageBlobServiceProperty -ResourceGroupName $rgname `
+Update-AzStorageBlobServiceProperty -ResourceGroupName $rgName `
     -StorageAccountName $destAccountName `
     -IsVersioningEnabled $true
 
 # List the service properties for both accounts.
-Get-AzStorageBlobServiceProperty -ResourceGroupName $rgname `
+Get-AzStorageBlobServiceProperty -ResourceGroupName $rgName `
     -StorageAccountName $srcAccountName
-Get-AzStorageBlobServiceProperty -ResourceGroupName $rgname `
+Get-AzStorageBlobServiceProperty -ResourceGroupName $rgName `
     -StorageAccountName $destAccountName
 
 # Create containers in the source and destination accounts.
-Get-AzStorageAccount -ResourceGroupName $rgname -StorageAccountName $srcAccountName |
+Get-AzStorageAccount -ResourceGroupName $rgName -StorageAccountName $srcAccountName |
     New-AzStorageContainer $srcContainerName1
-Get-AzStorageAccount -ResourceGroupName $rgname -StorageAccountName $destAccountName |
+Get-AzStorageAccount -ResourceGroupName $rgName -StorageAccountName $destAccountName |
     New-AzStorageContainer $destContainerName1
-Get-AzStorageAccount -ResourceGroupName $rgname -StorageAccountName $srcAccountName |
+Get-AzStorageAccount -ResourceGroupName $rgName -StorageAccountName $srcAccountName |
     New-AzStorageContainer $srcContainerName2
-Get-AzStorageAccount -ResourceGroupName $rgname -StorageAccountName $destAccountName |
+Get-AzStorageAccount -ResourceGroupName $rgName -StorageAccountName $destAccountName |
     New-AzStorageContainer $destContainerName2
 
 # Define replication rules for each container.
@@ -120,14 +120,14 @@ $rule2 = New-AzStorageObjectReplicationPolicyRule -SourceContainer $srcContainer
     -MinCreationTime 2021-09-01T00:00:00Z
 
 # Create the replication policy on the destination account.
-$destPolicy = Set-AzStorageObjectReplicationPolicy -ResourceGroupName $rgname `
+$destPolicy = Set-AzStorageObjectReplicationPolicy -ResourceGroupName $rgName `
     -StorageAccountName $destAccountName `
     -PolicyId default `
     -SourceAccount $srcAccountName `
     -Rule $rule1,$rule2
 
 # Create the same policy on the source account.
-Set-AzStorageObjectReplicationPolicy -ResourceGroupName $rgname `
+Set-AzStorageObjectReplicationPolicy -ResourceGroupName $rgName `
     -StorageAccountName $srcAccountName `
     -InputObject $destPolicy
 ```
@@ -218,7 +218,7 @@ az storage account or-policy show \
 
 ## Configure object replication using a JSON file
 
-If you do not have permissions to the source storage account or if you want to use more than 10 container pairs, then you can configure object replication on the destination account and provide a JSON file that contains the policy definition to another user to create the same policy on the source account. For example, if the source account is in a different Azure AD tenant from the destination account, then you can use this approach to configure object replication.
+If you don't have permissions to the source storage account or if you want to use more than 10 container pairs, then you can configure object replication on the destination account and provide a JSON file that contains the policy definition to another user to create the same policy on the source account. For example, if the source account is in a different Azure AD tenant from the destination account, then you can use this approach to configure object replication.
 
 > [!NOTE]
 > Cross-tenant object replication is permitted by default for a storage account. To prevent replication across tenants, you can set the **AllowCrossTenantReplication** property (preview) to disallow cross-tenant object replication for your storage accounts. For more information, see [Prevent object replication across Azure Active Directory tenants](object-replication-prevent-cross-tenant-policies.md).
@@ -252,7 +252,7 @@ You can then download a JSON file containing the policy definition that you can
 
 The downloaded JSON file includes the policy ID that Azure Storage created for the policy on the destination account. You must use the same policy ID to configure object replication on the source account.
 
-Keep in mind that uploading a JSON file to create a replication policy for the destination account via the Azure portal does not automatically create the same policy in the source account. Another user must create the policy on the source account before Azure Storage begins replicating objects.
+Keep in mind that uploading a JSON file to create a replication policy for the destination account via the Azure portal doesn't automatically create the same policy in the source account. Another user must create the policy on the source account before Azure Storage begins replicating objects.
 
 # [PowerShell](#tab/powershell)
 
@@ -262,7 +262,7 @@ To download a JSON file that contains the replication policy definition for the
 $rgName = "<resource-group>"
 $destAccountName = "<destination-storage-account>"
 
-$destPolicy = Get-AzStorageObjectReplicationPolicy -ResourceGroupName $rgname `
+$destPolicy = Get-AzStorageObjectReplicationPolicy -ResourceGroupName $rgName `
     -StorageAccountName $destAccountName
 $destPolicy | ConvertTo-Json -Depth 5 > c:\temp\json.txt
 ```
@@ -273,7 +273,7 @@ When running the example, be sure to set the `-ResourceGroupName` parameter to t
 
 ```powershell
 $object = Get-Content -Path C:\temp\json.txt | ConvertFrom-Json
-Set-AzStorageObjectReplicationPolicy -ResourceGroupName $rgname `
+Set-AzStorageObjectReplicationPolicy -ResourceGroupName $rgName `
     -StorageAccountName $srcAccountName `
     -PolicyId $object.PolicyId `
     -SourceAccount $object.SourceAccount `
@@ -306,7 +306,7 @@ az storage account or-policy create \
 
 ## Check the replication status of a blob
 
-You can check the replication status for a blob in the source account using the Azure portal, PowerShell, or Azure CLI. Object replication properties are not populated until replication has either completed or failed.
+You can check the replication status for a blob in the source account using the Azure portal, PowerShell, or Azure CLI. Object replication properties aren't populated until replication has either completed or failed.
 
 # [Azure portal](#tab/portal)
 
@@ -323,7 +323,7 @@ To check the replication status for a blob in the source account in the Azure po
 To check the replication status for a blob in the source account with PowerShell, get the value of the object replication **ReplicationStatus** property, as shown in the following example. Remember to replace values in angle brackets with your own values:
 
 ```powershell
-$ctxSrc = (Get-AzStorageAccount -ResourceGroupName $rgname `
+$ctxSrc = (Get-AzStorageAccount -ResourceGroupName $rgName `
     -StorageAccountName $srcAccountName).Context
 $blobSrc = Get-AzStorageBlob -Container $srcContainerName1 `
     -Context $ctxSrc `
@@ -363,7 +363,7 @@ To remove a replication policy in the Azure portal, follow these steps:
 
 1. Navigate to the source storage account in the Azure portal.
 1. Under **Settings**, select **Object replication**.
-1. Click the **More** button next to the policy name.
+1. Select the **More** button next to the policy name.
 1. Select **Delete Rules**.
 
 # [PowerShell](#tab/powershell)
@@ -372,12 +372,12 @@ To remove a replication policy, delete the policy from both the source account a
 
 ```powershell
 # Remove the policy from the destination account.
-Remove-AzStorageObjectReplicationPolicy -ResourceGroupName $rgname `
+Remove-AzStorageObjectReplicationPolicy -ResourceGroupName $rgName `
     -StorageAccountName $destAccountName `
     -PolicyId $destPolicy.PolicyId
 
 # Remove the policy from the source account.
-Remove-AzStorageObjectReplicationPolicy -ResourceGroupName $rgname `
+Remove-AzStorageObjectReplicationPolicy -ResourceGroupName $rgName `
     -StorageAccountName $srcAccountName `
     -PolicyId $destPolicy.PolicyId
 ```

articles/storage/blobs/soft-delete-blob-enable.md

@@ -7,7 +7,7 @@ author: tamram
 
 ms.service: storage
 ms.topic: how-to
-ms.date: 06/29/2021
+ms.date: 05/05/2022
 ms.author: tamram
 ms.subservice: blobs  
 ms.custom: devx-track-azurepowershell
@@ -19,7 +19,7 @@ Blob soft delete protects an individual blob and its versions, snapshots, and me
 
 Blob soft delete is part of a comprehensive data protection strategy for blob data. To learn more about Microsoft's recommendations for data protection, see [Data protection overview](data-protection-overview.md).
 
-Blob soft delete is disabled by default for a new storage account. You can enable or disable soft delete for a storage account at any time by using the Azure portal, PowerShell, or Azure CLI.
+Blob soft delete is enabled by default for a new storage account. You can enable or disable soft delete for a storage account at any time by using the Azure portal, PowerShell, or Azure CLI.
 
 ## Enable blob soft delete