Upgrade to App Service Environment v3
Important
If you're currently using App Service Environment v1 or v2, you must migrate your workloads to App Service Environment v3. App Service Environment v1 and v2 are retired as of 31 August 2024. There's a new version of App Service Environment that is easier to use and runs on more powerful infrastructure. To learn more about the new version, start with the Introduction to the App Service Environment. If you're currently using App Service Environment v1, please follow the steps in this article to migrate to the new version.
As of 31 August 2024, Service Level Agreement (SLA) and Service Credits no longer apply for App Service Environment v1 and v2 workloads that continue to be in production since they are retired products. Decommissioning of the App Service Environment v1 and v2 hardware has begun, and this may affect the availability and performance of your apps and data.
You must complete migration to App Service Environment v3 immediately or your apps and resources may be deleted. We will attempt to auto-migrate any remaining App Service Environment v1 and v2 on a best-effort basis using the in-place migration feature, but Microsoft makes no claim or guarantees about application availability after auto-migration. You may need to perform manual configuration to complete the migration and to optimize your App Service plan SKU choice to meet your needs. If auto-migration isn't feasible, your resources and associated app data will be deleted. We strongly urge you to act now to avoid either of these extreme scenarios.
If you need additional time, we can offer a one-time 30-day grace period for you to complete your migration. For more information and to request this grace period, review the grace period overview, and then go to Azure portal and visit the Migration blade for each of your App Service Environments.
For the most up-to-date information on the App Service Environment v1/v2 retirement, see the App Service Environment v1 and v2 retirement update.
This page is your one-stop shop for guidance and resources to help you upgrade successfully with minimal downtime. Follow the guidance to plan and complete your upgrade as soon as possible. This page is updated with the latest information as it becomes available.
Upgrade steps
| Step | Action | Resources |
|---|---|---|
| 1 | Receive a 30-day grace period | If you haven't requested a 30-day grace period, review the grace period overview, and then request a grace period by going to Azure portal and visiting the Migration blade for each of your App Service Environments. You must receive a grace period to prevent unexpected auto-migration or deletion. |
| 2 | Pre-flight check | Determine if your environment meets the prerequisites to automate your upgrade using one of the automated migration features. Decide whether an in-place or side-by-side migration is right for your use case. - Migration path decision tree - Automated upgrade using the in-place migration feature - Automated upgrade using the side-by-side migration feature If not, you can upgrade manually. - Manual migration |
| 3 | Migrate | Based on results of your review, either upgrade using one of the automated migration features or follow the manual steps. |
| 4 | Testing and troubleshooting | Upgrading using one of the automated migration features requires a 3-6 hour service window. If you use the side-by-side migration feature, you have the opportunity to test and validate your App Service Environment v3 before completing the upgrade. Support teams are monitoring upgrades to ensure success. If you have a support plan and you need technical help, create a support request. |
| 5 | Optimize your App Service plans | Once your upgrade is complete, you can optimize the App Service plans for additional benefits. Review the autoselected Isolated v2 SKU sizes and scale up or scale down your App Service plans as needed. - Scale down your App Service plans - App Service Environment post-migration scaling guidance Explore reserved instance pricing, savings plans, and check out the pricing estimates if needed. - App Service pricing page - How reservation discounts apply to Isolated v2 instances - Azure pricing calculator |
| 6 | Learn more | Overview of the upgrade process with App Service Environment Product Managers: - Azure App Service Community Standup: App Service Environment Migration On-demand Learn Live sessions with Azure FastTrack Architects: - Use the in-place automated migration feature - Use the side-by-side automated migration feature Need more help? Submit a request to contact FastTrack. Frequently asked questions Community support |
Additional information
What are the benefits of upgrading?
App Service Environment v3 is the latest version of App Service Environment. It's easier to use, runs on more powerful infrastructure that can go up to 64 cores and 256-GB RAM with faster scaling speeds for both Windows and Linux, and has simpler network topology. For more information about these and other benefits, see the following resources.
- Three reasons why you should prioritize migrating to App Service Environment v3 for your business
- Estimate your cost savings by migrating to App Service Environment v3
- Using App Service Environment v3 in Compliance-Oriented Industries
What changes when upgrading to App Service Environment v3?
What tooling is available to help with the upgrade to App Service Environment v3?
There are two automated migration features available to help you upgrade to App Service Environment v3.
- In-place migration feature migrates your App Service Environment to App Service Environment v3 in-place and is the recommended migration option. In-place means that your App Service Environment v3 replaces your existing App Service Environment in the same subnet. There's application downtime during the migration because a subnet can only have a single App Service Environment at a given time. For more information about this feature, see Automated upgrade using the in-place migration feature.
- Side-by-side migration feature creates a new App Service Environment v3 in a different subnet that you choose and recreates all of your App Service plans and apps in that new environment. Your existing environment is up and running during the entire migration. Once the new App Service Environment v3 is ready, you can redirect traffic to the new environment and complete the migration. There's no application downtime during the migration. For more information about this feature, see Automated upgrade using the side-by-side migration feature.
Note
Side-by-side migration comes with additional challenges compared to in-place migration. For customers who need to decide between the two options, the recommendation is to use in-place migration since there are fewer steps and less complexity. If you decide to use side-by-side migration, review the common sources of issues when migrating using the side-by-side migration feature section to avoid common pitfalls.
- Manual migration options are available if you can't use the automated migration features. For more information about these options, see Migration alternatives.
Why do some customers see performance differences after migrating?
App Service Environment v3 uses newer virtual machines that are based on virtual CPUs (vCPU), not physical cores. One vCPU typically doesn't equate to one physical core in terms of raw CPU performance. As a result, CPU-bound workloads might see a performance difference if attempting to match old-school physical core counts to current vCPU counts.
When migrating to App Service Environment v3, we map App Service plan tiers as follows:
| App Service Environment v2 SKU | App Service Environment v3 SKU |
|---|---|
| I1 | I1v2 |
| I2 | I2v2 |
| I3 | I3v2 |
Migration path decision tree
Use the following decision tree to determine which migration path is right for you. The recommendation for all customers is to use the in-place migration feature if your App Service Environment meets the criteria for an automated migration. In-place migration is the simplest and fastest way to upgrade to App Service Environment v3.
Post-retirement date activities
After 31 August 2024, decommissioning of the App Service Environment v1 and v2 hardware will begin, and this may affect the availability and performance of your apps and data. Additionally, since these products will be retired, after the official retirement on 31 August 2024, Service Level Agreement (SLA) and Service Credits will no longer apply for App Service Environment v1 and v2 workloads that continue to be in production.
You must complete migration to App Service Environment v3 as soon as possible or your apps and resources may be deleted. We will attempt to auto-migrate any remaining App Service Environment v1 and v2 on a best-effort basis using the in-place migration feature, but Microsoft makes no claim or guarantees about application availability after auto-migration. You may need to perform manual configuration to complete the migration and to optimize your App Service plan SKU choice to meet your needs. If auto-migration is not feasible, your resources and associated app data will be deleted. We strongly urge you to act now to avoid either of these extreme scenarios.
Cost saving opportunities after upgrading to App Service Environment v3
The App Service plan SKUs available for App Service Environment v3 run on the Isolated v2 (Iv2) tier. The number of cores and amount of RAM are effectively doubled per corresponding tier compared the Isolated tier. When you migrate, your App Service plans are converted to the corresponding tier. For example, your I2 instances are converted to I2v2. While I2 has two cores and 7-GB RAM, I2v2 has four cores and 16-GB RAM. If you expect your capacity requirements to stay the same, you're over-provisioned and paying for compute and memory you're not using. For this scenario, you can scale down your I2v2 instance to I1v2 and end up with a similar number of cores and RAM that you had previously.
Note
All scenarios are calculated using costs based on Linux $USD pricing in East US. The payment option is set to monthly. Estimates are based on the prices applicable on the day the estimate was created. Actual total estimates may vary. For the most up-to-date estimates, see the Azure pricing calculator.
To demonstrate the cost saving opportunity for this scenario, use the pricing calculator to estimate the monthly savings as a result of scaling down your App Service plans. For this example, your App Service Environment v2 has 1 I2 instance. You require two cores and 7-GB RAM. You're using pay-as-you-go pricing. On App Service Environment v2, your monthly payment is the following.
Stamp fee + 1(I2) = $991.34 + $416.10 = $1,407.44
When you migrate this App Service Environment using the migration feature, your new App Service Environment v3 has 1 I2v2 instance, which means you have four cores and 16-GB RAM. If you don't change anything, your monthly payment is the following.
Your monthly cost is reduced, but you don't need that much compute and capacity. You scale down your instance to I1v2 and your monthly cost is reduced even further.
Break even point
In most cases, migrating to App Service Environment v3 allows for cost saving opportunities. However, cost savings might not always be possible, especially if you're required to maintain a large number of small instances.
To demonstrate this scenario, you have an App Service Environment v2 with a single I1 instance. Your monthly cost is:
Stamp fee + 1(I1) = $991.34 + $208.05 = $1,199.39
If you migrate this environment to App Service Environment v3, your monthly cost is:
This change is a significant cost reduction, but you're over-provisioned since you have double the cores and RAM, which you might not need. This excess isn't an issue for this scenario since the new environment is cheaper. However, when you increase your I1 instances in a single App Service Environment, you see how migrating to App Service Environment v3 can increase your monthly cost.
For this scenario, your App Service Environment v2 has 14 I1 instances. Your monthly cost is:
Stamp fee + 14(I1) = $991.34 + $2,912.70 = $3,904.04
When you migrate this environment to App Service Environment v3, your monthly cost is:
Your App Service Environment v3 is now more expensive than your App Service Environment v2. As you start add more I1 instances, and therefore need more I1v2 instances when you migrate, the difference in price becomes more significant. If this scenario is a requirement for your environment, you might need to plan for an increase in your monthly cost. The following graph visually depicts the point where App Service Environment v3 becomes more expensive than App Service Environment v2 for this specific scenario.
Note
This calculation was done with Linux $USD prices in East US. Break even points will vary due to price variances in the different regions. For an estimate that reflects your situation, see the Azure pricing calculator.
For more scenarios on cost changes and savings opportunities with App Service Environment v3, see Estimate your cost savings by migrating to App Service Environment v3.
We want your feedback
Got 2 minutes? We'd love to hear about your upgrade experience in this quick, anonymous poll. You'll help us learn and improve.