Skip to content

Commit fc9839f

Browse files
authored
Update classic-account-migration-process.md
1 parent 0369821 commit fc9839f

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -61,8 +61,8 @@ The Validation step analyzes the state of resources in the classic deployment mo
6161

6262
The Validation step does not check for virtual machine (VM) disks that may be associated with the storage account. You must check your storage accounts manually to determine whether they support VM disks. For more information, see the following articles:
6363

64-
- [How to migrate your classic storage accounts to Azure Resource Manager](classic-account-migrate.md)
65-
- [Migrate to Resource Manager with PowerShell](../../virtual-machines/migration-classic-resource-manager-ps.md#step-52-migrate-a-storage-account)
64+
- [Migrate classic storage accounts to Azure Resource Manager](classic-account-migrate.md)
65+
- [Migrate VMs to Resource Manager with PowerShell](../../virtual-machines/migration-classic-resource-manager-ps.md#step-52-migrate-a-storage-account)
6666
- [Migrate VMs to Resource Manager using Azure CLI](../../virtual-machines/migration-classic-resource-manager-cli.md#step-5-migrate-a-storage-account)
6767

6868
Keep in mind that it's not possible to check for every constraint that the Azure Resource Manager stack might impose on the storage account during migration. Some constraints are only checked when the resources undergo transformation in the next step of migration (the Prepare step).

0 commit comments

Comments
 (0)