Skip to content

Commit 0bbff75

Browse files
authored
Fix broken link in migration note
1 parent f8a2010 commit 0bbff75

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -99,7 +99,7 @@ For more information about the migration process, see [Understand storage accoun
9999
> Accounts left in a **Prepare** migration state more 30 days may have their migrations committed on your behalf. If you need more than 30 days to validate your migration to Azure Resource Manager, you can abort the current migration and restart it when you are ready.
100100
101101
> [!NOTE]
102-
> After migrating your classic resources to Azure Resource Manager within your subscription, ensure that all Classic Admin role assignments are converted to the Owner role in Azure RBAC. Without an assigned Owner, your subscription may become orphaned. For detailed guidance, refer to [Azure classic subscription administrators](../..//role-based-access-control/classic-administrators.md).
102+
> After migrating your classic resources to Azure Resource Manager within your subscription, ensure that all Classic Admin role assignments are converted to the Owner role in Azure RBAC. Without an assigned Owner, your subscription may become orphaned. For detailed guidance, refer to [Azure classic subscription administrators](../../../role-based-access-control/classic-administrators.md).
103103
104104
You can migrate a classic storage account to the Azure Resource Manager deployment model with the Azure portal or PowerShell.
105105

0 commit comments

Comments
 (0)