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/classic-account-migration-overview.md
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ author: tamram
7
7
8
8
ms.service: storage
9
9
ms.topic: conceptual
10
-
ms.date: 03/27/2023
10
+
ms.date: 04/05/2023
11
11
ms.author: tamram
12
12
ms.subservice: common
13
13
---
@@ -29,7 +29,17 @@ Storage accounts created using the classic deployment model will follow the [Mod
29
29
> [!WARNING]
30
30
> If you do not migrate your classic storage accounts to Azure Resource Manager by August 31, 2024, you will permanently lose access to the data in those accounts.
31
31
32
-
## What resources are available for this migration?
32
+
## What actions should I take?
33
+
34
+
To migrate your classic storage accounts, you should:
35
+
36
+
1. Identify all classic storage accounts in your subscription.
37
+
1. Migrate any classic storage accounts to Azure Resource Manager.
38
+
1. Check your applications and logs to determine whether you are dynamically creating, updating, or deleting classic storage accounts from your code, scripts, or templates. If you are, then you need to update your applications to use Azure Resource Manager accounts instead.
39
+
40
+
For step-by-step instructions, see [How to migrate your classic storage accounts to Azure Resource Manager](classic-account-migrate.md).
41
+
42
+
## How to get help
33
43
34
44
- If you have questions, get answers from community experts in [Microsoft Q&A](/answers/tags/98/azure-storage-accounts).
35
45
- If your organization or company has partnered with Microsoft or works with Microsoft representatives, such as cloud solution architects (CSAs) or customer success account managers (CSAMs), contact them for additional resources for migration.
@@ -47,16 +57,6 @@ Storage accounts created using the classic deployment model will follow the [Mod
47
57
1. Under **Problem subtype**, select **Migrate account to new resource group/subscription/region/tenant**.
48
58
1. Select **Next**, then follow the instructions to submit your support request.
49
59
50
-
## What actions should I take?
51
-
52
-
To migrate your classic storage accounts, you should:
53
-
54
-
1. Identify all classic storage accounts in your subscription.
55
-
1. Migrate any classic storage accounts to Azure Resource Manager.
56
-
1. Check your applications and logs to determine whether you are dynamically creating, updating, or deleting classic storage accounts from your code, scripts, or templates. If you are, then you need to update your applications to use Azure Resource Manager accounts instead.
57
-
58
-
For step-by-step instructions, see [How to migrate your classic storage accounts to Azure Resource Manager](classic-account-migrate.md).
59
-
60
60
## See also
61
61
62
62
-[How to migrate your classic storage accounts to Azure Resource Manager](classic-account-migrate.md)
0 commit comments