Skip to content

Commit 49a0e55

Browse files
committed
classic account migration, part 2
1 parent 67d7bc9 commit 49a0e55

File tree

2 files changed

+13
-13
lines changed

2 files changed

+13
-13
lines changed

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

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: tamram
77

88
ms.service: storage
99
ms.topic: conceptual
10-
ms.date: 03/27/2023
10+
ms.date: 04/05/2023
1111
ms.author: tamram
1212
ms.subservice: common
1313
---
@@ -29,7 +29,17 @@ Storage accounts created using the classic deployment model will follow the [Mod
2929
> [!WARNING]
3030
> 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.
3131
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
3343

3444
- If you have questions, get answers from community experts in [Microsoft Q&A](/answers/tags/98/azure-storage-accounts).
3545
- 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
4757
1. Under **Problem subtype**, select **Migrate account to new resource group/subscription/region/tenant**.
4858
1. Select **Next**, then follow the instructions to submit your support request.
4959

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-
6060
## See also
6161

6262
- [How to migrate your classic storage accounts to Azure Resource Manager](classic-account-migrate.md)

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: tamram
77

88
ms.service: storage
99
ms.topic: conceptual
10-
ms.date: 03/27/2023
10+
ms.date: 04/05/2023
1111
ms.author: tamram
1212
ms.subservice: common
1313
---

0 commit comments

Comments
 (0)