Contoso migration series
We have a series of articles that demonstrate how the fictitious organization Contoso migrates its on-premises infrastructure to the Microsoft Azure cloud.
The series includes scenarios that illustrate how to set up an infrastructure migration, and how to run different types of migrations. Scenarios grow in complexity as they progress. The articles show how the Contoso company handles migration, but general instructions and pointers are provided throughout.
The articles in the series are summarized in the table below.
- Each migration scenario is driven by slightly different business requirements, that determine the migration strategy.
- For each deployment scenario, we provide information about business drivers and goals, a proposed architecture, steps to perform the migration, and recommendations for cleanup and next steps after migration is complete.
|Article 1: Overview||Overview of the article series, Contoso's migration strategy, and the sample apps that are used in the series.|
|Article 2: Deploy Azure infrastructure||Contoso prepares its on-premises infrastructure, and Azure infrastructure for migration. The same infrastructure is used for all articles in the series.|
|Article 3: Assess on-premises resources for migration to Azure||Contoso runs an assessment of its on-premises SmartHotel360 app running on VMware. Contoso assesses app VMs using the Azure Migrate service, and the app SQL Server database using Data Migration Assistant.|
|Article 4: Rehost an app on an Azure VM and SQL Database Managed Instance||Contoso runs a lift-and-shift migration to Azure for its on-premises SmartHotel360 app. Contoso migrates the app front-end VM using Azure Migrate. Contoso migrates the app database to an Azure SQL Database Managed Instance, using the Azure Database Migration Service.|
|Article 5: Rehost an app on Azure VMs||Contoso migrates its SmartHotel360 app VMs to Azure VMs using the Azure Migrate service.|
|Article 6: Rehost an app on Azure VMs and in a SQL Server AlwaysOn availability group||Contoso migrates the SmartHotel360 app. Contoso uses Azure Migrate to migrate the app VMs. It uses the Database Migration Service to migrate the app database to a SQL Server cluster that's protected by an AlwaysOn availability group.|
|Article 7: Rehost a Linux app on Azure VMs||Contoso completes a lift-and-shift migration of its Linux osTicket app to Azure VMs, using Azure Migrate.|
|Article 8: Rehost a Linux app on Azure VMs and Azure Database for MySQL||Contoso migrates its Linux osTicket app to Azure VMs using Azure Migrate. It migrates the app database to Azure Database for MySQ, using Azure Database Migration Service (includes an alternative option using MySQL Workbench).|
|Article 9: Refactor an app in an Azure web app and Azure SQL Database||Contoso migrates its SmartHotel360 app to an Azure web app, and migrates the app database to an Azure SQL Server instance, using the Azure Database Migration Service.|
|Article 10: Refactor a Windows app using Azure App Services and SQL Managed Instance||Contoso migrates an on-premises Windows-based app to an Azure web app, and migrates the app database to an Azure SQL Managed Instance, using the Azure Database Migration Service.|
|Article 11: Refactor a Linux app in an Azure web app and Azure Database for MySQL||Contoso migrates its Linux osTicket app to an Azure web app in multiple Azure regions, using Azure Traffic Manager, integrated with GitHub for continuous delivery. Contoso migrates the app database to an Azure Database for MySQL instance.|
|Article 12: Refactor Team Foundation Server on Azure DevOps Services||Contoso migrates its on-premises Team Foundation Server deployment to Azure DevOps Services in Azure.|
|Article 13: Rebuild an app in Azure||Contoso rebuilds its SmartHotel app using a range of Azure capabilities and services, including Azure App Service, Azure Kubernetes Service (AKS), Azure Functions, Azure Cognitive Services, and Azure Cosmos DB.|
|Article 14: Scale a migration to Azure||After trying out migration combinations, Contoso prepares to scale to a full migration to Azure.|