Skip to content

Commit 41eafc3

Browse files
authored
Update migrate-v1-v2.md
1 parent 343bbd8 commit 41eafc3

File tree

1 file changed

+6
-7
lines changed

1 file changed

+6
-7
lines changed

articles/application-gateway/migrate-v1-v2.md

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -36,6 +36,9 @@ This article primarily helps with the configuration migration. The traffic migra
3636

3737
[!INCLUDE [updated-for-az](../../includes/updated-for-az.md)]
3838

39+
> [!IMPORTANT]
40+
>Use a new PowerShell session each time to run the migration script. This applies when the migration fails or if you are using the script to migrate another V1 gateway. This is required because the initialized variables clean up the existing resource group before executing the migration script again.
41+
3942
## Configuration migration
4043

4144
An Azure PowerShell script is provided in this document. It performs the following operations to help you with the configuration:
@@ -47,15 +50,11 @@ An Azure PowerShell script is provided in this document. It performs the followi
4750

4851
You can download the migration script from the [PowerShell Gallery](https://www.powershellgallery.com/packages/AzureAppGWMigration).
4952

50-
> [!IMPORTANT]
51-
>**Known Issue:** Running the migration script multiple times in the same powershell session/window can delete all resources in the resource group.
52-
>
53-
>**Mitigation:** To avoid this issue, please run the migration script in a new PowerShell window or session each time. You can ensure that a new session is created before running the migration script again by running "Exit-PSSession" each time after the script has finished.
54-
>
55-
>**Resolution:** We apologize for the inconvenience and understand that this is not the ideal experience. We are working on fixing this issue and we expect to have a solution by August 10, 2023. After this date, customers will be able to run the migration script in the same session.
56-
5753
## Using the script
5854

55+
> [!NOTE]
56+
>Use a new PowerShell session each time to run the migration script. This applies when the migration fails or if you are using the script to migrate another V1 gateway. This is required because the initialized variables clean up the existing resource group before executing the migration script again.
57+
5958
There are two options for you depending on your local PowerShell environment setup and preferences:
6059

6160
* If you don't have the Azure Az modules installed, or don't mind uninstalling the Azure Az modules, the best option is to use the `Install-Script` option to run the script.

0 commit comments

Comments
 (0)