You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In August 2021, Azure announced that the retirement of Cloud Services (classic) would happen on August 31, 2024. As Azure App Service Environment v1 and v2 run on Cloud Services (classic), we announced that they would retire on the same date. Now that we have passed that date, 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.
As of 29 January 2024, App Service Environment v1 and v2 no longer supports the creation of new workloads using any of the available methods including APM/Bicep templates, Azure portal, Azure CLI, or REST API.
As of August 31, 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 since they are retired products.
Customers 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, but Microsoft makes no claim or guarantees about application availability after auto-migration. 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. 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, go to Azure portal and visit the Migration blade for your App Service Environment(s).
Please visit the product documentation for the latest information and resources, including free migration tooling, to help you complete the migration.
Required action
To avoid service disruption, please follow the stepsto complete your migration to App Service Environment v3 as soon as possible.
Help and support
Please visit the product documentation for the latest resources. Review the free on-demand webinar with Azure FastTrack Architects. If you have questions, get answers from community experts in Microsoft Q&A.
If you have a support plan and you encounter any problem during your migration, please create a support request.
Under Issue type, select Technical.
Under Subscription, select your subscription.
Under Service, select My services, then select ASE.
Under Resource, select the ASE you are migrating.
Under Summary, type a description of your issue.
Under Problem type, select Migration.
Learn more about service retirements that may impact your resources in the Azure Retirement Workbook. Please note that retirements may not be visible in the workbook for up to two weeks after being announced.
The text was updated successfully, but these errors were encountered:
In August 2021, Azure announced that the retirement of Cloud Services (classic) would happen on August 31, 2024. As Azure App Service Environment v1 and v2 run on Cloud Services (classic), we announced that they would retire on the same date. Now that we have passed that date, 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.
As of 29 January 2024, App Service Environment v1 and v2 no longer supports the creation of new workloads using any of the available methods including APM/Bicep templates, Azure portal, Azure CLI, or REST API.
As of August 31, 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 since they are retired products.
Customers 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, but Microsoft makes no claim or guarantees about application availability after auto-migration. 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. 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, go to Azure portal and visit the Migration blade for your App Service Environment(s).
Please visit the product documentation for the latest information and resources, including free migration tooling, to help you complete the migration.
Required action
To avoid service disruption, please follow the steps to complete your migration to App Service Environment v3 as soon as possible.
Help and support
Please visit the product documentation for the latest resources. Review the free on-demand webinar with Azure FastTrack Architects. If you have questions, get answers from community experts in Microsoft Q&A.
If you have a support plan and you encounter any problem during your migration, please create a support request.
Learn more about service retirements that may impact your resources in the Azure Retirement Workbook. Please note that retirements may not be visible in the workbook for up to two weeks after being announced.
The text was updated successfully, but these errors were encountered: