|
| 1 | +--- |
| 2 | +title: Azure Spring Apps retirement announcement |
| 3 | +description: Announces the retirement of the Azure Spring Apps service. |
| 4 | +author: KarlErickson |
| 5 | +ms.author: taoxu |
| 6 | +ms.service: azure-spring-apps |
| 7 | +ms.topic: overview |
| 8 | +ms.date: 09/30/2024 |
| 9 | +ms.custom: devx-track-java, engagement-fy23, references_regions |
| 10 | +--- |
| 11 | + |
| 12 | +# Azure Spring Apps retirement announcement |
| 13 | + |
| 14 | +Azure Spring Apps is a fully managed service for running Java Spring applications, jointly built by Microsoft and VMware by Broadcom. After careful consideration and analysis, Microsoft and Broadcom have made the difficult decision to retire the Azure Spring Apps service. We recommend Azure Container Apps as the primary service for your migration of workloads running on Azure Spring Apps. Azure Container Apps is a strong and enterprise ready platform that provides fully managed, serverless container service for polyglot apps and enhanced Java features to help you manage, monitor, and troubleshoot Java apps at scale. |
| 15 | + |
| 16 | +We're committed to supporting you with a long-term platform with migration tools, expert resources, and technical support through the end of the service. |
| 17 | + |
| 18 | +## Timeline |
| 19 | + |
| 20 | +Azure Spring Apps, including the Standard consumption and dedicated, Basic, Standard, and Enterprise plans, will be retired through a two-phased retirement plan: |
| 21 | + |
| 22 | +- On September 30, 2024, the Standard consumption and dedicated plan (preview) will enter a six-month retirement period and will be retired on March 31, 2025. |
| 23 | +- In mid-March 2025, all other Azure Spring Apps plans, including Basic, Standard, and Enterprise plans, will enter a three-year retirement period and will be retired on March 31, 2028. |
| 24 | + |
| 25 | +:::image type="content" source="media/retirement-announcement/retirement-period.png" alt-text="Diagram showing the Azure Spring Apps retirement period."::: |
| 26 | + |
| 27 | +## Migration recommendation |
| 28 | + |
| 29 | +To ensure that you maintain high performance and achieve scalability, flexibility, and cost-efficiency for your business, we recommend Azure Container Apps as the primary service for your migration of workloads running on Azure Spring Apps. |
| 30 | + |
| 31 | +Azure Container Apps is a fully managed, serverless container service for polyglot apps and offers enhanced Java features to help you manage, monitor, and troubleshoot Java apps at scale. |
| 32 | + |
| 33 | +Key Features of Azure Container Apps: |
| 34 | + |
| 35 | +- Fully managed, serverless container platform |
| 36 | +- Scale to zero capability |
| 37 | +- Open-source foundation and add-ons |
| 38 | +- [Enhanced Java support](../../container-apps/java-overview.md) |
| 39 | + - Managed Spring components support (Eureka Server, Config Server, Spring Boot Admin) |
| 40 | + - Built-in JVM metrics |
| 41 | + - Diagnostics for Java apps |
| 42 | + |
| 43 | +For more information about Azure Container Apps, see [Azure Container Apps overview](../../container-apps/overview.md). |
| 44 | + |
| 45 | +## Migration support for the Azure Spring Apps Standard consumption and dedicated plan |
| 46 | + |
| 47 | +For the Azure Spring Apps Standard consumption and dedicated plan, new customers will no longer be able to sign up for the service after September 30, 2024, while existing customers will remain operational until this plan is retired on March 31, 2025. |
| 48 | + |
| 49 | +A one-click migration experience will be enabled for the Azure Spring Apps Standard consumption and dedicated plan by mid-October, providing customers with a seamless transition from Azure Spring Apps to Azure Container Apps. For more information, see [the FAQ](https://aka.ms/DeprecatedASAConsunptionPlanFAQ). |
| 50 | + |
| 51 | +## Migration support for the Azure Spring Apps Basic, Standard, and Enterprise plans |
| 52 | + |
| 53 | +For the Azure Spring Apps Basic, Standard, and Enterprise plans, new customers will no longer be able to sign up for the service after March 31, 2025, while existing customers will remain operational until the plans are phased out on March 31, 2028. |
| 54 | + |
| 55 | +We encourage you to start testing out Azure Container Apps for your Java Spring workloads and get prepared for the migration when the retirement for the Basic, Standard, and Enterprise plans starts in mid-March 2025. |
| 56 | + |
| 57 | +Step-by-step migration guidance will be ready by the end of December 2024 and the migration tool will be available by mid-March 2025 before the retirement starts. |
| 58 | + |
| 59 | +## What is the impact for customers using Tanzu Components with Azure Spring Apps Enterprise? |
| 60 | + |
| 61 | +If customers are interested in obtaining or continuing Spring commercial support and using Tanzu Components while migrating to Azure Container Apps, the components can download and run as JAR files on top of Azure Container Apps. For more information, please work with Broadcom sellers. |
| 62 | + |
| 63 | +## FAQ |
| 64 | + |
| 65 | +### What are the migration destinations? |
| 66 | + |
| 67 | +We recommend Azure Container Apps as the primary service for your migration of workloads running on Azure Spring Apps. Azure Container Apps is a fully managed serverless container service for polyglot apps and offers enhanced Java features to help you manage, monitor, and troubleshoot Java apps at scale. |
| 68 | + |
| 69 | +A one-click migration experience will be enabled for Azure Spring Apps Standard consumption and dedicated plan by mid-October, providing customers with a seamless transition from Azure Spring Apps to Azure Container Apps. For more information, see [the FAQ](https://aka.ms/DeprecatedASAConsunptionPlanFAQ). |
| 70 | + |
| 71 | +We're working on the migration experience from the Azure Spring Apps Basic, Standard, and Enterprise plans to Azure Container Apps, and the migration guidance will be available by March 2025. |
| 72 | + |
| 73 | +You might also consider the following alternative solutions: |
| 74 | + |
| 75 | +- PaaS solution: Azure App Service is a fully managed platform for building, deploying, and scaling web apps, mobile app backends, and RESTful APIs. It supports multiple programming languages (such as Java and .NET), integrates with various development tools, and provides features like autoscaling, load balancing, and security for applications. Learn more: [App Service Overview](../../app-service/overview.md). |
| 76 | +- Containerized solution: Azure Kubernetes Service (AKS) is a managed container orchestration service that simplifies the deployment, management, and scaling of containerized applications using Kubernetes. It offers features like automated updates, monitoring, and scaling, enabling developers to focus on application development rather than infrastructure management. Learn more: [What is Azure Kubernetes Service (AKS)?](/azure/aks/what-is-aks). |
| 77 | +- If you're currently using Spring commercial support or Tanzu components as part of Azure Spring Apps Enterprise, you need to switch to using Tanzu Platform Spring Essentials on Azure Container Apps. Learn more: [VMware Tanzu Spring](https://tanzu.vmware.com/spring). |
| 78 | + |
| 79 | +### What is the migration timeline? |
| 80 | + |
| 81 | +Existing customers are required to migrate their Azure Spring Apps Standard consumption and dedicated workloads to Azure Container Apps by March 31, 2025. Customers on Basic, Standard, and Enterprise plans are required to complete this transition by March 31, 2028. Azure Spring Apps will be entirely retired by March 31, 2028. |
| 82 | + |
| 83 | +### Will Azure Spring Apps still allow new customer sign-ups? |
| 84 | + |
| 85 | +For Azure Spring Apps Standard consumption and dedicated plan, new customers will no longer be able to sign up for the service after September 30, 2024, while existing customers will remain operational until these plans are retired on March 31, 2025. |
| 86 | + |
| 87 | +For Azure Spring Apps Basic, Standard, and Enterprise plans, new customers will no longer be able to sign up for the service after March 31, 2025, while existing customers will remain operational until the plans are phased out on March 31, 2028. |
| 88 | + |
| 89 | +### Will Microsoft continue to support my current workload? |
| 90 | + |
| 91 | +Yes, support will continue for your workloads on Azure Spring Apps until the retirement date. You'll continue to receive SLA assurance, infrastructure updates/maintenance (VM and AKS), management of OSS/Tanzu components, and updates for container images of your apps including base OS, runtime (JDK, dotnet runtime, and so on), and APM agents. You can still raise support tickets as usual for prompt assistance through the end of the service. |
| 92 | + |
| 93 | +### Will Azure Spring Apps provide any new features during the retirement period? |
| 94 | + |
| 95 | +No, we won't take up any feature requests from customers and won't be building any features in the Azure Spring Apps service. Instead, we'll prioritize new features and enhancements on Azure Container Apps. |
| 96 | + |
| 97 | +### What will happen after retirement date? |
| 98 | + |
| 99 | +After March 31, 2025, the Azure Spring Apps Standard consumption and dedicated plan will be completely discontinued. As a result, you will no longer receive support and access to your workloads and Azure Spring Apps services. |
| 100 | + |
| 101 | +After March 31, 2028, Azure Spring Apps Basic, Standard and Enterprise plans will be completely discontinued. As a result, you will no longer receive support and access to your workloads and Azure Spring Apps services. We strongly suggest you migrate your workloads to Azure Container Apps by March 31, 2028. |
| 102 | + |
| 103 | +### Does Microsoft Container Apps offer feature parity with Azure Spring Apps? |
| 104 | + |
| 105 | +Most Java features work the same on Azure Container Apps, with some experiential differences. Features such as autopatching and Terraform support aren't available on Azure Container Apps yet, and we're working on enabling the features by the end of December. |
| 106 | + |
| 107 | +If you have interest in obtaining or continuing Spring commercial support and using Tanzu components, you can download the components and run them as JAR files on top of Azure Container Apps. Please work with your Broadcom sales to explore running Tanzu Platform Spring Essentials on top of Azure Container Apps. |
| 108 | + |
| 109 | +### Will Microsoft Azure Container Apps be available in the same Azure regions as Azure Spring Apps? |
| 110 | + |
| 111 | +For the Standard consumption and dedicated plan, Azure Container Apps and Azure Spring Apps are available in the same regions. |
| 112 | + |
| 113 | +Azure Container Apps will be available in the same Azure regions as Azure Spring Apps for customers under the Basic, Standard, and Enterprise plans before the migration starts in March 2025. |
| 114 | + |
| 115 | +### Are there pricing differences across Microsoft solutions? |
| 116 | + |
| 117 | +Azure Spring Apps operates on a consumption-based model with a basic unit where you only pay for vCPU and memory for your apps. |
| 118 | + |
| 119 | +[Azure Container Apps](https://azure.microsoft.com/pricing/details/container-apps/) offers the following two pricing models: |
| 120 | + |
| 121 | +- A consumption model billed based on per-second resource allocation (on VCPU and memory) and requests. |
| 122 | +- A dedicated model with a single tenancy guarantee, access to specialized hardware, and more predictable pricing. |
| 123 | + |
| 124 | +Billing for the dedicated plan is based on the number of vCPU seconds and gibibyte (GiB) seconds allocated across Azure Container App instances. Azure Container Apps also provides savings plan. |
| 125 | + |
| 126 | +The costs for Microsoft solutions will vary based on their pricing model and optimizations that can be enabled. We recommend using the [Azure Pricing Calculator](https://azure.microsoft.com/pricing/calculator/?ef_id=_k_8d2e1450f88b14d2046272e613f0ee0b_k_&OCID=AIDcmm5edswduu_SEM__k_8d2e1450f88b14d2046272e613f0ee0b_k_&msclkid=8d2e1450f88b14d2046272e613f0ee0b), which provides details on meters, usage prices, and available savings plans to accurately assess anticipated costs. |
| 127 | + |
| 128 | +### What is the impact for customers using Tanzu Components within Azure Spring Apps Enterprise? |
| 129 | + |
| 130 | +If you're interested in obtaining or continuing Spring commercial support and using Tanzu Components while migrating to Azure Container Apps, you can download the components and run them as JAR files on top of Azure Container Apps. For more information, please work with your Broadcom sales contact. |
| 131 | + |
| 132 | +### How can I stay up to date with Azure Spring Apps retirement guidance? |
| 133 | + |
| 134 | +The following table indicates the overall release timeline for whole Azure Spring Apps retirement period. We'll keep it updated when the corresponding doc/tool is ready for release. |
| 135 | + |
| 136 | +| Item | Target plans | Release date | |
| 137 | +|---------------------------------------------------------------------------------|-----------------------------------------|--------------------| |
| 138 | +| Official retirement start date | Standard consumption and dedicated plan | September 30, 2024 | |
| 139 | +| Block new service instance creation for all customers | Standard consumption and dedicated plan | September 30, 2024 | |
| 140 | +| One-click migration experience to Azure Container Apps | Standard consumption and dedicated plan | October 2024 | |
| 141 | +| Guidance for helping switch from Tanzu components to alternative solutions | Enterprise plan | October 2024 | |
| 142 | +| Guidance for migrating to Azure Container Apps (without migration tool support) | Basic, Standard, and Enterprise plans | December 2024 | |
| 143 | +| Official retirement date after a half year retirement period | Standard consumption and dedicated plan | March 31, 2025 | |
| 144 | +| Official retirement start date | Basic, Standard, and Enterprise plans | Mid-March 2025 | |
| 145 | +| Guidance for migrating to Azure Container Apps with migration tool support | Basic, Standard, and Enterprise plans | Mid-March 2025 | |
| 146 | +| Block new customer sign-ups | Basic, Standard, and Enterprise plans | April 2025 | |
| 147 | +| Official retirement date after a three-year retirement period | Basic, Standard, and Enterprise plans | March 31 2028 | |
| 148 | + |
| 149 | +### How can I get transition help and support during migration? |
| 150 | + |
| 151 | +If you have any questions, you can open a support ticket through the Azure portal for technical help: create an [Azure Support Request](/azure/azure-portal/supportability/how-to-create-azure-support-request). |
0 commit comments