Merge pull request #4874 from sushantrane/srane-replicate-data-globally-update

Changes to Replicate data globally panel for azure cosmos db

Author: Stacyrch140

articles/cosmos-db/cassandra/support.md

@@ -350,7 +350,7 @@ Azure Cosmos DB supports Azure role-based access control (Azure RBAC) for provis
 
 ## Keyspace and Table options
 
-The options for region name, class, replication_factor, and datacenter in the `CREATE KEYSPACE` command are ignored currently. The system uses the underlying Azure Cosmos DB's [global distribution](../global-distribution.md) replication method to add the regions. If you need the cross-region presence of data, you can enable it at the account level with PowerShell, CLI, or the Azure portal. For more information, see [Add regions to your database account](../how-to-manage-database-account.yml#add-remove-regions-from-your-database-account).
+The options for region name, class, replication_factor, and datacenter in the `CREATE KEYSPACE` command are ignored currently. The system uses the underlying Azure Cosmos DB's [global distribution](../global-distribution.md) replication method to add the regions. If you need the cross-region presence of data, you can enable it at the account level with PowerShell, CLI, or the Azure portal. For more information, see [Add regions to your database account](../how-to-manage-database-account.yml#add-or-remove-regions-from-your-database-account).
 
 Durable_writes can't be disabled because Azure Cosmos DB ensures every write is durable. In every region, Azure Cosmos DB replicates the data across the replica set that is made up of four replicas and this replica set [configuration](../global-distribution.md) can't be modified.
 

articles/cosmos-db/data-residency.md

@@ -20,7 +20,7 @@ In Azure Cosmos DB, you can configure your data and backups to remain in a singl
 
 ## Residency requirements for data
 
-In Azure Cosmos DB, you must explicitly configure the cross-region data replication. Learn how to configure geo-replication using [Azure portal](how-to-manage-database-account.yml#add-remove-regions-from-your-database-account), [Azure CLI](scripts/cli/common/regions.md). To meet data residency requirements, you can create an Azure Policy definition that allows certain regions to prevent data replication to unwanted regions.
+In Azure Cosmos DB, you must explicitly configure the cross-region data replication. Learn how to configure geo-replication using [Azure portal](how-to-manage-database-account.yml#add-or-remove-regions-from-your-database-account), [Azure CLI](scripts/cli/common/regions.md). To meet data residency requirements, you can create an Azure Policy definition that allows certain regions to prevent data replication to unwanted regions.
 
 ## Residency requirements for backups
 

articles/cosmos-db/distribute-data-globally.md

@@ -65,6 +65,6 @@ With Azure Cosmos DB, you can add or remove the regions associated with your acc
 * [Global distribution - under the hood](global-distribution.md)
 * [How to configure multi-region writes in your applications](how-to-multi-master.md)
 * [Configure multiple write-regions](how-to-manage-database-account.yml#configure-multiple-write-regions)
-* [Add or remove regions from your Azure Cosmos DB account](how-to-manage-database-account.yml#add-remove-regions-from-your-database-account)
+* [Add or remove regions from your Azure Cosmos DB account](how-to-manage-database-account.yml#add-or-remove-regions-from-your-database-account)
 * [Create a custom conflict resolution policy for API for NoSQL accounts](how-to-manage-conflicts.md#create-a-custom-conflict-resolution-policy)
 * [Programmable consistency models in Azure Cosmos DB](consistency-levels.md)

articles/cosmos-db/global-distribution.md

@@ -98,7 +98,7 @@ For complete details on consistency level semantics and guarantees, see [Consist
 
 Next learn how to configure global distribution by using the following articles:
 
-* [Add/remove regions from your database account](how-to-manage-database-account.yml#add-remove-regions-from-your-database-account)
+* [Add/remove regions from your database account](how-to-manage-database-account.yml#add-or-remove-regions-from-your-database-account)
 * [How to create a custom conflict resolution policy](how-to-manage-conflicts.md#create-a-custom-conflict-resolution-policy)
 * Trying to do capacity planning for a migration to Azure Cosmos DB? You can use information about your existing database cluster for capacity planning.
     * If all you know is the number of vcores and servers in your existing database cluster, read about [estimating request units using vCores or vCPUs](convert-vcore-to-request-unit.md) 

articles/cosmos-db/how-to-manage-conflicts.md

@@ -535,7 +535,7 @@ Learn about the following Azure Cosmos DB concepts:
 - [Global distribution - under the hood](global-distribution.md)
 - [How to configure multi-region writes in your applications](how-to-multi-master.md)
 - [Configure clients for multihoming](how-to-manage-database-account.yml#configure-multiple-write-regions)
-- [Add or remove regions from your Azure Cosmos DB account](how-to-manage-database-account.yml#add-remove-regions-from-your-database-account)
+- [Add or remove regions from your Azure Cosmos DB account](how-to-manage-database-account.yml#add-or-remove-regions-from-your-database-account)
 - [How to configuremulti-region writes in your applications](how-to-multi-master.md).
 - [Partitioning and data distribution](partitioning.md)
 - [Indexing in Azure Cosmos DB](index-policy.md)

articles/cosmos-db/how-to-manage-database-account.yml

@@ -109,34 +109,39 @@ procedureSection:
 
           :::image type="content" source="~/reusable-content/ce-skilling/azure/media/cosmos-db/azure-cosmos-db-account-created-2.png" alt-text="Screenshot shows the Azure Cosmos DB account page." lightbox="~/reusable-content/ce-skilling/azure/media/cosmos-db/azure-cosmos-db-account-created-2.png":::
   - title: |
-      Add/remove regions from your database account
+      Add or remove regions from your database account
     summary: |
-      > [!TIP]
-      > When a new region is added, all data must be fully replicated and committed into the new region before the region is marked as available. The amount of time this operation takes depends upon how much data is stored within the account. If an [asynchronous throughput scaling operation](scaling-provisioned-throughput-best-practices.md#background-on-scaling-rus) is in progress, the throughput scale-up operation is paused and resumes automatically when the add/remove region operation is complete. Additionally, when removing an existing region, all replication across regions (within [partition sets](./global-distribution.md)) must complete before the region is marked as unavailable.
+      > [!NOTE]
+      > Adding or removing a region is an asynchronous operation that performs consistency checks and transfers data. This can result in long execution times, possibly many hours, depending on the amount of data. During this time, other operations that need to update the account aren't allowed.
+
+      > [!IMPORTANT]
+      > When you add a region, you're billed for the additional RU/s and storage copied to the region.
     steps:
       - |
         Sign in to [Azure portal](https://portal.azure.com).
       - |
         Go to your Azure Cosmos DB account and select **Replicate data globally** in the resource menu.
       - |
-        To add regions, select the hexagons on the map with the **+** label that corresponds to your desired regions. Alternatively, to add a region, select the **+ Add region** option and choose a region from the drop-down menu.
-      - |
-        To remove regions, clear one or more regions from the map by selecting the blue hexagons with check marks. You can also select the *wastebasket* (🗑) icon next to the region on the right side.
+        Select **Manage regions** to open the **Manage regions** pane.
 
+          :::image type="content" source="./media/how-to-manage-database-account/manage-regions.png" alt-text="Screenshot of the Replicate data globally page with manage regions selected.":::
+
+      - |
+        To add a region, select a region from the **Region** dropdown. If you want to enable availability zone support for the region, select the **Availability zone** checkbox, then select **Add**. To learn more, see [Availability zone support for Azure Cosmos DB](/azure/reliability/reliability-cosmos-db-nosql#availability-zone-support).
       - |
-        To save your changes, select **OK**.
+        To remove a region, select the delete icon next to the region you want to remove.
 
-          :::image type="content" source="./media/how-to-manage-database-account/add-region.png" alt-text="Screenshot of the Replicate data globally menu, highlighting a region.":::
+          :::image type="content" source="./media/how-to-manage-database-account/manage-regions-pane.png" alt-text="Screenshot of the Replicate data globally page and the Manage regions pane.":::
 
-        In a single-region write mode, you can't remove the write region. You must fail over to a different region before you can delete the current write region.
+        In single-region write mode, you can't remove the write region. You must fail over to a different region before you can delete the current write region.
 
-        In a multi-region write mode, you can add or remove any region, if you have at least one region.
+        In multi-region write mode, you can add or remove any region, as long as at least one region remains.
 
         ## <a id="configure-multiple-write-regions"></a>Configure multiple write-regions
 
-        Open the **Replicate data globally** tab and select **Enable** to enable multi-region writes. After you enable multi-region writes, all the read regions that you currently have on the account will become read and write regions.
+        In the **Configuration** section of the **Replicate data globally** page, select the **Multi-region writes** checkbox to enable multi-region writes. It will ask for a confirmation to enable this feature. After you enable multi-region writes, all the read regions that you currently have on the account become read and write regions.
 
-        :::image type="content" source="./media/how-to-manage-database-account/single-to-multi-master.png" alt-text="Screenshot of the Replicate data globally menu, highlighting Configure regions and Save.":::
+        :::image type="content" source="./media/how-to-manage-database-account/configure-multi-region-writes.png" alt-text="Screenshot of the Replicate data globally page, highlighting the Multi-region writes checkbox.":::
   - title: |
       Enable service-managed failover for your Azure Cosmos DB account
     summary: |
@@ -157,20 +162,20 @@ procedureSection:
   - title: |
       Perform forced failover for your Azure Cosmos DB Account
     summary: |
-      A forced failover (region offline) enables users to promptly address degraded performance, partial outages, or regional disruptions in a Cosmos DB account. A service-managed failover depends on the service's confirmation and which might take time to activate based on the progression of the outage. A forced failover allows administrators to quickly restore availability for the affected region without waiting for the service-managed failover.
+      A forced failover (Offline region) enables users to promptly address degraded performance, partial outages, or regional disruptions in a Cosmos DB account. A service-managed failover depends on the service's confirmation and which might take time to activate based on the progression of the outage. A forced failover allows administrators to quickly restore availability for the affected region without waiting for the service-managed failover.
     steps:
       - |
         From your Azure Cosmos DB account, open the **Replicate data globally** pane.
       - |
         At the top of the pane, select **Offline region**.
 
-          :::image type="content" source="./media/how-to-manage-database-account/offline-region-failover.png" alt-text="Screenshot that shows the offline region portal menu.":::
+          :::image type="content" source="./media/how-to-manage-database-account/offline-region.png" alt-text="Screenshot that shows the offline region portal menu.":::
       - |
         Review the warning message indicating the possibility of data loss due to un-replicated writes not being available in the region that will be promoted to the new write region based on the failover priority.
       - |
         Select the region to be marked offline, check the box titled **I understand and agree to offline the currently selected region**, and click the **Offline region** button. 
 
-          :::image type="content" source="./media/how-to-manage-database-account/offline-region-warning.png" alt-text="Screenshot that shows the offline region warning.":::
+          :::image type="content" source="./media/how-to-manage-database-account/offline-region-pane.png" alt-text="Screenshot that shows the offline region warning.":::
       - |
         Once completed, the region with the highest failover priority is promoted to the new write region, while the original write region is marked offline.
 
@@ -184,25 +189,21 @@ procedureSection:
   - title: |
       Set failover priorities for your Azure Cosmos DB account
     summary: |
-      After an Azure Cosmos DB account is configured for service-managed failover, the failover priority for regions can be changed.
+      You can configure failover priorities for the regions in your Azure Cosmos DB account to determine the order in which regions are promoted to the write region during a failover.
 
-      > [!IMPORTANT]
-      > You can't modify the write region (failover priority of zero) when the account is configured for service-managed failover. To change the write region, you must disable service-managed failover and do a manual failover.
     steps:
       - |
         From your Azure Cosmos DB account, open the **Replicate data globally** pane.
       - |
-        At the top of the pane, select **Service-Managed Failover**.
+        At the top of the pane, select **Configure failvoer policy**.
 
-        :::image type="content" source="./media/how-to-manage-database-account/replicate-data-globally.png" alt-text="Screenshot showing the Replicate data globally menu.":::
-      - |
-        On the **Service-Managed Failover** pane, make sure that **Enable Service-Managed Failover** is set to **ON**.
+        :::image type="content" source="./media/how-to-manage-database-account/configure-failover-policy.png" alt-text="Screenshot showing the Replicate data globally menu.":::
       - |
-        To modify the failover priority, drag the read regions via the three dots on the left side of the row that appear when you hover over them.
+        On the **Configure failover policy** pane, drag and drop the priorities of read regions to be failed over to as needed.
       - |
-        Select **Save**.
+        Select **OK** to save the failover priority configuration.
 
-        :::image type="content" source="./media/how-to-manage-database-account/automatic-failover.png" alt-text="Screenshot of the Service-Managed failover portal menu.":::
+        :::image type="content" source="./media/how-to-manage-database-account/configure-failover-policy-pane.png" alt-text="Screenshot of the Configure failover policy portal menu.":::
   - title: |
       Change write region for your Azure Cosmos DB Account
     summary: |
@@ -222,13 +223,9 @@ procedureSection:
 
           :::image type="content" source="./media/how-to-manage-database-account/change-write-region.png" alt-text="Screenshot of the change write region menu.":::
       - |
-        The **Change write region** panel provides details to ensure that this operation isn't executed during outage scenarios. Select and acknowledge that this operation is not being performed during regional outages.
-
-          :::image type="content" source="./media/how-to-manage-database-account/change-write-region-details.png" alt-text="Screenshot of the change write region details.":::
-      - |
-        Select a new write region and checkbox to acknowledge the operation confirmation. Click **Ok** to perform the operation.
+        The **Change write region** panel provides details to ensure that this operation isn't executed during outage scenarios. Select a new write region, acknowledge that this operation isn't being performed during regional outages by selecting the checkboxes, and then select **OK** to perform the operation.
 
-          :::image type="content" source="./media/how-to-manage-database-account/change-write-region-confirm.png" alt-text="Screenshot of the change write region confirmation.":::
+          :::image type="content" source="./media/how-to-manage-database-account/change-write-region-pane.png" alt-text="Screenshot of the change write region confirmation.":::
 
 relatedContent:
   - text: Manage Azure Cosmos DB for NoSQL resources using PowerShell