Assessing workloads

In this guide, we explore how to assess various workloads—including ASP.NET, .NET Core, Java, PHP, SAP, and specialized high-performance computing workloads—using Microsoft’s powerful assessment tools. These tools enable you to evaluate and prepare your on-premises environments for a seamless migration to Azure.

Overview of Assessment Tools

Microsoft provides a suite of tools tailored to different workload types. The core tool is the Server Assessment, integrated into Azure Migrate, which combines both assessment and migration functionalities to offer an end-to-end process. By deploying a lightweight appliance on your on-premises environment, Azure Migrate collects detailed workload data (such as memory, CPU, and operating system details from virtual machines) and transfers it to Azure for analysis. Azure then calculates a readiness score that indicates whether a workload is ready for migration, requires changes, or is not supported.

Additional assessment tools include:

• Database Assessment (DMA Tool): Also known as the Database Migration Assistant, this utility examines your on-premises Microsoft SQL Server databases. It highlights compatibility issues and evaluates migration readiness for Azure SQL Database, Azure SQL Managed Instance, or SQL Server on a VM.
• Web App Assessment: This tool assists in evaluating on-premises web applications in preparation for migration to Azure.

Other valuable tools are:

• TCO Calculator: This tool, while not a complete assessment solution, helps you estimate the total cost of ownership and potential savings when adopting cloud services.
• Service Map: By installing an agent on each machine, Service Map creates a comprehensive dependency analysis and visualizes how servers and processes are interconnected. This is particularly beneficial for understanding virtual machine dependencies prior to migration.

Exploring Azure Migrate in the Azure Portal

Within the Azure portal, the Azure Migrate section provides a central location to initiate workload assessments.

Creating a Migration Project

To get started, create a new migration project by following these steps:

1. Define the project parameters, for example:

   • Resource Group: Migrate RG
   • Project Name: NYC to Azure (assuming a migration for a New York City data center)
   • Geography: United States

   This project aggregates all assessment data from your on-premises environment.

2. Note that historically, Azure Site Recovery handled migrations by replicating workloads to Azure before performing a cutover. Today, Azure Migrate offers a complete picture that integrates both assessment and migration capabilities.

Assessment Phase

Within your Azure Migrate project, the assessment process is divided into two primary sections:

• Discovery and Assessment: Gather data from your on-premises environment.
• Migration and Modernization: Utilize tools for migrating and modernizing workloads after the assessment.

Data Collection Methods

Data can be collected in two primary ways: using an on-premises appliance or by importing a CSV file.

Importing Data via CSV

1. Download the CSV template provided by Azure.
2. Populate the template with the required details such as server name, IP address, core count, memory, and operating system information. Some fields are mandatory while others are optional.

3. Upload the completed CSV file back to Azure.

Using an On-Premises Appliance

Deploy an appliance within your environment for automated data collection. Depending on your infrastructure:

• For VMware environments: Generate a project key, download the OVA file, deploy the appliance, and configure it.
• For Hyper-V: Utilize the provided VHD file.
• For physical servers or AWS environments: Download a ZIP file and run a PowerShell script on a Windows Server (minimum requirements: Windows Server 2016, 16 GB memory, 8 vCPUs, and 80 GB storage).

The appliance automatically sends the required data to Azure for the assessment.

Database Assessment with DMA

Install the Database Migration Assistant (DMA) on your on-premises SQL Server to identify compatibility issues and examine migration challenges.

Initiating an Assessment

After gathering your server data, begin the assessment process with these steps:

1. If using the CSV method, upload your CSV file.
2. Wait approximately 10 minutes for the import process to complete.
3. Review the assessment results, including any warnings (e.g., disk sizing issues) and the total number of records processed.

Once the import is successful and your environment data is discovered (for example, 10 servers comprising 8 Windows and 2 Linux servers), proceed to configure the assessment for Azure VMs.

Configuring Assessment Settings

1. Select the assessment for Azure VMs.
2. Click "Edit" within the assessment settings to adjust parameters such as reservation options and target VM series. For example, choose "None" for reservation and "Select All" for VM series.
3. Configure additional licensing options like Azure Hybrid Benefit if applicable.

Running the assessment will generate a detailed report that includes:

• The number of machines ready for migration
• Workloads that require modifications or are not supported
• Estimated compute and storage costs

Next Steps: Utilizing Migration Tools

Following the assessment phase, you can proceed to the migration stage by leveraging the migration tools available within Azure Migrate. These tools facilitate the actual migration and modernization of your workloads based on the assessment results.

Before initiating migration, ensure you have enabled dependency analysis by installing agents that create a comprehensive service map of your environment. This step is essential for understanding interdependencies and ensuring a smooth transition.

This guide concludes our discussion on assessment tools. In the upcoming section, we will dive deep into the migration tools offered by Azure Migrate and explore how they help you efficiently move your workloads to the cloud.

For further details, visit:

• Azure Migrate Documentation
• Microsoft SQL Server to Azure Migration Guide
• Service Map Documentation

Happy migrating!