Assessment overview (migrate to Azure Spring Apps) (preview)
This article provides an overview of assessments for migrating on-premises Spring Boot apps to Azure Spring Apps using the Azure Migrate: Discovery and assessment tool.
What's an assessment?
An assessment with the Discovery and assessment tool is a point in time snapshot of data and measures the readiness and provides cost details to host on-premises servers, databases, and web apps to Azure.
Types of assessments
The Azure Migrate: Discovery and assessment tool supports the following four types of assessments:
| Assessment Type | Details |
|---|---|
| Azure VM | Assessments to migrate your on-premises servers to Azure virtual machines. You can assess your on-premises servers in VMware environment, Hyper-V environment, and physical servers for migration to Azure VMs using this assessment type. |
| Azure SQL | Assessments to migrate your on-premises SQL servers from your VMware environment to Azure SQL Database or Azure SQL Managed Instance. |
| Web apps on Azure | Assessments to migrate your on-premises Spring Boot apps to Azure Spring Apps or ASP.NET/Java web apps to Azure App Service. |
| Azure VMware Solution (AVS) | Assessments to migrate your on-premises VMware VMs to Azure VMware Solution (AVS). Learn more. |
An Azure Spring Apps assessment provides the following sizing criteria:
| Sizing criteria | Details | Data |
|---|---|---|
| Performance-based | Assessment that makes recommendations based on collected resource consumption data | The Azure Spring Apps assessment is calculated based on the memory consumption of your discovered workload, and an estimated consumption of CPU cores. |
How do I assess my on-premises Spring Boot apps?
You can assess your on-premises Spring Boot apps using the configuration data collected by a lightweight Azure Migrate appliance. The appliance discovers on-premises Spring Boot apps and sends the configuration data to Azure Migrate. Learn more.
How do I assess with the appliance?
If you're deploying an Azure Migrate appliance to discover on-premises servers, do the following steps:
- Set up Azure and your on-premises environment to work with Azure Migrate.
- For your first assessment, create an Azure Migrate project.
Note
The Azure Migrate: Discovery and assessment tool gets added to the project by default.
- Deploy a lightweight Azure Migrate appliance. The appliance continuously discovers on-premises servers and sends configuration and performance data to Azure Migrate. Deploy the appliance as a VM or a physical server. You don't need to install anything on servers that you want to assess.
After the appliance begins discovery, you can gather servers (hosting Spring Boot apps) that you want to assess into a group and run an assessment for the group with assessment type Web apps on Azure.
Learn more about Spring Boot apps assessments.
What properties are used to customize the assessment?
The following are included in Azure Spring Apps assessment properties:
| Setting | Details |
|---|---|
| Target location | The Azure region to which you want to migrate. Azure Spring Apps configuration and cost recommendations are based on the location that you specify. |
| Environment type | Specifies the environment to apply pricing applicable to Production or Dev/Test. |
| Offer/Licensing program | The Azure offer in which you're enrolled. The assessment estimates the cost for that offer. |
| Currency | The billing currency for your account. |
| Discount (%) | Any subscription-specific discounts that you receive on top of the Azure offer. The default setting is 0%. |
| EA subscription | Specifies that an Enterprise Agreement (EA) subscription is used for cost estimation. Takes into account the discount applicable to the subscription. Retain the default settings for reserved instances and discount (%) properties. |
| Savings options (compute) | Specify the savings option that you want the assessment to consider. This helps to optimize your Azure Compute cost. We recommend Azure reservations (one year or 3 years reserved) for the most consistently running resources. Azure Savings Plan (one year or 3 years savings plan) provide more flexibility and automated cost optimization. Ideally post-migration, you could use Azure reservation and savings plan at the same time (reservation is first), but in the Azure Migrate assessments, you can only see cost estimates of one savings option at a time. When you select None, the Azure Compute cost is based on the Pay-as-you-go rate or based on actual usage. You need to select Pay-as-you-go in Offer/licensing program to be able to use Reserved Instances or Azure Savings Plan. When you select any savings option other than None, the Discount (%) setting isn't applicable. The monthly cost estimates are calculated by multiplying 744 hours with the hourly price of the recommended SKU. |
Calculate readiness
Azure Spring Apps readiness for Spring Boot apps is based on feature compatibility checks between on-premises configuration of Spring Boot apps and Azure Spring Apps:
- The Azure Spring Apps assessment considers the Spring Boot apps configuration data to identify compatibility issues.
- If there are no compatibility issues found, the readiness is marked as Ready for the target deployment type.
- If there are non-critical compatibility issues, such as degraded or unsupported features that don't block the migration to a specific target deployment type, the readiness is marked as Ready with conditions (hyperlinked) with warning details and recommended remediation guidance. You may migrate such apps first and optimize later.
- If there are any compatibility issues that may block the migration to a specific target deployment type, the readiness is marked as Not ready with issue details and recommended remediation guidance.
- If the discovery is still in progress or there are any discovery issues for a Spring Boot app, the readiness is marked as Unknown as the assessment couldn't compute the readiness for that Spring Boot app.
Calculate sizing
The assessment summary shows the estimated monthly costs for hosting your apps in Spring Apps. In Azure Spring Apps, you pay charges per Azure Spring Apps service instance and not per app. One or more apps can be configured to run on the same service instance. Whatever apps you put into this Azure Spring Apps service instance are all up to you.
For the purpose of cost estimation, we assume you include all your accessed apps into the same Azure Spring Apps service instance. Learn more about the details of Azure Spring Apps pricing from the pricing page and pricing calculator. The monthly cost on this card assumes each month has 744 hours instead of 730 hours.
The estimated cost applies for both Azure Spring Apps Standard Tier and Enterprise Tier. For Enterprise Tier, there will be additional cost on software IP and resource consumption for Tanzu components, which are not included in cost estimation.
Next steps
- Learn how to run an Azure Spring Apps assessment.