Skip to content

Commit 0cbbb70

Browse files
committed
init
1 parent e9500d4 commit 0cbbb70

File tree

2 files changed

+9
-3
lines changed

2 files changed

+9
-3
lines changed

articles/app-service/environment/migrate.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Migrate to App Service Environment v3 by using the migration feature
33
description: Overview of the migration feature for migration to App Service Environment v3
44
author: seligj95
55
ms.topic: article
6-
ms.date: 06/08/2023
6+
ms.date: 06/19/2023
77
ms.author: jordanselig
88
ms.custom: references_regions
99
---
@@ -69,6 +69,10 @@ The migration feature doesn't support the following scenarios. See the [manual m
6969

7070
The App Service platform reviews your App Service Environment to confirm migration support. If your scenario doesn't pass all validation checks, you can't migrate at this time using the migration feature. If your environment is in an unhealthy or suspended state, you can't migrate until you make the needed updates.
7171

72+
> [!NOTE]
73+
> App Service Environment v3 doesn't support IP SSL. If you use IP SSL, you must remove all IP SSL bindings before migrating to App Service Environment v3. The migration feature will support your environment once all IP SSL bindings are removed.
74+
>
75+
7276
### Troubleshooting
7377

7478
If your App Service Environment doesn't pass the validation checks or you try to perform a migration step in the incorrect order, you may see one of the following error messages:
@@ -210,6 +214,8 @@ For more scenarios on cost changes and savings opportunities with App Service En
210214
The migration feature supports this [migration scenario](#supported-scenarios). You can migrate using a manual method if you don't want to use the migration feature. You can configure your [custom domain suffix](./how-to-custom-domain-suffix.md) when creating your App Service Environment v3 or any time after.
211215
- **What if my App Service Environment is zone pinned?**
212216
Zone pinned App Service Environment is currently not a supported scenario for migration using the migration feature. App Service Environment v3 doesn't support zone pinning. To migrate to App Service Environment v3, see the [manual migration options](migration-alternatives.md).
217+
- **What if my App Service Environment has IP SSL addresses?**
218+
IP SSL isn't supported on App Service Environment v3. You must remove all IP SSL bindings before migrating using the migration feature or one of the manual options. If you intend to use the migration feature, once you remove all IP SSL bindings, you will pass that validation check and can proceed with the automated migration.
213219
- **What properties of my App Service Environment will change?**
214220
You're on App Service Environment v3 so be sure to review the [features and feature differences](overview.md#feature-differences) compared to previous versions. For ILB App Service Environment, you keep the same ILB IP address. For internet facing App Service Environment, the public IP address and the outbound IP address change. Note for ELB App Service Environment, previously there was a single IP for both inbound and outbound. For App Service Environment v3, they're separate. For more information, see [App Service Environment v3 networking](networking.md#addresses). For a full comparison of the App Service Environment versions, see [App Service Environment version comparison](version-comparison.md).
215221
- **What happens if migration fails or there is an unexpected issue during the migration?**

articles/app-service/environment/migration-alternatives.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Migrate to App Service Environment v3
33
description: How to migrate your applications to App Service Environment v3
44
author: seligj95
55
ms.topic: article
6-
ms.date: 10/20/2022
6+
ms.date: 06/19/2023
77
ms.author: jordanselig
88
---
99
# Migrate to App Service Environment v3
@@ -154,7 +154,7 @@ Once your migration and any testing with your new environment is complete, delet
154154
- **Will I experience downtime during the migration?**
155155
Downtime is dependent on your migration process. If you have a different App Service Environment that you can point traffic to while you migrate or if you can use a different subnet to create your new environment, you won't have downtime. However, if you must use the same subnet, there will be downtime resulting from the time it takes to delete the old environment, create the App Service Environment v3, create the new App Service plans, re-create the apps, and update any resources that need to know about the new IP addresses.
156156
- **Do I need to change anything about my apps to get them to run on App Service Environment v3?**
157-
No, apps that run on App Service Environment v1 and v2 shouldn't need any modifications to run on App Service Environment v3.
157+
No, apps that run on App Service Environment v1 and v2 shouldn't need any modifications to run on App Service Environment v3. If you are using IP SSL, that will need to be removed before migrating.
158158
- **What if my App Service Environment has a custom domain suffix?**
159159
The migration feature supports this [migration scenario](./migrate.md#supported-scenarios). You can migrate using a manual method if you don't want to use the migration feature. You can configure your [custom domain suffix](./how-to-custom-domain-suffix.md) when creating your App Service Environment v3 or any time after that.
160160
- **What if my App Service Environment is zone pinned?**

0 commit comments

Comments
 (0)