Skip to content

Commit f6ed3c4

Browse files
committed
fix images
1 parent a356801 commit f6ed3c4

File tree

7 files changed

+12
-13
lines changed

7 files changed

+12
-13
lines changed

articles/storage/blobs/TOC.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -336,7 +336,7 @@ items:
336336
- name: Understand the migration process
337337
href: ../common/classic-account-migration-process.md?toc=/azure/storage/blobs/toc.json&bc=/azure/storage/blobs/breadcrumb/toc.json
338338
- name: Migrate a classic storage account to Resource Manager
339-
href: ../common/storage-account-migrate-classic.md?toc=/azure/storage/blobs/toc.json&bc=/azure/storage/blobs/breadcrumb/toc.json
339+
href: ../common/classic-account-migrate.md?toc=/azure/storage/blobs/toc.json&bc=/azure/storage/blobs/breadcrumb/toc.json
340340
- name: Create and manage containers
341341
items:
342342
- name: Manage containers (Azure portal)

articles/storage/common/classic-account-migrate.md

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -62,12 +62,19 @@ To migrate a classic storage account to the Azure Resource Manager deployment mo
6262

6363
:::image type="content" source="./media/classic-account-migrate/validate-storage-account.png" alt-text="Screenshot showing how to migrate your classic storage account to Azure Resource Manager." lightbox="./media/classic-account-migrate/validate-storage-account.png":::
6464

65-
1. After a successful validation, click on **Prepare** to begin the migration.
65+
1. After a successful validation, click on **Prepare** button to simulate the migration.
6666

6767
> [!IMPORTANT]
6868
> There may be a delay of a few minutes after validation is complete before the Prepare button is enabled.
6969
70-
1. Type **yes** to confirm, then select **Commit** to complete the migration.
70+
1. If the Prepare step completes successfully, you'll see a link to the new resource group. Select that link to navigate to the new resource group. The migrated storage account appears under the **Resources** tab in the **Overview** page for the new resource group.
71+
72+
At this point you can compare the configuration and data in the classic storage account to the newly migrated storage account. You'll see both in the list of storage accounts in the portal. Both the classic account and the migrated account have the same name.
73+
74+
:::image type="content" source="media/classic-account-migrate/compare-classic-migrated-accounts.png" alt-text="Screenshot showing the results of the Prepare step in the Azure portal." lightbox=="media/classic-account-migrate/compare-classic-migrated-accounts.png":::
75+
76+
1. If you're not satisfied with the results of the migration, select **Abort** to delete the new storage account and resource group. You can then address any problems and try again.
77+
1. When you're ready to commit, type **yes** to confirm, then select **Commit** to complete the migration.
7178

7279
# [PowerShell](#tab/azure-powershell)
7380

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

Lines changed: 2 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -51,19 +51,11 @@ Storage accounts created using the classic deployment model will follow the [Mod
5151

5252
To migrate your classic storage accounts, you should:
5353

54-
1. Identify all classic storage accounts in your subscription(s).
54+
1. Identify all classic storage accounts in your subscription.
5555
1. Migrate any classic storage accounts to Azure Resource Manager.
5656
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.
5757

58-
For step-by-step instructions, see [Migrate a classic storage account to Azure Resource Manager](storage-account-migrate-classic.md).
59-
60-
## Unsupported features and known issues
61-
62-
- [Customer-managed failover](storage-disaster-recovery-guidance.md) is not supported for classic storage accounts.
63-
- Challenges locating classic OS disks or images - https://supportability.visualstudio.com/AzureIaaSVM/_wiki/wikis/AzureIaaSVM/496154/Locate-Classic-OS-Disks-VM-Images-in-Storage-Account_Storage
64-
- Classic artifacts blocking storage account deletion - https://supportability.visualstudio.com/AzureIaaSVM/_wiki/wikis/AzureIaaSVM/496138/Delete-Classic-Storage-Account-Portal_Storage
65-
- Customers that only have internal billable Classic Storage and have no visibility into those resources and no ability to migrate those resources to ARM - https://supportability.visualstudio.com/AzureIaaSVM/_wiki/wikis/AzureIaaSVM/606146/Classic-Storage-Account-Retirement-Message_Storage
66-
- Classic StgAcct not showing in the portal - https://supportability.visualstudio.com/AzureIaaSVM/_wiki/wikis/AzureIaaSVM/496225/Storage-Account-Not-Visible-in-Portal-or-PowerShell_Storage
58+
For step-by-step instructions, see [How to migrate your classic storage accounts to Azure Resource Manager](classic-account-migrate.md).
6759

6860
## See also
6961

54 KB
Loading
-31.5 KB
Loading

0 commit comments

Comments
 (0)