Study guide

12.1 Migration Assessment: Cloud Adoption Framework & On-Premises Evaluation

Exam AZ-305: Designing Microsoft Azure Infrastructure Solutions Exam

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Orientation

1.1 AZ-305 Current Exam Facts & Format 1.2 Candidate Profile, Prerequisites & the AZ-104 Requirement 1.3 Skills Outline, Domain Weights & How to Use This Guide

2 Chapter 2: Logging, Monitoring & Diagnostics Design

2.1 Logging Solution Design 2.2 Log Routing Design 2.3 Azure Monitor Metrics & Alerting Design 2.4 Application Insights & Diagnostic Monitoring Design

3 Chapter 3: Authentication & Authorization Design

3.1 Authentication Solution Design 3.2 Identity Management Design 3.3 Authorization for Azure Resources 3.4 Authorization for On-Premises Resources 3.5 Secrets, Certificates & Key Management Design

4 Chapter 4: Governance, Compliance & Identity Governance Design

4.1 Management Group & Subscription Hierarchy Design 4.2 Resource Group Organization & Tagging Strategy Design 4.3 Compliance Management Design 4.4 Identity Governance Design

5 Chapter 5: Relational Data Storage Design

5.1 Relational Data Storage Selection 5.2 Database Service & Compute Tier Design 5.3 Database Scalability Design 5.4 Relational Data Protection Design

6 Chapter 6: Semi-Structured & Unstructured Data Storage Design

6.1 Semi-Structured Data Storage Design 6.2 Unstructured Data Storage Design 6.3 Storage Tier & Cost-Performance Trade-off Design 6.4 Unstructured Data Protection & Durability Design

7 Chapter 7: Data Integration & Analytics Design

7.1 Data Integration Pipeline Design 7.2 Event-Based & Real-Time Data Integration Design 7.3 Data Analytics Platform Design

8 Chapter 8: Backup & Disaster Recovery Design

8.1 Recovery Objectives Design: Calculating and Meeting RTO/RPO 8.2 Azure Site Recovery Architecture for Hybrid Workloads 8.3 Compute Backup & Recovery Design 8.4 Database Backup & Recovery Design 8.5 Unstructured Data Backup & Recovery Design

9 Chapter 9: High Availability Design

9.1 Compute High Availability: Availability Sets & Availability Zones 9.2 Compute High Availability: Load Balancing & VM Scale Set Design 9.3 Relational Data High Availability Design 9.4 Semi-Structured & Unstructured Data High Availability Design

10 Chapter 10: Compute Solution Design

10.1 Compute Requirements Analysis & Virtual Machine-Based Solution Design 10.2 Container-Based Solution Design (AKS, Container Apps, Azure Container Instances) 10.3 Serverless-Based Solution Design (Azure Functions, Logic Apps) 10.4 Batch Processing Solution Design (Azure Batch, HPC Workloads)

11 Chapter 11: Application Architecture Design

11.1 Messaging Architecture Design (Service Bus, Queue Storage) 11.2 Event-Driven Architecture Design (Event Grid, Event Hub) 11.3 API Integration & Application Caching Design (API Management, Azure Cache for Redis, CDN) 11.4 Application Configuration Management & Automated Deployment Design (App Configuration, DevOps Pipelines, Deployment Slots)

12 Chapter 12: Migration Design

12.1 Migration Assessment: Cloud Adoption Framework & On-Premises Evaluation 12.2 IaaS & PaaS Workload Migration Design 12.3 Database Migration Design (Data Migration Service, Database Migration Assistant) 12.4 Unstructured Data Migration Design (AzCopy, Data Box, Storage Migration Service)

13 Chapter 13: Network Solution Design

13.1 Internet Connectivity Design 13.2 Hybrid Connectivity Design 13.3 Network Security Optimization Design 13.4 Network Performance Optimization & Load-Balancing/Routing Design

14 Chapter 14: Final Review, Exam Strategy & Career Path

14.1 Cross-Domain Scenario Practice: Combining Identity, Data, Continuity & Infrastructure Decisions 14.2 Common AZ-305 Decision Traps 14.3 Final Study Plan & Practice Assessment Strategy 14.4 After AZ-305: Retake Policy, Renewal & Career Path

12.1 Migration Assessment: Cloud Adoption Framework & On-Premises Evaluation

Key Takeaways Explain This Topic AI

CAF's Migrate methodology follows Assess -> Deploy (Migrate) -> Release, with Azure Migrate powering the Assess step

The six migration strategies are Rehost, Refactor, Rearchitect, Rebuild, Replace, and Retire/Retain -- match the strategy to the stated constraint, not the theoretical ideal

Performance-based sizing (actual utilization) is the cost-optimization answer; as-on-premises sizing matches configured specs and often over-provisions

Azure Migrate's business case feature builds TCO comparisons from real discovered inventory rather than generic estimates (Microsoft's standalone TCO calculator has been retired)

Dependency visualization groups interdependent servers into the same migration wave to avoid breaking application connectivity

Last updated: October 2026

Why This Topic Matters

AZ-305's Migrations subgroup opens with the two bullets that come before you pick any target service: "Evaluate a migration solution that leverages the Microsoft Cloud Adoption Framework (CAF) for Azure" and "Evaluate on-premises servers, data, and applications for migration." Exam scenarios in this area rarely ask "which VM size?" — they ask "what should you do first , before you touch a single resource in Azure?" Getting this wrong on the exam (and in practice) means recommending a migration tool before you have discovered what you actually have, sized it correctly, or built a business case a stakeholder will approve.

Cloud Adoption Framework: The Migrate Methodology

The Cloud Adoption Framework (CAF) is Microsoft's prescriptive methodology for moving to and operating in Azure. CAF organizes adoption into phases — Strategy, Plan, Ready, Adopt (which includes Migrate and Innovate), Govern, Manage, and Secure — with Migrate as the phase an AZ-305 architect owns most directly. Inside Migrate, CAF defines a repeatable loop:

Assess — inventory workloads, assess technical readiness, and estimate cost/effort.

Deploy (Migrate) — execute the move using the appropriate migration tooling.

Release (Optimize/Promote) — validate the workload in production, decommission the source, and optimize cost/performance.

The most heavily tested CAF artifact is the set of migration strategies , historically called the "5 Rs" and now commonly extended to six:

Strategy Definition Typical Azure Target Example Trigger

Rehost Lift-and-shift with no code change Azure VMs (IaaS) Tight deadline, legacy app with OS-level dependencies

Refactor / Repackage Minor changes to run on a managed platform App Service, AKS, Container Apps App is stateless and uses a supported runtime

Rearchitect Modify/extend the app for cloud-native scale Microservices on AKS, Azure SQL Database Monolith needs independent scaling of components

Rebuild Discard the old app; build new on PaaS/serverless Azure Functions, Logic Apps Legacy code is unmaintainable or licensing-locked

Replace (Repurchase) Swap for a SaaS equivalent Dynamics 365, Microsoft 365 Custom app duplicates a commodity SaaS capability

Retire / Retain Decommission unused assets, or keep on-premises N/A App has no users, or compliance mandates on-prem

Exam trap: a question that says "migrate with no application changes and the shortest possible timeline" is asking for Rehost , even if PaaS would be "better" long-term — AZ-305 rewards matching the stated constraint , not the theoretically optimal architecture.

Azure Migrate: The Assessment Engine

Azure Migrate is the central hub for the Assess step and the tool AZ-305 expects you to name whenever a scenario needs discovery, sizing, or a business case:

Discovery : an Azure Migrate appliance deployed on-premises connects to VMware vCenter or Hyper-V hosts for agentless discovery (no software installed inside each VM). Physical servers, other clouds (AWS/GCP), and scenarios needing deeper OS-level telemetry use agent-based discovery (Azure Migrate: Discovery and assessment agent plus the Dependency agent).

Assessment sizing modes : "As on-premises" sizing matches the Azure VM SKU to the source server's configured specs (safe, but often over-provisions). Performance-based sizing uses actual CPU/memory/disk utilization history to right-size — this is the mode to recommend when a scenario emphasizes cost optimization.

Dependency visualization : maps which servers talk to which, so you group interdependent workloads into the same migration wave — migrating a web tier without its database tier in the same wave breaks the application.

Business case : compares multi-year on-premises TCO against Azure, factoring in Azure Hybrid Benefit , Reserved Instances , and right-sizing savings, using your actual discovered inventory rather than generic assumptions. This is the correct answer whenever a scenario asks for an executive-ready cost justification — generic estimates use assumed, not discovered, data (Microsoft's standalone TCO calculator has been retired).

Evaluating On-Premises Servers, Data, and Applications

Before recommending any target, an architect inventories four things: compute (OS version and support status — Azure Migrate flags servers on end-of-support OS like older Windows Server releases), applications (dependency mapping, licensing constraints), data (structured vs. unstructured, classification, compliance residency requirements), and network (available bandwidth, which determines whether an online transfer is even feasible within the maintenance window — a calculation you'll reuse in Section 12.4).

Exam Scenario

Contoso has 500 on-premises VMware VMs and wants a board-ready comparison of three-year on-premises costs versus Azure, including savings from right-sizing and existing Windows Server licenses. The correct recommendation is Azure Migrate: Discovery and assessment with the business case feature — not the Azure pricing calculator (Microsoft's standalone TCO calculator has been retired), and not Azure Migrate: Server Migration (that tool executes moves; it doesn't build cost cases).

Key Takeaways

CAF's Migrate methodology is Assess → Deploy (Migrate) → Release; Azure Migrate powers the Assess step.

Match the migration strategy (Rehost/Refactor/Rearchitect/Rebuild/Replace/Retire) to the stated constraint, especially timeline and code-change tolerance.

Use performance-based sizing (not as-on-premises sizing) when a scenario asks for cost optimization.

The Azure Migrate business case feature — not a generic calculator — is the answer for discovered-inventory-based TCO comparisons.

Dependency mapping determines migration wave grouping; never split tightly-coupled tiers across waves.