Merge pull request #196860 from tamram/tamram22-0502

clarify number of containers to migrate to VLW at once

Author: PRMerger12

articles/storage/blobs/immutable-time-based-retention-policy-overview.md

@@ -7,7 +7,7 @@ author: tamram
 
 ms.service: storage
 ms.topic: conceptual
-ms.date: 12/01/2021
+ms.date: 05/02/2022
 ms.author: tamram
 ms.subservice: blobs
 ---
@@ -52,7 +52,7 @@ To configure version-level retention policies, you must first enable version-lev
 
 Version-level immutability on the storage account must be enabled when you create the account. When you enable version-level immutability for a new storage account, all containers subsequently created in that account automatically support version-level immutability. It's not possible to disable support for version-level immutability on a storage account after you've enabled it, nor is it possible to create a container without version-level immutability support when it's enabled for the account.
 
-If you have not enabled support for version-level immutability on the storage account, then you can enable support for version-level immutability on an individual container at the time that you create the container. Existing containers can also support version-level immutability, but must undergo a migration process first. This process may take some time and is not reversible. You can migrate only one container at a time per storage account. For more information about migrating a container to support version-level immutability, see [Migrate an existing container to support version-level immutability](immutable-policy-configure-version-scope.md#migrate-an-existing-container-to-support-version-level-immutability).
+If you have not enabled support for version-level immutability on the storage account, then you can enable support for version-level immutability on an individual container at the time that you create the container. Existing containers can also support version-level immutability, but must undergo a migration process first. This process may take some time and is not reversible. You can migrate ten containers at a time per storage account. For more information about migrating a container to support version-level immutability, see [Migrate an existing container to support version-level immutability](immutable-policy-configure-version-scope.md#migrate-an-existing-container-to-support-version-level-immutability).
 
 Version-level time-based retention policies require that [blob versioning](versioning-overview.md) is enabled for the storage account. To learn how to enable blob versioning, see [Enable and manage blob versioning](versioning-enable.md). Keep in mind that enabling versioning may have a billing impact. For more information, see the **Pricing and billing** section in [Blob versioning](versioning-overview.md#pricing-and-billing).
 

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

@@ -7,7 +7,7 @@ author: tamram
 
 ms.service: storage
 ms.topic: how-to
-ms.date: 04/26/2022
+ms.date: 05/02/2022
 ms.author: tamram
 ms.subservice: blobs
 ms.custom: devx-track-azurecli, devx-track-azurepowershell
@@ -41,7 +41,7 @@ To create a replication policy in the Azure portal, follow these steps:
 1. Under **Data management**, select **Object replication**.
 1. Select **Set up replication rules**.
 1. Select the destination subscription and storage account.
-1. In the **Container pairs** section, select a source container from the source account, and a destination container from the destination account. You can create up to 10 container pairs per replication policy using this method. If you want to configure more than 10 container pairs (up to 1,000), see [Configure object replication using a JSON file](#configure-object-replication-using-a-json-file).
+1. In the **Container pairs** section, select a source container from the source account, and a destination container from the destination account. You can create up to 10 container pairs per replication policy from the Azure portal. To configure more than 10 container pairs (up to 1000), see [Configure object replication using a JSON file](#configure-object-replication-using-a-json-file).
 
     The following image shows a set of replication rules.
 

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

@@ -7,7 +7,7 @@ author: tamram
 
 ms.service: storage
 ms.topic: conceptual
-ms.date: 04/26/2022
+ms.date: 05/02/2022
 ms.author: tamram
 ms.subservice: blobs
 ms.custom: devx-track-azurepowershell
@@ -39,6 +39,8 @@ Enabling change feed and blob versioning may incur additional costs. For more de
 
 Object replication is supported for general-purpose v2 storage accounts and premium block blob accounts. Both the source and destination accounts must be either general-purpose v2 or premium block blob accounts. Object replication supports block blobs only; append blobs and page blobs are not supported.
 
+Customer-managed failover is not supported for either the source or the destination account in an object replication policy.
+
 ## How object replication works
 
 Object replication asynchronously copies block blobs in a container according to rules that you configure. The contents of the blob, any versions associated with the blob, and the blob's metadata and properties are all copied from the source container to the destination container.
@@ -84,7 +86,7 @@ The source and destination accounts may be in the same region or in different re
 
 ### Replication rules
 
-Replication rules specify how Azure Storage will replicate blobs from a source container to a destination container. You can specify up to 1,000 replication rules for each replication policy. Each replication rule defines a single source and destination container, and each source and destination container can be used in only one rule, meaning that a maximum of 1,000 source containers and 1,000 destination containers may participate in a single replication policy.
+Replication rules specify how Azure Storage will replicate blobs from a source container to a destination container. You can specify up to 1000 replication rules for each replication policy. Each replication rule defines a single source and destination container, and each source and destination container can be used in only one rule, meaning that a maximum of 1000 source containers and 1000 destination containers may participate in a single replication policy.
 
 When you create a replication rule, by default only new block blobs that are subsequently added to the source container are copied. You can specify that both new and existing block blobs are copied, or you can define a custom copy scope that copies block blobs created from a specified time onward.
 

articles/storage/scripts/storage-blobs-container-calculate-billing-size-powershell.md

@@ -2,14 +2,14 @@
 title: Azure PowerShell script sample - Calculate the total billing size of a blob container | Microsoft Docs
 description: Calculate the total size of a container in Azure Blob storage for billing purposes.
 services: storage
-author: fhryo-msft
+author: stevenmatthew
 
 ms.service: storage
 ms.subservice: blobs
 ms.devlang: powershell
 ms.topic: sample
 ms.date: 12/29/2020
-ms.author: fryu
+ms.author: shaas
 ---
 
 # Calculate the total billing size of a blob container

articles/storage/scripts/storage-blobs-container-calculate-size-cli.md

@@ -2,13 +2,13 @@
 title: Azure CLI Script Sample - Calculate blob container size | Microsoft Docs
 description: Calculate the size of a container in Azure Blob storage by totaling the size of the blobs in the container.
 services: storage
-author: tamram
+author: stevenmatthew
 ms.service: storage
 ms.subservice: blobs
 ms.devlang: azurecli
 ms.topic: sample
 ms.date: 03/01/2022
-ms.author: tamram 
+ms.author: shaas 
 ms.custom: devx-track-azurecli
 ---
 

articles/storage/scripts/storage-blobs-container-calculate-size-powershell.md

@@ -3,14 +3,14 @@ title: Calculate size of a blob container with PowerShell
 titleSuffix: Azure Storage
 description: Calculate the size of a container in Azure Blob Storage by totaling the size of each of its blobs.
 services: storage
-author: tamram
+author: stevenmatthew
 
 ms.service: storage
 ms.subservice: blobs
 ms.devlang: powershell
 ms.topic: sample
 ms.date: 12/04/2019
-ms.author: tamram 
+ms.author: shaas 
 ms.custom: devx-track-azurepowershell
 ---
 

articles/storage/scripts/storage-blobs-container-delete-by-prefix-cli.md

@@ -2,13 +2,13 @@
 title: Azure CLI Script Sample - Delete containers by prefix | Microsoft Docs
 description: Delete Azure Storage blob containers based on a container name prefix, then clean up the deployment. See help links for commands used in the script sample.
 services: storage
-author: tamram
+author: stevenmatthew
 ms.service: storage
 ms.subservice: blobs
 ms.devlang: azurecli
 ms.topic: sample
 ms.date: 03/01/2022
-ms.author: tamram 
+ms.author: shaas 
 ms.custom: devx-track-azurecli
 ---
 

articles/storage/scripts/storage-blobs-container-delete-by-prefix-powershell.md

@@ -2,14 +2,14 @@
 title: Azure PowerShell Script Sample - Delete containers by prefix | Microsoft Docs
 description: Read an example that shows how to delete Azure Blob storage based on a prefix in the container name, using Azure PowerShell.
 services: storage
-author: tamram
+author: stevenmatthew
 
 ms.service: storage
 ms.subservice: blobs
 ms.devlang: powershell
 ms.topic: sample
 ms.date: 06/13/2017
-ms.author: tamram 
+ms.author: shaas 
 ms.custom: devx-track-azurepowershell
 ---
 

articles/storage/scripts/storage-common-rotate-account-keys-cli.md

@@ -2,13 +2,13 @@
 title: Azure CLI Script Sample - Rotate storage account access keys | Microsoft Docs
 description: Create an Azure Storage account, then retrieve and rotate its account access keys.
 services: storage
-author: tamram
+author: stevenmatthew
 ms.service: storage
 ms.subservice: blobs
 ms.devlang: azurecli
 ms.topic: sample
 ms.date: 03/02/2022
-ms.author: tamram 
+ms.author: shaas 
 ms.custom: devx-track-azurecli
 ---
 

articles/storage/scripts/storage-common-rotate-account-keys-powershell.md

@@ -3,14 +3,14 @@ title: Rotate storage account access keys with PowerShell
 titleSuffix: Azure Storage
 description: Create an Azure Storage account, then retrieve and rotate one of its account access keys.
 services: storage
-author: tamram
+author: stevenmatthew
 
 ms.service: storage
 ms.subservice: blobs
 ms.devlang: powershell
 ms.topic: sample
 ms.date: 12/04/2019
-ms.author: tamram 
+ms.author: shaas 
 ms.custom: devx-track-azurepowershell
 ---