Study guide

Azure Migration Services and Tools

Microsoft Azure Fundamentals AZ-900

Track your progress as you read

Finished sections get a check mark.

1 Introduction

About the Microsoft Azure Fundamentals (AZ-900) Exam Study Strategies and Exam Tips

2 Domain 1: Cloud Concepts (25-30%)

1.1 What Is Cloud Computing? 1.2 Cloud Service Models (IaaS, PaaS, SaaS) 1.3 Cloud Deployment Models (Public, Private, Hybrid) 1.4 The Consumption-Based Model

3 Domain 2A: Azure Architecture Components

2.1 Azure Regions and Availability Zones 2.2 Azure Resource Hierarchy (Management Groups, Subscriptions, Resource Groups) 2.3 Azure Resource Manager (ARM) Overview

4 Domain 2B: Azure Compute Services

2.3 Azure Virtual Machines 2.4 Azure App Service, Containers, and Serverless 2.5 Azure Virtual Desktop

5 Domain 2C: Azure Networking Services

2.6 Azure Virtual Networks (VNet) 2.7 Azure VPN Gateway and ExpressRoute 2.8 Azure Load Balancing and Content Delivery

6 Domain 2D: Azure Storage Services

2.9 Azure Storage Accounts and Services 2.10 Azure Database Services 2.11 Azure Data Services and Analytics

7 Domain 2E: Azure Identity, Access, and Security

2.11 Microsoft Entra ID (Azure Active Directory) 2.12 Azure RBAC, Zero Trust, and Defense in Depth 2.13 Azure Security Services

8 Domain 3A: Azure Cost Management

3.1 Factors That Affect Azure Costs 3.2 Azure Pricing Calculator and Cost Management 3.3 Using Tags for Cost Management and Organization

9 Domain 3B: Azure Governance and Compliance

3.3 Azure Policy 3.4 Resource Locks and Tags 3.5 Azure Blueprints, ARM Templates, and Bicep 3.6 Azure Governance Features: Putting It All Together

10 Domain 3C: Azure Monitoring and Management Tools

3.6 Azure Monitor and Service Health 3.7 Azure Compliance, Privacy, and Trust 3.8 Azure Activity Log, Diagnostics, and Resource Health

11 Additional Azure Services and Exam Review

Azure AI and Machine Learning Services Azure IoT and DevOps Services AZ-900 Exam Review: Key Concepts Summary Common AZ-900 Exam Scenarios and Practice

12 Advanced Azure Topics and Service Deep Dives

Azure Migration Services and Tools High Availability and Disaster Recovery in Azure Azure Networking: Private Link, Service Endpoints, and Bastion Azure Management Tools: Portal, CLI, PowerShell, and Cloud Shell Azure SLAs, Service Lifecycle, and Support Plans

Azure Migration Services and Tools

Key Takeaways Explain This Topic AI

The current AZ-900 migration objective names Azure Migrate and Azure Data Box; deeper DMS and strategy details are implementation context.

Azure Migrate discovery and assessment can be no-charge, while replication, networking, test compute, target resources, or partner tools may incur costs.

DMS online/offline availability depends on source and target; online migration reduces planned downtime but cannot guarantee a fixed cutover.

Data Box usable capacity differs from raw capacity: current devices include roughly 120 TB and 525 TB usable options; verify regional availability before selecting a model.

A practical assess–migrate–optimize–operate workflow is editorial, not a fixed exam-tested CAF phase sequence.

Last updated: October 2026

Quick Answer: Azure Migrate supports discovery, assessment, and migration planning for supported workloads. Azure Data Box supports large offline data transfers. Both are listed in the current AZ-900 migration objective. Database Migration Service and detailed migration strategies are useful implementation context, not named objectives. Costs and migration modes vary by scenario.

Azure Migrate: the central hub

Azure Migrate brings discovery, assessment, and supported server-migration workflows into one place. Its discovery and assessment features have no separate service charge, but projects may incur replication storage, network, test-compute, target-resource, or partner-tool charges. Use it when the source and target scenario is supported; the AZ-900 outline names its migration purpose without making it the starting point for every kind of migration. Depending on the source environment and feature, an appliance or connector can discover server inventory, utilization, and dependencies. Validate discovery coverage and data quality before sizing a migration.

What Azure Migrate covers

  • Tool inside Azure Migrate What it does
  • Discovery and assessment Inventories servers, checks Azure-readiness, recommends VM sizes

Server migration Supports selected physical, virtual, and cloud-source scenarios; check current support and costs

  • Database assessment Supported database tooling identifies compatibility and target options
  • Web app assessment Evaluates ASP.NET/Java apps for Azure App Service
  • Azure Virtual Desktop assessment Available planning scenarios depend on current product support

An assessment can report Azure-readiness , an Azure SKU recommendation, and a modeled monthly cost for supported workloads. Azure Migrate offers performance-based sizing when adequate performance history is available and as-is sizing based on provisioned capacity; inspect the selected assessment setting before interpreting a recommended VM size.

Azure Database Migration Service (DMS)

Azure Database Migration Service (DMS) supports specified source-to-target migrations; its mode and availability vary by pair. These details go beyond the current AZ-900 migration objective, which names Azure Migrate and Azure Data Box.

Source Common Azure target

SQL Server Selected Azure SQL Database, SQL Managed Instance, or SQL VM scenarios; online support differs by target

  • MySQL Check supported Azure Database for MySQL migration scenario
  • PostgreSQL Check supported Azure Database for PostgreSQL migration scenario
  • Other engines Consult the current source-target support matrix before selecting DMS
  • Mode Behavior Downtime
  • Offline Migrate with an application outage or controlled pause Depends on data size and method

Online Synchronize while source remains available, then plan cutover Usually lower downtime, but no guaranteed duration

Worked example: A retailer wants to migrate SQL Server to Azure SQL Managed Instance while minimizing downtime. First verify that the source-target pair and online mode are supported, then test replication and rehearse cutover. Online migration can reduce downtime, but it cannot promise a five-minute window. A development copy may be moved offline if the outage is acceptable.

The Data Box family: offline transfer

When you must move tens of terabytes or more and your internet link is slow, copying over the wire could take weeks. Azure Data Box is the physical answer — Microsoft ships you a ruggedized, encrypted device, you copy data locally, and ship it back.

  • Device Usable capacity Typical use
  • Data Box Disk Capacity depends on ordered disks and current availability Smaller offline transfers
  • Data Box Current options include about 120 TB or 525 TB usable; check regional catalog Large offline transfers

Workflow: order in the portal, Microsoft ships it, you copy data over local SMB/NFS, ship it back, Microsoft uploads it to your storage account, then securely wipes the device to NIST standards.

Migration strategies — the 5 Rs

The following five labels are a useful planning vocabulary, not a claimed AZ-900 tested sequence. Actual migration strategy depends on workload, risk, time, and target architecture.

Rehost (lift and shift): move an application to Azure IaaS with little or no code change. It can shorten an initial move, but operational, compatibility, security, and cost risks still require assessment. Consider it when time is constrained and the existing architecture can run appropriately in Azure.

Refactor: make minor changes so the app runs on PaaS such as Azure App Service or Azure SQL Database. You shed some patching and server management without rewriting business logic.

Rearchitect: redesign the application for cloud-native patterns such as microservices, containers (Azure Kubernetes Service), or serverless (Azure Functions). Higher effort, higher long-term payoff.

Rebuild: discard the old code and build fresh as a cloud-native app.

Replace: retire the application entirely and adopt a SaaS product such as Dynamics 365 instead.

The Cloud Adoption Framework migration journey

A practical migration plan can be organized as assess, migrate, optimize, then operate securely . This is an editorial workflow, not a fixed Cloud Adoption Framework phase sequence or a published AZ-900 question pattern:

  • Phase Key actions
  • Assess Inventory workloads, map dependencies, build a modeled business case with Azure Migrate
  • Migrate Choose a strategy (the 5 Rs), replicate, cut over, and validate
  • Optimize Right-size VMs, apply Reserved Instances and Azure Hybrid Benefit, tier cold data
  • Secure and Manage Turn on Microsoft Defender for Cloud, Azure Policy, monitoring, and backup

An Azure Migrate business case can model on-premises and Azure economics from assessment inputs, while the Pricing Calculator estimates planned Azure services. The TCO Calculator has been retired. Right-sizing during optimization may reduce cost. Confirm discovery coverage, assessment mode, and performance history before acting on a smaller-SKU recommendation.

On the Exam: "Large data, limited bandwidth, move to Azure" = Data Box . "Discover and assess on-premises servers" = Azure Migrate . For database migration, check the supported target and online/offline methods before selecting DMS. Rehosting means moving with minimal code change. For migration economics, use Azure Migrate business-case analysis; the current AZ-900 outline names Azure Migrate and Data Box.