Skip to content

Commit f28b7be

Browse files
authored
Update side-by-side-migrate.md
1 parent e72e0b9 commit f28b7be

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

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

Lines changed: 5 additions & 1 deletion
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: 7/24/2024
7+
ms.date: 7/25/2024
88
ms.author: jordanselig
99
---
1010
# Migration to App Service Environment v3 using the side-by-side migration feature
@@ -450,6 +450,10 @@ For ELB App Service Environments, get the public inbound IP address by running t
450450
az rest --method get --uri "${ASE_ID}?api-version=2022-03-01" --query properties.networkingConfiguration.externalInboundIpAddresses
451451
```
452452

453+
> [!IMPORTANT]
454+
> If your migration includes a custom domain suffix, the default host name behavior for App Service Environment v3 is different than for App Service Environment v2. For App Service Environment v3, the default host name always uses the default domain suffix and is in the form *APP-NAME.ASE-NAME.appserviceenvironment.net*. Review all your dependent resources, such as App Gateway, that use the host names of your apps to ensure they're updated to account for this behavior. For more information on App Service Environment feature differences between the different versions, see [App Service Environment version comparison](version-comparison.md).
455+
>
456+
453457
### 11. Redirect customer traffic, validate your App Service Environment v3, and complete migration
454458

455459
This step is your opportunity to test and validate your new App Service Environment v3.

0 commit comments

Comments
 (0)