Skip to content

Commit b011278

Browse files
authored
Update classic-account-migration-process.md
Fix broken link
1 parent e5ae704 commit b011278

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
@@ -7,7 +7,7 @@ author: tamram
77

88
ms.service: storage
99
ms.topic: conceptual
10-
ms.date: 04/10/2023
10+
ms.date: 04/12/2023
1111
ms.author: tamram
1212
ms.subservice: common
1313
---
@@ -63,7 +63,7 @@ The Validation step does not check for virtual machine (VM) disks that may be as
6363

6464
- [How to migrate your classic storage accounts to Azure Resource Manager](classic-account-migrate.md)
6565
- [Migrate to Resource Manager with PowerShell](../../virtual-machines/migration-classic-resource-manager-ps.md#step-52-migrate-a-storage-account)
66-
- [Migrate VMs to Resource Manager using Azure CLI](../../virtual-machines/migration-classic-resource-manager-cli#step-5-migrate-a-storage-account.md
66+
- [Migrate VMs to Resource Manager using Azure CLI](../../virtual-machines/migration-classic-resource-manager-cli#step-5-migrate-a-storage-account.md)
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).
6969

0 commit comments

Comments
 (0)