Discovering GCP Instance for Migration to Azure VM — Part 1

5 min readAug 11, 2023

Introduction

The process of migrating Google Cloud Platform (GCP) virtual machines (VMs) to Microsoft Azure involves a crucial initial step: discovering the servers to be migrated. This phase ensures a comprehensive assessment of your existing GCP infrastructure, aiding in efficient migration planning. By accurately identifying and assessing VMs, you can make informed decisions and proceed with a seamless and successful migration to Azure. This article details the key steps and considerations involved in the discovery process, setting the foundation for a well-executed migration project.

Discovery in Azure migration refers to the initial phase of the migration process where the existing on-premises or cloud-based resources, such as virtual machines, servers, applications, and databases, are identified, inventoried, and assessed for migration to Microsoft Azure. It involves using tools and techniques to gather essential information about the source environment, including configuration, dependencies, and performance characteristics.

Prerequisites:

Create an instance in Google Cloud Platform (GCP) that needs to be migrated (the source VM). And enable an IIS service in it.

Install an IIS server on the source VM in GCP.

Preparing Azure for Migration with the Migration and Modernization Tool

Open the Migration and Modernization Tool interface.

Navigate to the “Servers, Databases, and Web Apps Discovery” section.

Create a new project dedicated to migration and discovery.

Click on the “Discover” option to initiate the discovery process.

Choose the appropriate virtualization type, such as “Physical” or “Others (GCP).”

Generate a project key by providing a name to the appliance.

Click on “Generate key.” This key will be used to register the discovery appliance with your Azure Migrate project.

Installing Azure Migrate Appliance:

Copy the download link for the Azure Migrate appliance from the Azure portal to the Remote Desktop Protocol (RDP) session on the GCP instance.

Download the Azure Migrate installer within the RDP instance.

Run the Azure Migrate installer in the RDP instance.

Copy the installation path and navigate to that path in PowerShell.

Execute the command “.\AzureMigrateInstaller.ps1” to run the installation.

Running Azure Migrate Appliance Configuration Manager:

Open the “Azure Migrate Appliance Configuration Manager.”

Run the configuration manager; it will handle prerequisite checks.

Copy the Project Key generated earlier and paste it into the appropriate field.

The key will be verified, indicated by a green check mark.

Checking Azure Portal for Appliances:

While the configuration manager is running, check the Azure portal for appliances related to the migration.

Confirming Successful Discovery:

Verify in the Azure portal that the VMs have been successfully discovered.

This step ensures that the discovery process has accurately identified the VMs in your GCP instance.

FAQs:

What is Discovered ?

Virtual Machines (VMs), Networking Storage, Applications Data, Workloads

What Might Not Be Discovered ?

Legacy Systems, Unmanaged Resources, Custom Applications, Network Complexity, Regulatory and Compliance Considerations, Specialized Hardware

Why migrate to Azure ?

Migrating to Azure offers several advantages, including reduced infrastructure costs, scalability, enhanced security features, simplified management, and access to a wide range of Azure services for application modernization.

How do I monitor and manage migrated resources in Azure?

Azure offers tools like Azure Monitor and Azure Security Center for monitoring and managing resources. These tools provide insights into performance, security, and compliance, helping you maintain the health of your migrated environment.

Below are the document links for reference:

https://learn.microsoft.com/en-us/azure/migrate/tutorial-migrate-gcp-virtual-machines

https://learn.microsoft.com/en-us/azure/migrate/troubleshoot-discovery