Build and deploy Spring Boot applications with a fully managed service from Microsoft and VMware
Azure Spring Apps makes it quick, safe, and easy to deploy and operate Spring Boot applications in the cloud.
Explore pricing options
Apply filters to customize pricing options to your needs.
Prices are estimates only and are not intended as actual price quotes. Actual pricing may vary depending on the type of agreement entered with Microsoft, date of purchase, and the currency exchange rate. Prices are calculated based on US dollars and converted using Thomson Reuters benchmark rates refreshed on the first day of each calendar month. Sign in to the Azure pricing calculator to see pricing based on your current program/offer with Microsoft. Contact an Azure sales specialist for more information on pricing or to request a price quote. For more information on Azure pricing see frequently asked questions.
US government entities are eligible to purchase Azure Government services from a licensing solution provider with no upfront financial commitment, or directly through a pay-as-you-go online subscription.
Important—The price in R$ is merely a reference; this is an international transaction and the final price is subject to exchange rates and the inclusion of IOF taxes. An eNF will not be issued.
US government entities are eligible to purchase Azure Government services from a licensing solution provider with no upfront financial commitment, or directly through a pay-as-you-go online subscription.
Important—The price in R$ is merely a reference; this is an international transaction and the final price is subject to exchange rates and the inclusion of IOF taxes. An eNF will not be issued.
Standard consumption plan
For each app instance in the Standard consumption plan, Azure Spring Apps charges for requests and resource allocation measured in vCPU and GBibyte (GB). Applications scale on-demand based on requests and events. App instances are billed for active usage when they are running. An application can be configured to scale to zero instance when there are no requests or events to process. No usage charges apply when an application is scaled to zero.
You can optionally configure Apps in the Standard consumption plan with a minimum number of app instances to be always running in idle mode. When an application scales down to its minimum number of app instances, usage is charged at a reduced idle rate when an app instance is inactive. An app instance enters active mode and is charged at the active rate when it is starting up, when it is processing requests, or when its vCPU or bandwidth usage are above the active billing thresholds1. The first 50 vCPU-hours, 100 memory GB-hours and 2 million requests are free each month and shared in Azure Container Apps environments.
1An app instance is active when vCPU usage is above 0.01 cores or when data received is above 1,000 bytes per second.
Standard dedicated plan
In addition to the consumption plan, you can add dedicated workload profiles to fit characteristics of your workload. Workload profiles determine the amount of compute and memory resources available to Spring apps deployed in the Standard consumption & dedicated plan. See Azure Container Apps workload profile to learn more. You will be billed for the total number of vCPUs and memory provisioned in dedicated workload profile, per second that each instance is running. More than one app can run in a single workload profile depending on how many resources each app requires and the resources available in the workload profile. These workload profiles can automatically scale out to multiple instances as needed.
Standard consumption plan pricing (preview)
Standard consumption | |
---|---|
vCPU active usage / second | $- |
vCPU idle usage / second | $- |
Memory active usage / second | $- |
Memory idle usage / second | $- |
Requests / million | $- |
^Monthly free grant |
50 vCPU-hours 100 memory GB-hours 2 million requests |
Standard dedicated pricing (preview)
Meter | Price |
---|---|
Dedicated plan management (hour) | $- per hour |
vCPU (hour) | $- per hour |
Memory (GiB-hour) | $- per hour |
Eureka and Spring Cloud Config server are Spring components that can be optionally turned on and off in Standard consumption and dedicated plan. You will be billed for the total number of hours Eureka and Spring Cloud Config server are turned on.
Eureka and Spring Cloud Config server pricing (preview)
Meter | Price |
---|---|
Eureka | $- per hour |
Spring Cloud Config server | $- per hour |
Basic
For each app instance in the Basic Plan, Azure Spring Apps charges for one base unit price of 'Basic vCPU and memory group duration', which includes 4 GB of memory and 2 vCPUs. When you exceed either, or both, of the capacities included in the 'Basic vCPU and memory group duration', you will be billed for the actual additional usage based on the total 'Basic Overage Memory Duration' and 'Basic Overage vCPU Duration'. The first 50 vCPU-hours and 100 memory GB-hours are free each month. The first 50 vCPU-hours and 100 memory GB-hours are free each month. Eureka and Spring Cloud Config are included at no extra charge in the Basic price plan.
Standard
For each app instance in the Standard Plan, Azure Spring Apps charges for one base unit price of 'Standard vCPU and memory group duration', which includes 12 GB of memory and 6 vCPUs. When you exceed either, or both, of the capacities included in the 'Standard vCPU and memory group duration', you will be billed for the actual additional usage based on the total 'Standard Overage Memory Duration' and 'Standard Overage vCPU Duration'. The first 50 vCPU-hours and 100 memory GB-hours are free each month. The first 50 vCPU-hours and 100 memory GB-hours are free each month. Eureka, Spring Cloud Config and build service are included at no extra charge in the Standard price plan.
Enterprise
For each app instance in the Enterprise Plan, Azure Spring Apps charges for one base unit price of 'Enterprise vCPU and memory group duration', which includes 12 GB of memory and 6 vCPUs. When you exceed either, or both, of the capacities included in the 'Enterprise vCPU and memory group duration', you will be billed for the actual additional usage based on the total 'Enterprise Overage Memory Duration' and 'Enterprise Overage vCPU Duration'. The first 50 vCPU-hours and 100 memory GB-hours are free each month.
Basic, Standard, Enterprise plan pricing
Basic - For tire kicking and individual dev/test | Standard - For general purpose production workloads | Enterprise - For mission-critical workloads | |
---|---|---|---|
Base price | $-/hour | $-/hour | $-/hour |
Included vCPU and Memory | 2 vCPUs, 4 GB | 6 vCPUs, 12 GB | 6 vCPUs, 12 GB |
Overage vCPU price | $-/vCPU-hour | $-/vCPU-hour | $-/vCPU-hour |
Overage memory price | $-/GB-hour | $-/GB-hour | $-/GB-hour |
*Monthly free grant |
50 vCPU-hours 100 memory GB-hours |
50 vCPU-hours 100 memory GB-hours |
50 vCPU-hours 100 memory GB-hours |
Software IP | - | - | Licensing cost details |
Plan comparison
Standard consumption (preview) | Standard dedicated (Preview) | Standard | Enterprise | Basic | |
---|---|---|---|---|---|
Hosted in Azure Container Apps environments and designed to seamlessly interact with other apps running in the same environment with simplified networking and unified observability. | Hosted in Azure Container Apps environments and designed to seamlessly interact with other apps running in the same environment with simplified networking and unified observability. | Spring centric and opinionated application hosting platform with built-in and pre-configured settings for build, service registry, storage, etc. | Provides VMware Tanzu components and address enterprise requirements around configuration management, integration, portability, flexibility, all backed by commercial support from VMware and Microsoft. | Entry level plan for individual dev/test | |
Limits | |||||
Min App Instance Size | 0.25 vCPU, 0.5 GB | 0.1 vCPU, 0.1 GB | 0.5 vCPU, 0.5 GB | 0.5 vCPU, 0.5 GB | 0.5 vCPU, 0.5 GB |
Max App instance size | 4 vCPU, 8 GB | 16 vCPU, 128 GB | 4 vCPU, 8 GB | 8 vCPU, 32 GB | 1 vCPU, 2 GB |
Start from | 0 vCPU, 0 GB | 4 vCPU, 16 GB | 6 vCPU, 12 GB | 6 vCPU, 12 GB | 2 vCPU, 4 GB |
Max App instances | 400 | 1000 | 500 | 500 | 25 |
Highly available Spring Apps runtime | - | ||||
SLA | Not available during preview | Not available during preview | 99.9% | 99.95% | - |
Persistent storage | Bring Your Own Storage | Bring Your Own Storage | 50 GB per app, up to 10 apps | 50 GB per app, up to 10 apps | 1 GB per app, up to 10 apps |
Pricing model | |||||
Based on consumption (Pay-as-you-go) | Based on provisioned resource | Resource provisioned in base unit + additional usage | Resource provisioned in base unit + additional usage | Resource provisioned in base unit + additional usage | |
App management | |||||
Deploy from Source | Coming soon | Coming soon | Build from source with OSS buildpacks | Build from source with Tanzu buildpacks | - |
Deploy from *Java artifact | Jar | Jar | Jar | Jar, WAR | Jar |
Run Custom Image | |||||
Manually scale in/out or up/down | |||||
Start/stop/restart/delete applications | Coming soon | Coming soon | |||
Rolling update | - | ||||
Spring Apps runtime | |||||
Externalized configuration in git | Spring Cloud Config | Spring Cloud Config | Spring Cloud Config | Application Configuration Service for VMware Tanzu | Spring Cloud Config |
Service registration and discovery | Eureka | Eureka | Eureka | VMware Tanzu Service Registry | Eureka |
Application Gateway | - | - | - | - | |
API Portal | - | - | - | - | |
Application Accelerator | - | - | - | - | |
Application Live View | - | - | - | - | |
Build Service | - | ||||
Blue/Green Deployment | - | ||||
Monitoring & Diagnostics | |||||
Log stream | |||||
Azure Spring Apps Diagnostics | |||||
Metrics and logs in Azure Monitor | |||||
Distributed tracing | |||||
Networking | |||||
VNET integration | - | ||||
SSL termination | |||||
Custom Domains | - | ||||
Security | |||||
Single tenancy | - | - | - | - | |
Managed identities for Azure resources | |||||
Encryption at REST | |||||
Development Tools | |||||
Maven plugin | |||||
IntelliJ plugin | |||||
CI/CD integration | |||||
Service Connector | Coming soon | Coming soon | |||
Programming languages and frameworks | |||||
Polyglot support | Available via Container Apps environment | Available via Container Apps environment | Available via custom image | Available via custom image and VMware Tanzu Build Service | Available via custom image |
Azure pricing and purchasing options

Connect with us directly
Get a walkthrough of Azure pricing. Understand pricing for your cloud solution, learn about cost optimization and request a custom proposal.
Talk to a sales specialistSee ways to purchase
Purchase Azure services through the Azure website, a Microsoft representative, or an Azure partner.
Explore your optionsAdditional resources
Azure Spring Apps
Learn more about Azure Spring Apps features and capabilities.
Pricing calculator
Estimate your expected monthly costs for using any combination of Azure products.
SLA
Review the Service Level Agreement for Azure Spring Apps.
Documentation
Review technical tutorials, videos, and more Azure Spring Apps resources.
Frequently asked questions
-
Azure Spring Apps is billed on a per second basis and metered hourly, in fractional hours calculated based on the number of seconds of usage incurred.
-
Azure Spring Apps resources and overage usage are tracked at the service instance level.
-
A “Basic vCPU and Memory group Duration” includes 4 GB memory and 2 vCPUs. A “Standard vCPU and Memory Group Duration” includes 12 GB memory and 6 vCPUs.
-
Yes, you will be charged for one "vCPU and Memory Group Duration" per service instance according to your pricing tier (basic or standard). Any additional memory and vCPU usage will be billed based on the total count of "Overage Memory Duration" and "Overage vCPU Duration" in our subscription according to your pricing tier for Azure Spring Apps.
-
Rates listed for “vCPU and Memory Group Duration” apply for apps in stopped state. To stop billing completely, delete or stop your service instance
-
Basic tier is intended for individual dev/test usage and does not come with SLA. It is suitable for those looking to explore Azure Spring Apps.
Standard tier is intended for general purpose production workloads and comes with SLA.
Enterprise tier is intended for customers that want commercial VMware Tanzu components and advanced Spring Runtime support.
-
VMware Tanzu license is calculated based on vCPU consumption of user apps running in the Enterprise tier. As an example, considering you have 17.5 vCPU in your Enterprise service instance with the following resource allocation.
Component vCPU consumed Spring cloud gateway 3 Build service 2 API Portal 0.5 User apps 12 Hourly cost = VMware Tanzu license cost x 12
Talk to a sales specialist for a walk-through of Azure pricing. Understand pricing for your cloud solution.
Get free cloud services and a $200 credit to explore Azure for 30 days.