Skip to content

Commit eb2d8f0

Browse files
Merge pull request #280621 from seligj95/patch-3
step 5 clarification
2 parents 5c7cde5 + 550de96 commit eb2d8f0

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/app-service/environment/side-by-side-migrate.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how to migrate your App Service Environment v2 to App Service
44
author: seligj95
55
ms.topic: tutorial
66
ms.custom: devx-track-azurecli, references_regions
7-
ms.date: 6/28/2024
7+
ms.date: 7/11/2024
88
ms.author: jordanselig
99
---
1010
# Migration to App Service Environment v3 using the side-by-side migration feature
@@ -296,7 +296,7 @@ az rest --method get --uri "${ASE_ID}/configurations/networking?api-version=2022
296296

297297
### 5. Update dependent resources with new outbound IPs
298298

299-
By using the new outbound IPs, update any of your resources or networking components to ensure that your new environment functions as intended after migration is started. It's your responsibility to make any necessary updates. The new outbound IPs are used once the App Service Environment v3 is created during the migration step.
299+
By using the new outbound IPs, update any of your resources or networking components to ensure that your new environment functions as intended after migration is started. It's your responsibility to make any necessary updates. The new outbound IPs are used once the App Service Environment v3 is created during the migration step. For example, if you have a custom domain suffix and an Azure Key Vault and are managing access restrictions with a firewall, you need to update the Azure Key Vault's firewall to allow either just the new outbound IPs or the entire new subnet.
300300

301301
### 6. Delegate your App Service Environment subnet
302302

0 commit comments

Comments
 (0)