Tutorial: Assess web apps for migration to Azure App Service

In this tutorial, you learn how to:

Prerequisites

• If you don't have an Azure subscription, create a free account before you begin.
• Before you follow this tutorial to assess your web apps for migration to Azure App Service, make sure you've discovered the web apps you want to assess using the Azure Migrate appliance for VMware, Hyper-V, or Physical servers.
• If you want to try out this feature in an existing project, ensure that you have completed the prerequisites in this article.

Run an assessment

To run an assessment, follow these steps:

1. Sign into the Azure portal and search for Azure Migrate.

2. On the Azure Migrate page, under Migration goals, select Servers, databases and web apps.

3. On the Servers, databases and web apps page, under Assessments tools, select Web apps on Azure from the Assess dropdown menu.

   

4. On the Create assessment page, under Basics tab, do the following:

   1. The assessment type is pre-selected as Web apps on Azure and the discovery source defaulted to Servers discovered from Azure Migrate appliance. Select the Scenario as Web apps to App Service.

      

   2. Select Edit to review the assessment properties.

      The following are included in Azure App Service assessment properties:

      

      Property	Details
      Target location	The Azure region to which you want to migrate. Azure App Service configuration and cost recommendations are based on the location that you specify.
      Environment type	Type of environment in which it's running.
      Offer	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)	The Savings option the assessment must consider.
      Isolation required	Select Yes if you want your web apps to run in a private and dedicated environment in an Azure datacenter.

   • In Savings options (Compute), specify the savings option that you want the assessment to consider, helping to optimize your Azure Compute cost.
     • Azure reservations (one year or three year reserved) are a good option for the most consistently running resources.
     • Azure Savings Plan (one year or three year savings plan) provides additional flexibility and automated cost optimization. Ideally post migration, you could use Azure reservation and savings plan at the same time (reservation is consumed first), but in the Azure Migrate assessments, you can only see cost estimates of 1 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.
   1. Select Save if you made any changes.

5. On the Create assessment page, select Next: Select servers to assess.

6. Under the Select servers to assess tab, do the following:

   • Assessment name: Specify a name for the assessment.
   • Select or create a group: Select Create New and specify a group name. You can also use an existing group.
   • Appliance name: Select the appliance.
   • Web app type: Select ASP.NET.
   • Web app type: Select Java.
   • Select the servers that you want to add to the group from the table.
   • Select Next.

   

7. Under Review + create assessment tab, review the assessment details, and select Create assessment to create the group and run the assessment.

   

8. After the assessment is created, go to Servers, databases and web apps > Azure Migrate: Discovery and assessment. Refresh the tile data by selecting the Refresh option on top of the tile. Wait for the data to refresh.

9. On the Servers, databases and web apps page, under Assessment tools > Assessments, select the number next to Web apps on Azure in the Assessment section.

10. Select the assessment name, which you wish to view.

Review an assessment

To view an assessment, follow these steps:

1. On the Azure Migrate page, under Migration goals, select Servers, databases and web apps.

2. On the Servers, databases and web apps page, under Assessment tools > Assessments, select the number next to the Web apps on Azure assessment.

3. On the Assessments page, select a desired assessment name to view from the list of assessments.

   

   The Overview page contains 3 sections:

   • Essentials: The Essentials section displays the group the assessed entity belongs to, its status, the location, discovery source, and currency in US dollars.
   • Assessed entities: This section displays the number of servers selected for the assessments, number of Azure app services in the selected servers, and the number of distinct Sprint Boot app instances that were assessed.
   • Migration scenario: This section provides a pictorial representation of the number of apps that are ready, ready with conditions, and not ready. You can see two graphical representations, one for All Web applications to App Service Code and the other for All Web applications to App Service Containers. In addition, it also lists the number of apps ready to migrate and the estimated cost for the migration for the apps that are ready to migrate.

4. Review the assessment summary. You can also edit the assessment properties or recalculate the assessment.

Review readiness

To review the readiness for the web apps, follow these steps:

1. On Assessments, select the name of the assessment that you want to view.

2. Select View more details to view more details about each app and instances. Review the Azure App service Code and Azure App service Container readiness column in the table for the assessed web apps:

   

   1. If there are no compatibility issues found, the readiness is marked as Ready for the target deployment type.
   2. 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.
   3. 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.
   4. If the discovery is still in progress or there are any discovery issues for a web app, the readiness is marked as Unknown as the assessment couldn't compute the readiness for that web app.
   5. If the assessment isn't up-to-date, the status shows as Outdated. Select the corresponding assessment and select Recalculate assessment. The assessment is recalculated and the Readiness overview screen is updated with the results of the recalculated assessments.

3. Select the Readiness status to open the Migration issues and warnings pane with details of the cause of the issue and recommended action.

   

4. Review the recommended SKU for the web apps, which is determined as per the matrix below:

   Readiness	Determine size estimate	Determine cost estimates
   Ready	Yes	Yes
   Ready with conditions	Yes	Yes
   Not ready	No	No
   Unknown	No	No

Review cost estimates

The assessment summary shows the estimated monthly costs for hosting your web apps.
Select the Cost details tab to view a monthly cost estimate depending on the SKUs.

Next steps

• Learn how to perform at-scale agentless migration of ASP.NET web apps to Azure App Service.
• Learn more about how Azure App Service assessments are calculated.