The Microsoft Cloud Adoption Framework (CAF) provides five core migration patterns to move workloads to Azure, each matching different business and technical needs. These patterns are rehost (lift-and-shift), refactor (optimize), rearchitect (rebuild), replace (repurchase), and retire (decommission). Choosing the correct pattern requires evaluating the workload's specific dependencies, its required performance and uptime (SLAs), and any legal or security compliance constraints.
The selection process depends heavily on the workload's characteristics and its readiness for the cloud. For instance, a legacy application with complex dependencies but a need for a fast move might be a candidate for rehost using tools like Azure Migrate. An application needing minor code changes to better use cloud scaling features would fit the refactor pattern. A fundamentally new cloud-native design is needed for the rearchitect pattern. This mapping balances migration speed, cost, and long-term operational benefits.
A decision tree that evaluates workload characteristics to select one of the five Cloud Adoption Framework migration patterns: Retire, Replace, Rehost, Refactor, or Rearchitect.
To implement the chosen strategy, you use Azure Migrate and related services in a sequence of phases. The process begins with discovery, where tools automatically inventory servers and map their dependencies. Next, an assessment phase estimates costs and recommends target Azure services. Finally, the migration phase executes the data transfer, which often involves an initial copy, a period of resynchronization, and a final cut-over. Throughout all phases, you must enforce governance and cost controls using Azure Policy, budgets, and tagging to maintain security, compliance, and financial oversight.
Venture into the world of Azure Infrastructure, where design meets functionality. Harness your skills and gain mastery over complex cloud structures to ace the AZ-305 Designing Microsoft Azure Infrastructure Solutions exam!
Prepare and test your skills
Prepare and test your skills
The five core migration patterns are rehost (lift-and-shift), refactor (optimize), rearchitect (rebuild), replace (repurchase), and retire (decommission).
Use rehost for a legacy application with complex dependencies that needs a fast move, using tools like Azure Migrate. Use refactor when an application needs minor code changes to better use cloud scaling features.
The process begins with discovery, which inventories servers and maps dependencies, followed by an assessment phase that estimates costs and recommends target Azure services, and finally the migration phase that involves an initial copy, resynchronization, and a final cut-over. Throughout all phases, you enforce governance with Azure Policy, budgets, and tagging.
StudyCerts
StudyCerts