Skip to content

Commit b5e8acc

Browse files
authored
Update classic-account-migration-process.md
1 parent 933b981 commit b5e8acc

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

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

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -58,6 +58,9 @@ There are four steps to the migration process, as shown in the following diagram
5858
> [!NOTE]
5959
> The operations described in the following sections are all idempotent. If you have a problem other than an unsupported feature or a configuration error, retry the prepare, abort, or commit operation.
6060
61+
> [!NOTE]
62+
> 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.
63+
6164
### Validate
6265

6366
The Validation step is the first step in the migration process. The goal of this step is to analyze the state of the resources that you want to migrate from the classic deployment model. The Validation step evaluates whether the resources are capable of migration (success or failure). If the classic storage account isn't capable of migration, Azure lists the reasons why.

0 commit comments

Comments
 (0)