You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/storage/common/redundancy-migration.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -69,7 +69,7 @@ The following table provides an overview of how to switch between replication ty
69
69
70
70
Depending on your scenario from the [changing redundancy configuration](#changing-redundancy-configuration) section, use one of the following methods to change your replication settings.
71
71
72
-
### Change the redundancy configuration using Azure Portal, PowerShell, or Azure CLI
72
+
### Change the redundancy configuration using Azure portal, PowerShell, or Azure CLI
73
73
74
74
In most cases you can use the Azure portal, PowerShell, or the Azure CLI to change the geo-redundant or read access (RA) replication setting for a storage account.
75
75
@@ -131,12 +131,12 @@ There are two ways to initiate a conversion:
131
131
132
132
Instead of opening a support request, customers in most regions can start a conversion and monitor its progress. This option eliminates potential delays related to creating and managing support requests. For help determining the regions in which customer-initiated conversion is supported, see the [region limitations](#region) article.
133
133
134
-
Customer-initiated conversion can be comleted in supported regions using the Azure Portal, PowerShell, or the Azure CLI. After brinitiated, the conversion could still take up to 72 hours to begin.
134
+
Customer-initiated conversion can be completed in supported regions using the Azure portal, PowerShell, or the Azure CLI. After initiation, the conversion could still take up to 72 hours to begin.
135
135
136
-
[!IMPORTANT]
136
+
> [!IMPORTANT]
137
137
> There is no SLA for completion of a conversion.
138
138
>
139
-
>If you need more control over when a conversion begins and finishes, consider a [Manual migration](#manual-migration). Generally, the more data you have in your account, the longer it takes to replicate that data to other zones or regions.
139
+
>If you need more control over when a conversion begins and finishes, consider a [Manual migration](#manual-migration). Generally, the more data you have in your account, the longer it takes to replicate that data to other zones or regions.
140
140
>
141
141
> For more information about the timing of a customer-initiated conversion, see [Timing and frequency](#timing-and-frequency).
0 commit comments