Public Preview for Azure Migrate ASP.NET Assessments & Business Case for Windows Containers

This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Community Hub.

Today we're excited to announce the public preview of ASP.NET Assessments and the Business Case features for Windows Containers on Azure Kubernetes Services (AKS) and App Service via Azure Migrate. 


With these new features, Azure Migrate now provides the following for ASP.NET web apps: 

  1. Cloud readiness for AKS, and App Service  
  2. A recommended configuration of Node SKUs and Node count (or App Service plan) 
  3. The yearly cost savings by running these apps on Azure 


These new features add on top of the existing functionality of discovering and migrating .NET web apps which are already in General Availability. 


In this blog post, we’ll dive deeper into how you can use the Assessment and Business case features with Azure Kubernetes Services: 

  1. Prerequisites
  2. Business Case Overview
  3. Assessment Overview  



To create a business case or an assessment, you first need to create an Azure Migrate project and set up a discovery appliance, allowing you to discover your .NET web apps at-scale. 

The key difference between a business case and an assessment is the granularity. Business case reports are generated at a datacenter (migrate project level) whereas an assessment can be generated for select workloads such as ASP.NET web apps. 


Business Case Overview 

Creating a business case in Azure Migrate provides an auto-generated Total Cost of Ownership (TCO) comparison for all workloads discovered in the migrate project. 

Once created, you can see the estimated yearly cost of your web apps on AKS as well as the overall cost comparison on the Azure PaaS report. 




The AKS section shows the total cost, distribution of the cost by Node Pools and the total number of apps recommended for AKS (there could be other targets such as App Service recommended for your apps, based on migration strategy). 

The cost comparison section compares the TCO between on-prem and Azure across cost categories such as compute, storage, IT labor etc. You can find more information about the Business Case you can refer to Azure Migrate's documentation on this.


Assessment Overview 

Creating an assessment for AKS, you see the readiness status of your apps as well as the estimated cost 


As seen below, the report shows the readiness distribution of 5 apps:  

  1. 2 apps are ready for migration
  2. 2 apps have conditions that need addressing
  3. 1 app is not ready and requires more significant mediation 

The report also projects a cost of $797 to run these apps on AKS, month over month. 




For each web app, you can also see the migration warnings or issues if any and get guidance on resolving/mitigating them. A warning is often a minor fix whereas an error typically requires a breaking change. 




Finally, the assessment also provides a recommended configuration of the AKS cluster (or App Service plan). The recommendation here provides the system and user node SKUs, respective node counts and the app to node association. In particular, the assessment recommends using a Standard_NV6ads_A10_v5 SKU for the Node pool hosting the web apps. 



Similar assessments can be created for Azure App Service (code and containers) 


In Closing 


To get started, you can find detailed guides for creating and understanding these assessments in our documentation – AKS and App Service. We encourage you to utilize Azure Migrate powered assessments to super charge your app modernization journey to Azure. 

Leave a Reply

Your email address will not be published. Required fields are marked *


This site uses Akismet to reduce spam. Learn how your comment data is processed.