Azure Solutions Architecture · AZ-305 · Networking & Business Continuity · by Raushan Ranjan, MCT
Moving workloads to the cloud requires a strategic and methodical approach. A solution architect uses the Cloud Adoption Framework (CAF) and a suite of Azure services to ensure the migration is successful, secure, and cost-effective.
1. Evaluate Migration with the Cloud Adoption Framework
The Cloud Adoption Framework (CAF) provides a proven, six-step process for a successful cloud journey. The "Migrate" methodology is a key part of this framework.
- Assess: This is the first and most critical phase. You evaluate your on-premises environment to understand your workloads, their dependencies, and their performance requirements. The goal is to determine what you're going to migrate, what it will cost, and how you will do it.
- Migrate: This phase is where the actual migration happens. You execute the plan by using the right tools to move your applications, data, and infrastructure to Azure.
- Optimize: Once the migration is complete, you refine and improve your migrated workloads to take full advantage of cloud benefits. This includes rightsizing VMs, optimizing costs, and improving security.
2. The Azure Migration Framework & Tools
The Azure Migration Framework is the practical implementation of the CAF's Migrate methodology, and Azure Migrate is the central tool that brings it all together. Think of Azure Migrate as a unified hub for all your migration activities.
Assess your Workloads
You start here. To assess your workloads, you deploy a lightweight Azure Migrate appliance on-premises. This appliance discovers and collects data on your servers, databases, and web apps. It then analyzes this data to:
- Identify dependencies between servers so you know what to migrate together.
- Determine the Azure readiness of your workloads (can they be moved as-is?).
- Provide cost estimates for running your workloads in Azure.
- Recommend the right-sized Azure VMs and services.
Compare Migration Tools
Azure offers a variety of migration tools, and the best choice depends on the workload.
IaaS (Virtual Machines)
- For a "lift-and-shift" migration of servers, you use Azure Migrate: Server Migration. It replicates the on-premises VM to Azure with minimal downtime.
Databases
- For databases, you have two options:
- Azure Database Migration Service (DMS): This is a managed service for migrating databases to Azure with minimal downtime. It can migrate a wide variety of database types (e.g., SQL Server, Oracle, MySQL).
- Azure Data Studio with the Azure SQL Migration extension: This is an integrated tool for modernizing and migrating SQL Server databases. It provides assessment, recommendations, and the ability to migrate to Azure SQL Database or Azure SQL Managed Instance.
Storage Migration
Migrating data is a key part of any project. The choice of tool depends on the amount of data and network bandwidth.
Online Tools
These tools use your network to transfer data. They're best for smaller datasets or scenarios where you have a fast, reliable network connection.
- AzCopy: A command-line tool for high-performance data copying to and from Azure Storage.
- Azure Storage Mover: A fully managed service for migrating file shares and objects from on-premises or other clouds to Azure.
Offline Tools
These tools are for very large datasets (terabytes to petabytes) where using the network is too slow or costly.
- Azure Data Box: This is a family of physical devices you rent from Microsoft. You load your data onto the device at your on-premises location and then ship it back to Azure for upload to your storage account. It's much faster than an online transfer for massive amounts of data.
When a solution architect designs a migration solution, they're not just moving things from one place to another; they are using the opportunity to modernize, optimize, and secure the infrastructure. This is where all the services from the modules you listed come together.
1. Migration Strategy: The Starting Point
Before any technical work begins, a solution architect must define the migration strategy. This involves a thorough assessment of the current environment to understand dependencies, identify workloads, and estimate costs.
Azure Migrate: This is the primary service for the entire migration journey. It's a free, unified hub that provides tools to discover and assess on-premises resources, including servers, databases, and web apps. It can identify interdependencies between servers, analyze performance, and recommend the right-sized Azure VMs and databases for your workloads, which is crucial for cost optimization.
The 6 Rs: A common framework for migration strategy is the "6 Rs." A solution architect decides the fate of each application:
- Rehost (Lift and Shift): Migrate with minimal changes, often to Azure VMs.
- Replatform (Lift and Optimize): Make minor cloud-native changes, like moving a database to Azure SQL Managed Instance.
- Rearchitect/Refactor: Redesign the application to take full advantage of cloud-native services like Azure Functions or microservices.
- Repurchase: Replace an existing application with a SaaS solution.
- Retain: Keep the application on-premises.
- Retire: Decommission the application.
2. Technical Migration Process
Once the strategy is set, the architect chooses the right tools and services for the actual migration.
IaaS Migration (VMs & Files)
- Azure Migrate: Server Migration: For migrating on-premises VMs to Azure. It replicates the VMs with minimal downtime and provides a test migration feature to ensure everything works before the final cutover.
- Data Box: For very large data migrations (terabytes to petabytes) where network bandwidth is a bottleneck. This is a physical device you load with data on-premises and then ship to Microsoft for direct upload to Azure storage.
Database Migration
- Azure Database Migration Service (DMS): This is a fully managed service for migrating databases to Azure. It supports both online (minimal downtime) and offline migrations. It works with various database engines like SQL Server, MySQL, PostgreSQL, and Oracle. DMS automates the migration process and provides a consolidated view of the progress.
Data Integration and Storage
- Azure Data Factory: For migrating large datasets between different data stores and for orchestrating data transformation pipelines.
- Azure Blob Storage: A target for unstructured data like documents, backups, and images. Data from on-premises file shares can be migrated here.
- Azure Files: For migrating on-premises file shares that need to retain the SMB protocol and be accessible to Azure VMs.
3. Post-Migration Optimization & Modernization
Migration isn't the end of the journey. A solution architect must ensure the migrated workloads are secure, cost-effective, and performant.
Connecting the Dots: A Hollistic View
- Governance & Security: After migrating, the architect applies the security controls designed in the governance and authentication/authorization modules. This includes using Azure Policy to enforce compliance, Azure Firewall for network security, and Entra ID to manage access to the migrated resources.
- Networking: The migrated VMs and services are integrated into the pre-designed hub-and-spoke network topology, allowing them to communicate with other resources and on-premises networks securely.
- Business Continuity: An architect must immediately implement the business continuity solution. They'll configure Azure Backup for the new VMs and databases and set up Azure Site Recovery to protect mission-critical applications by replicating them to a different region.
- Logging & Monitoring: Post-migration, Azure Monitor and Log Analytics are configured to track performance, identify issues, and ensure the migrated workloads are running optimally. This is a crucial step for the ongoing operation of the solution.
By integrating these services, a solution architect can execute a migration that is not just a lift and shift, but a strategic move that sets the business up for long-term success in the cloud.