Added balance of Failover updates/articles

Author: stevenmatthew

articles/storage/common/last-sync-time-get.md

@@ -23,7 +23,7 @@ This article describes how to check the **Last Sync Time** property for your sto
 
 ## About the Last Sync Time property
 
-Because geo-replication is asynchronous, it is possible that data written to the primary region has not yet been written to the secondary region at the time an outage occurs. The **Last Sync Time** property indicates the most recent time that data from the primary region is guaranteed to have been written to the secondary region. For accounts that have a hierarchical namespace, the same **Last Sync Time** property also applies to the metadata managed by the hierarchical namespace, including ACLs. All data and metadata written prior to the last sync time  is available on the secondary, while data and metadata written after the last sync time may not have been written to the secondary, and may be lost. Use this property in the event of an outage to estimate the amount of data loss you may incur by initiating an account failover.
+Because geo-replication is asynchronous, it is possible that data written to the primary region has not yet been written to the secondary region at the time an outage occurs. The **Last Sync Time** property indicates the most recent time that data from the primary region is guaranteed to have been written to the secondary region. For accounts that have a hierarchical namespace, the same **Last Sync Time** property also applies to the metadata managed by the hierarchical namespace, including ACLs. All data and metadata written prior to the last sync time  is available on the secondary, while data and metadata written after the last sync time may not have been written to the secondary, and may be lost. Use this property in the event of an outage to estimate the amount of data loss you may incur by initiating a customer-managed (unplanned) failover.
 
 The **Last Sync Time** property is a GMT date/time value.
 

articles/storage/common/redundancy-migration.md

@@ -15,14 +15,14 @@ ms.custom: engagement-fy23, references_regions, devx-track-azurepowershell
 
 <!--
 Initial: 81 (3717/68)
-Current: 98 (3765/4)
+Current: 98 (3761/0)
 -->
 
-# Change the redundancy configuration for a storage account
+# Change how a storage account is replicated
 
 Azure Storage always stores multiple copies of your data to protect it in the face of both planned and unplanned events. These events include transient hardware failures, network or power outages, and massive natural disasters. Data redundancy ensures that your storage account meets the [Service-Level Agreement (SLA) for Azure Storage](https://azure.microsoft.com/support/legal/sla/storage/), even in the face of failures.
 
-This article describes the process of changing replication setting(s) for an existing storage account.
+This article describes the process of changing replication settings for an existing storage account.
 
 ## Options for changing the replication type
 
@@ -98,6 +98,24 @@ Set-AzStorageAccount -ResourceGroupName <resource_group> `
     -SkuName <sku>
 ```
 
+You can also add or remove zone redundancy to your storage account. To change between locally redundant and zone-redundant storage with PowerShell, call the [Start-AzStorageAccountMigration](/powershell/module/az.storage/start-azstorageaccountmigration) command and specify the `-TargetSku` parameter:
+
+```powershell
+Start-AzStorageAccountMigration
+    -AccountName <String>
+    -ResourceGroupName <String>
+    -TargetSku <String>
+    -AsJob
+```
+
+To track the current migration status of the conversion initiated on your storage account, call the [Get-AzStorageAccountMigration](/powershell/module/az.storage/get-azstorageaccountmigration) cmdlet:
+
+```powershell
+Get-AzStorageAccountMigration
+   -AccountName <String>
+   -ResourceGroupName <String>
+```
+
 # [Azure CLI](#tab/azure-cli)
 
 You can use the Azure CLI to change the redundancy options for your storage account.
@@ -111,6 +129,25 @@ az storage account update \
     --sku <sku>
 ```
 
+You can also add or remove zone redundancy to your storage account. To change between locally redundant and zone-redundant storage with Azure CLI, call the [az storage account migration start](/cli/azure/storage/account/migration#az-storage-account-migration-start) command and specify the `--sku` parameter:
+
+```azurecli-interactive
+az storage account migration start  \
+    -- account-name <string> \
+    -- g <string> \
+    --sku <string> \
+    --no-wait
+```
+
+To track the current migration status of the conversion initiated on your storage account, use the [az storage account migration show](/cli/azure/storage/account/migration#az-storage-account-migration-show) command:
+
+```azurecli-interactive
+az storage account migration show 
+    --account-name <string>
+    - g <sting>
+    -n "default"
+```
+
 ---
 
 ### Perform a conversion