Skip to content

Commit 45edc2c

Browse files
authored
Fix typo in classic-account-migration-overview.md
1 parent f7d051d commit 45edc2c

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/storage/common/classic-account-migration-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ If your applications are using Azure Service Manager classic APIs to manage clas
5050
On or after 1 November 2024:
5151

5252
- Your ability to perform write operations using the classic service model APIs, including PUT and PATCH, will be limited. You will only be able to perform read and list operations using the classic service model APIs.
53-
- Your remaining classic storage accounts will be migrated to Azure Resource Manager on your behalf on a rolling schedule. Your data will continue to be stored, but any applications that use the classic service model APIs to perform management plane operations will experience disruptions if you're actively using any write operations. Write operations will only be available through the Azure Resource Manager APIs after your account(s) have been migrated. Once migration is completed, you will see two storage accounts with the same name through interfaces such as the Azure Portal. This is by design. One account is your classic storage account and the other is your Azure Resource Manager and Storage Resource Provider account. To perform any management operations that udpate your storage account, you must use Azure Resource Manager and Storage Resource Provider APIs.
53+
- Your remaining classic storage accounts will be migrated to Azure Resource Manager on your behalf on a rolling schedule. Your data will continue to be stored, but any applications that use the classic service model APIs to perform management plane operations will experience disruptions if you're actively using any write operations. Write operations will only be available through the Azure Resource Manager APIs after your account(s) have been migrated. Once migration is completed, you will see two storage accounts with the same name through interfaces such as the Azure Portal. This is by design. One account is your classic storage account and the other is your Azure Resource Manager and Storage Resource Provider account. To perform any management operations that update your storage account, you must use Azure Resource Manager and Storage Resource Provider APIs.
5454
- Note: There are no impacts on the availability of the data plane APIs before, during, or after the migration of classic storage accounts.
5555

5656
## What actions should I take?

0 commit comments

Comments
 (0)