Merge pull request #225022 from tamram/tamram23-0125a

incorp public PRs for LCM, versioning

Author: American-Dipper

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

@@ -5,7 +5,7 @@ description: Use Azure Storage lifecycle management policies to create automated
 author: normesta
 
 ms.author: normesta
-ms.date: 01/05/2023
+ms.date: 01/25/2023
 ms.service: storage
 ms.subservice: common
 ms.topic: conceptual
@@ -138,7 +138,7 @@ Filters include:
 | Filter name | Filter type | Notes | Is Required |
 |-------------|-------------|-------|-------------|
 | blobTypes   | An array of predefined enum values. | The current release supports `blockBlob` and `appendBlob`. Only delete is supported for `appendBlob`, set tier isn't supported. | Yes |
-| prefixMatch | An array of strings for prefixes to be matched. Each rule can define up to 10 case-sensitive prefixes. A prefix string must start with a container name. For example, if you want to match all blobs under `https://myaccount.blob.core.windows.net/sample-container/blob1/...` for a rule, the prefixMatch is `sample-container/blob1`. | If you don't define prefixMatch, the rule applies to all blobs within the storage account. | No |
+| prefixMatch | An array of strings for prefixes to be matched. Each rule can define up to 10 case-sensitive prefixes. A prefix string must start with a container name. For example, if you want to match all blobs under `https://myaccount.blob.core.windows.net/sample-container/blob1/...` for a rule, the prefixMatch is `sample-container/blob1`.<br /><br />To match the blob name exactly, include the trailing forward slash ('/'), *e.g.*, `sample-container/blob1/`. To match the name pattern, omit the trailing forward slash, *e.g.*, `sample-container/blob1`. | If you don't define prefixMatch, the rule applies to all blobs within the storage account. | No |
 | blobIndexMatch | An array of dictionary values consisting of blob index tag key and value conditions to be matched. Each rule can define up to 10 blob index tag condition. For example, if you want to match all blobs with `Project = Contoso` under `https://myaccount.blob.core.windows.net/` for a rule, the blobIndexMatch is `{"name": "Project","op": "==","value": "Contoso"}`. | If you don't define blobIndexMatch, the rule applies to all blobs within the storage account. | No |
 
 To learn more about the blob index feature together with known issues and limitations, see [Manage and find data on Azure Blob Storage with blob index](storage-manage-find-blobs.md).

articles/storage/blobs/media/versioning-enable/portal-list-blob-versions.png

@@ -6,7 +6,7 @@ author: normesta
 
 ms.service: storage
 ms.topic: conceptual
-ms.date: 08/09/2022
+ms.date: 01/25/2023
 ms.author: normesta
 ms.subservice: blobs
 ms.custom: devx-track-azurepowershell
@@ -55,6 +55,8 @@ Object replication asynchronously copies block blobs in a container according to
 
 Object replication requires that blob versioning is enabled on both the source and destination accounts. When a replicated blob in the source account is modified, a new version of the blob is created in the source account that reflects the previous state of the blob, before modification. The current version in the source account reflects the most recent updates. Both the current version and any previous versions are replicated to the destination account. For more information about how write operations affect blob versions, see [Versioning on write operations](versioning-overview.md#versioning-on-write-operations).
 
+If your storage account has object replication policies in effect, you cannot disable blob versioning for that account. You must delete any object replication policies on the account before disabling blob versioning.
+
 ### Deleting a blob in the source account
 
 When a blob in the source account is deleted, the current version of the blob becomes a previous version, and there's no longer a current version. All existing previous versions of the blob are preserved. This state is replicated to the destination account. For more information about how to delete operations affect blob versions, see [Versioning on delete operations](versioning-overview.md#versioning-on-delete-operations).

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

@@ -7,7 +7,7 @@ author: normesta
 
 ms.service: storage
 ms.topic: how-to
-ms.date: 06/07/2021
+ms.date: 01/25/2023
 ms.author: normesta
 ms.subservice: blobs
 ms.custom: devx-track-azurepowershell
@@ -21,6 +21,8 @@ This article shows how to enable or disable blob versioning for the storage acco
 
 ## Enable blob versioning
 
+You can enable blob versioning with the Azure portal, PowerShell, Azure CLI, or an Azure Resource Manager template.
+
 # [Azure portal](#tab/portal)
 
 To enable blob versioning for a storage account in the Azure portal:
@@ -29,7 +31,7 @@ To enable blob versioning for a storage account in the Azure portal:
 1. Under **Blob service**, choose **Data protection**.
 1. In the **Versioning** section, select **Enabled**.
 
-:::image type="content" source="media/versioning-enable/portal-enable-versioning.png" alt-text="Screenshot showing how to enable blob versioning in Azure portal":::
+    :::image type="content" source="media/versioning-enable/portal-enable-versioning.png" alt-text="Screenshot showing how to enable blob versioning in Azure portal":::
 
 # [PowerShell](#tab/powershell)
 
@@ -91,6 +93,63 @@ For more information about deploying resources with templates in the Azure porta
 
 ---
 
+## List blob versions
+
+To display a blob's versions, use the Azure portal, PowerShell, or Azure CLI. You can also list a blob's versions using one of the Blob Storage SDKs.
+
+# [Azure portal](#tab/portal)
+
+To list a blob's versions in the Azure portal:
+
+1. Navigate to your storage account in the portal, then navigate to the container that contains your blob.
+1. Select the blob for which you want to list versions.
+1. Select the **Versions** tab to display the blob's versions.
+
+    :::image type="content" source="media/versioning-enable/portal-list-blob-versions.png" alt-text="Screenshot showing how to list blob versions in the Azure portal":::
+
+# [PowerShell](#tab/powershell)
+
+To list a blob's versions with PowerShell, call the [Get-AzStorageBlob](/powershell/module/az.storage/get-azstorageblob) command with the `-IncludeVersion` parameter:
+
+```azurepowershell
+$account = Get-AzStorageAccount -ResourceGroupName <resource-group> -Name <storage-account>
+$ctx = $account.Context
+$container = "<container-name>"
+
+$blobs = Get-AzStorageBlob -Container $container -Prefix "ab" -IncludeVersion -Context $ctx
+
+foreach($blob in $blobs)
+{
+    Write-Host $blob.Name
+    Write-Host $blob.VersionId
+    Write-Host $blob.IsLatestVersion
+}
+```
+
+# [Azure CLI](#tab/azure-cli)
+
+To list a blob's versions with Azure CLI, call the [az storage blob directory list](/cli/azure/storage/blob/directory#az-storage-blob-directory-list) command with the `--include v` parameter:
+
+```azurecli
+storageAccount="<storage-account>"
+containerName="<container-name>"
+
+az storage blob list \
+    --container-name $containerName \
+    --prefix "ab" \
+    --query "[[].name, [].versionId]" \
+    --account-name $storageAccount \
+    --include v \
+    --auth-mode login \
+    --output tsv 
+```
+
+# [Template](#tab/template)
+
+N/A
+
+---
+
 ## Modify a blob to trigger a new version
 
 The following code example shows how to trigger the creation of a new version with the Azure Storage client library for .NET, version [12.5.1](https://www.nuget.org/packages/Azure.Storage.Blobs/12.5.1) or later. Before running this example, make sure you have enabled versioning for your storage account.
@@ -99,7 +158,7 @@ The example creates a block blob, and then updates the blob's metadata. Updating
 
 :::code language="csharp" source="~/azure-storage-snippets/blobs/howto/dotnet/dotnet-v12/CRUD.cs" id="Snippet_UpdateVersionedBlobMetadata":::
 
-## List blob versions
+## List blob versions with .NET
 
 To list blob versions or snapshots with the .NET v12 client library, specify the [BlobStates](/dotnet/api/azure.storage.blobs.models.blobstates) parameter with the **Version** field.
 

articles/storage/blobs/versioning-enable.md

@@ -7,7 +7,7 @@ author: normesta
 
 ms.service: storage
 ms.topic: conceptual
-ms.date: 01/20/2023
+ms.date: 01/25/2023
 ms.author: normesta
 ms.subservice: blobs 
 ms.custom: devx-track-azurepowershell
@@ -122,6 +122,8 @@ After versioning is disabled, modifying the current version creates a blob that
 
 You can read or delete versions using the version ID after versioning is disabled. You can also list a blob's versions after versioning is disabled.
 
+Object replication relies on blob versioning. Before you can disable blob versioning, you must delete any object replication policies on the account. For more information about object replication, see [Object replication for block blobs](object-replication-overview.md).
+
 The following diagram shows how modifying a blob after versioning is disabled creates a blob that is not versioned. Any existing versions associated with the blob persist.
 
 :::image type="content" source="media/versioning-overview/modify-base-blob-versioning-disabled.png" alt-text="Diagram showing that modification of a current version after versioning is disabled creates a blob that is not a version.":::

articles/storage/blobs/versioning-overview.md

@@ -7,7 +7,7 @@ author: jimmart-dev
 
 ms.service: storage
 ms.topic: conceptual
-ms.date: 10/25/2022
+ms.date: 01/25/2023
 ms.author: jammart
 ms.reviewer: dineshm
 ms.subservice: common