azureblog.co.uk
← AZ-305 study plan
AZ-305 · Design infrastructure solutions

Design migrations

The Cloud Adoption Framework approach, assessing on-premises estates, migrating to IaaS and PaaS, and moving databases and unstructured data.

  • 16 min
  • 5 concepts
  • Try it yourself
  • 4-question check

Learn

A migration is a project, not a copy job. The Cloud Adoption Framework gives the method; Azure Migrate gives the tools to discover, assess and move workloads.

  1. 1

    Evaluate a migration solution that leverages the Microsoft Cloud Adoption Framework for Azure

    The CAF phases include Strategy, Plan, Ready (landing zones), Adopt (migrate and innovate), and ongoing Govern, Secure and Manage. For each workload pick a migration strategy: rehost (lift and shift), replatform (small changes, e.g. to PaaS), refactor, rearchitect, rebuild, replace (SaaS) or retire/retain.

    Remember: Ready = landing zones before anything moves.

  2. 2

    Evaluate on-premises servers, data, and applications for migration

    Azure Migrate discovers servers (VMware, Hyper-V, physical) with an appliance or agentless, maps dependencies, and creates assessments: readiness, right-sized SKUs and monthly cost (with Azure Hybrid Benefit) for Azure VMs, SQL, web apps and AVS. Business cases compare on-premises and Azure costs.

    Remember: Dependency analysis groups servers that must move together.

  3. 3

    Recommend a solution for migrating workloads to infrastructure as a service (IaaS) and platform as a service (PaaS)

    IaaS: Azure Migrate server migration (agentless for VMware and Hyper-V) replicates VMs with test migrations before cutover. Azure VMware Solution moves VMware workloads unchanged. PaaS: App Service migration tooling in Azure Migrate for .NET and Java web apps, or containerise apps for AKS or Container Apps.

    Remember: Keep VMware tooling: Azure VMware Solution.

  4. 4

    Recommend a solution for migrating databases

    Use Azure Database Migration Service (and the Azure SQL migration extension in Azure Data Studio or the portal) for online (minimal downtime) or offline migration of SQL Server to Azure SQL MI, SQL Database or SQL on VMs. Assess compatibility first. Managed Instance link uses distributed availability groups for near-zero downtime. Use DMS for MySQL and PostgreSQL too.

    Remember: Minimal downtime: online migration.

  5. 5

    Recommend a solution for migrating unstructured data

    AzCopy for scripted copies, Azure Storage Mover for managed migration of file shares to Azure Files or Blob, Azure File Sync to sync and tier file servers, and Azure Data Box family for offline transfer of large datasets (tens to hundreds of TB) where bandwidth is limited.

    Remember: Too big for the network: Data Box.

A migration with Azure Migrate

  1. DiscoverAppliance inventories servers and dependencies.
  2. AssessReadiness, sizing and cost.
  3. ReplicateContinuous replication to Azure.
  4. Test migrateRun in an isolated network.
  5. Cut overMigrate, then decommission the source.

Try it

Which tool or strategy?

This interactive part needs JavaScript.

In the portal

  • Azure MigrateAzure portal: Azure Migrate > Servers, databases and web apps
  • Database Migration ServiceAzure portal: Azure Database Migration Services > Create
  • Storage MoverAzure portal: Storage Movers > Create

Key terms

Click a card to see the definition.

Check your understanding

4 questions. Score 80% or more and these skills are marked as confident in your AZ-305 study plan.

  1. Which CAF phase prepares landing zones?

  2. Which tool assesses readiness and cost of on-premises servers?

  3. Moving an app to App Service with small changes is which strategy?

  4. Which manages migration of file shares to Azure Files?

Sources

Facts in this lesson are from Microsoft Learn. This site isn't affiliated with Microsoft.