Merge pull request #48247 from wwlpublish/d0c2a6de86f0d93562d0f1cbad7f1f9764d6667680cb26cfe4f71de0a78c4021-live

Stacyrch140 · web-flow · commit 485978550e65 · 2025-03-10T11:19:20.000-04:00
Modules/M04-design-migrations
diff --git a/learn-pr/wwl-azure/design-migrations/1-introduction.yml b/learn-pr/wwl-azure/design-migrations/1-introduction.yml
@@ -2,9 +2,11 @@
 uid: learn.wwl.design-migrations.introduction
 title: Introduction
 metadata:
+  adobe-target: true
+  prefetch-feature-rollout: true
   title: Introduction
   description: "Introduction"
-  ms.date: 12/09/2024
+  ms.date: 03/10/2025
   author: wwlpublish
   ms.author: cynthist
   ms.topic: unit
diff --git a/learn-pr/wwl-azure/design-migrations/10-summary-resources.yml b/learn-pr/wwl-azure/design-migrations/10-summary-resources.yml
@@ -2,9 +2,11 @@
 uid: learn.wwl.design-migrations.summary-resources
 title: Summary and resources
 metadata:
+  adobe-target: true
+  prefetch-feature-rollout: true
   title: Summary and resources
   description: "Summary and resources"
-  ms.date: 12/09/2024
+  ms.date: 03/10/2025
   author: wwlpublish
   ms.author: cynthist
   ms.topic: unit
diff --git a/learn-pr/wwl-azure/design-migrations/2-evaluate-migration-cloud-adoption-framework.yml b/learn-pr/wwl-azure/design-migrations/2-evaluate-migration-cloud-adoption-framework.yml
@@ -2,9 +2,11 @@
 uid: learn.wwl.design-migrations.evaluate-migration-cloud-adoption-framework
 title: Evaluate migration with the Cloud Adoption Framework
 metadata:
+  adobe-target: true
+  prefetch-feature-rollout: true
   title: Evaluate migration with the Cloud Adoption Framework
   description: "Evaluate migration with the Cloud Adoption Framework"
-  ms.date: 12/09/2024
+  ms.date: 03/10/2025
   author: wwlpublish
   ms.author: cynthist
   ms.topic: unit
diff --git a/learn-pr/wwl-azure/design-migrations/3-describe-azure-migration-framework.yml b/learn-pr/wwl-azure/design-migrations/3-describe-azure-migration-framework.yml
@@ -2,9 +2,11 @@
 uid: learn.wwl.design-migrations.describe-azure-migration-framework
 title: Describe the Azure migration framework
 metadata:
+  adobe-target: true
+  prefetch-feature-rollout: true
   title: Describe the Azure migration framework
   description: "Describe the Azure migration framework"
-  ms.date: 12/09/2024
+  ms.date: 03/10/2025
   author: wwlpublish
   ms.author: cynthist
   ms.topic: unit
diff --git a/learn-pr/wwl-azure/design-migrations/4-assess-your-premises-workloads.yml b/learn-pr/wwl-azure/design-migrations/4-assess-your-premises-workloads.yml
@@ -2,9 +2,11 @@
 uid: learn.wwl.design-migrations.assess-your-premises-workloads
 title: Assess your on-premises workloads
 metadata:
+  adobe-target: true
+  prefetch-feature-rollout: true
   title: Assess your on-premises workloads
   description: "Assess your on-premises workloads with Service Map, Azure TCO Calculator, and Azure Migrate Server Assessment."
-  ms.date: 12/09/2024
+  ms.date: 03/10/2025
   author: wwlpublish
   ms.author: cynthist
   ms.topic: unit
diff --git a/learn-pr/wwl-azure/design-migrations/5-select-migration-tool.yml b/learn-pr/wwl-azure/design-migrations/5-select-migration-tool.yml
@@ -2,9 +2,11 @@
 uid: learn.wwl.design-migrations.select-migration-tool
 title: Select a migration tool
 metadata:
+  adobe-target: true
+  prefetch-feature-rollout: true
   title: Select a migration tool
   description: "Select a migration tool and examine Azure Migrate for migration and Azure Resource Mover."
-  ms.date: 12/09/2024
+  ms.date: 03/10/2025
   author: wwlpublish
   ms.author: cynthist
   ms.topic: unit
diff --git a/learn-pr/wwl-azure/design-migrations/6-migrate-your-databases.yml b/learn-pr/wwl-azure/design-migrations/6-migrate-your-databases.yml
@@ -2,9 +2,11 @@
 uid: learn.wwl.design-migrations.migrate-your-databases
 title: Migrate your structured data in databases
 metadata:
+  adobe-target: true
+  prefetch-feature-rollout: true
   title: Migrate your structured data in databases
   description: "Migrate your structured data in databases with the Azure Database Migration Service and SQL Server Data Migration Assistant (DMA)."
-  ms.date: 12/09/2024
+  ms.date: 03/10/2025
   author: wwlpublish
   ms.author: cynthist
   ms.topic: unit
diff --git a/learn-pr/wwl-azure/design-migrations/7-select-online-storage-migration-tool.yml b/learn-pr/wwl-azure/design-migrations/7-select-online-storage-migration-tool.yml
@@ -2,9 +2,11 @@
 uid: learn.wwl.design-migrations.select-online-storage-migration-tool
 title: Select an online storage migration tool for unstructured data
 metadata:
+  adobe-target: true
+  prefetch-feature-rollout: true
   title: Select an online storage migration tool for unstructured data
   description: "Select an online storage migration tool to move unstructured data."
-  ms.date: 12/09/2024
+  ms.date: 03/10/2025
   author: wwlpublish
   ms.author: cynthist
   ms.topic: unit
diff --git a/learn-pr/wwl-azure/design-migrations/8-migrate-offline-data.yml b/learn-pr/wwl-azure/design-migrations/8-migrate-offline-data.yml
@@ -2,9 +2,11 @@
 uid: learn.wwl.design-migrations.migrate-offline-data
 title: Migrate offline data
 metadata:
+  adobe-target: true
+  prefetch-feature-rollout: true
   title: Migrate offline data
   description: "Migrate offline data with Azure Import/Export and Azure Data Box."
-  ms.date: 12/09/2024
+  ms.date: 03/10/2025
   author: wwlpublish
   ms.author: cynthist
   ms.topic: unit
diff --git a/learn-pr/wwl-azure/design-migrations/9-knowledge-check.yml b/learn-pr/wwl-azure/design-migrations/9-knowledge-check.yml
@@ -2,9 +2,11 @@
 uid: learn.wwl.design-migrations.knowledge-check
 title: Knowledge check
 metadata:
+  adobe-target: true
+  prefetch-feature-rollout: true
   title: Knowledge check
   description: "Knowledge check"
-  ms.date: 12/09/2024
+  ms.date: 03/10/2025
   author: wwlpublish
   ms.author: cynthist
   ms.topic: unit
diff --git a/learn-pr/wwl-azure/design-migrations/includes/2-evaluate-migration-cloud-adoption-framework.md b/learn-pr/wwl-azure/design-migrations/includes/2-evaluate-migration-cloud-adoption-framework.md
@@ -12,8 +12,6 @@ Tailwind Traders shouldn't undertake cloud adoption without considerable plannin
 
 - [The One Migrate approach to migrating the IT portfolio](/azure/cloud-adoption-framework/scenarios?azure-portal=true). Examine the scenarios captured in the migrate methodology. The examples demonstrate the same set of consistent guidelines and processes for migrating both Microsoft and third-party technologies.
 
-- [Azure cloud migration best practices checklist](/azure/cloud-adoption-framework/migrate/azure-best-practices?azure-portal=true). Follow this document to learn how best to address common migration needs through the application of consistent best practices.
-
 - [The Cloud Adoption Framework migration model](/azure/cloud-adoption-framework/migrate/migration-considerations?azure-portal=true). Explore this document to understand migration and why the process can be an intensive activity. As you increase your migration effort, review these process improvements to help optimize aspects of your migration.
 
 ### Things to consider when implementing migration adoption
diff --git a/learn-pr/wwl-azure/design-migrations/includes/4-assess-your-premises-workloads.md b/learn-pr/wwl-azure/design-migrations/includes/4-assess-your-premises-workloads.md
@@ -22,10 +22,11 @@ Let's examine three Azure services and tools to support the assessment stage of
 - Azure TCO Calculator
 - Azure Migrate
 
-
-
 ## Service Map
 
+> [!Note]
+>  Service Map will be retired on 30 September 2025. Be sure to migrate to VM insights before this date to continue monitoring processes and dependencies for your virtual machines.
+
 The Service Map feature of Azure Monitor lets you automatically discover applications and their components in your on-premises environment. Use the feature to gain valuable insights into the app structure at Tailwind Traders to effectively plan and perform your migration. Service Map supports discovery on both Windows and Linux platforms.
 
 You can use Service Map to review the Tailwind Traders server environment as a collection of interconnected systems. Service Map displays the environment details in several formats:
diff --git a/learn-pr/wwl-azure/design-migrations/includes/6-migrate-your-databases.md b/learn-pr/wwl-azure/design-migrations/includes/6-migrate-your-databases.md
@@ -2,66 +2,38 @@ Most applications use a database to store the data used by the application. For
 
 ## Azure Database Migration Service
 
-The Azure Database Migration Service is part of Azure Migrate. You can use the Database Migration Service to migrate your on-premises databases, including:
+The [Azure Database Migration Service](/azure/dms/dms-overview) is part of Azure Migrate. Supported scenarios include:
 
-- Azure virtual machines running SQL Server
-- Azure SQL Database (Database Migration Assistant)
+- Azure SQL Database
 - Azure SQL Managed Instance
-- Azure Cosmos DB
-- Azure Database for MySQL
-- Azure Database for PostgreSQL
+- Azure SQL VM
+- Azure Cosmos DB 
+- Azure Database for MySQL 
+- Azure Database for PostgreSQL 
 
 ### Things to know about the Database Migration Service
 
-The Azure Database Migration Service is a fully managed service. The service provides two ways to migrate structured data in SQL Server databases:
+Azure Database Migration Service is a fully managed service. The service enables seamless migrations from multiple database sources to Azure data platforms. You can migrate your databases offline or while they're online.
 
-- **Online migration**: An online migration uses a continuous synchronization of live data, which allows a cut over to the Azure replica database at any time. Online migration minimizes downtime. 
-
-- **Offline migration**: An offline migration requires shutting down the server at the start of the migration, which results in downtime for the service.
-
-#### Migrating data in databases
+- **Offline migration**: An offline migration requires shutting down the server at the start of the migration. Use online migration if you can't afford application downtime. 
 
-When you begin a migration of structured data with the Database Migration Service, [SQL Server Data Migration Assistant (DMA)](/sql/dma/dma-overview?azure-portal=true) guides you through the process. This process consists of three primary steps:
-
-1. **Assess databases**: DMA helps you assess the databases you want to migrate.
+- **Online migration**: An online migration uses a continuous synchronization of live data, which allows a cut over to the Azure replica database at any time. Online migration minimizes downtime. 
 
-1. **Migrate schema**: DMA separates the schema from your databases. The schema is then recreated in the target Azure SQL Database instances.
+Not all migration scenarios have both offline and online capabilities. 
 
-1. **Migrate data and verify**: DMA copies the data in your databases to the target instances and then verifies the migrated databases.
+| Migration scenario | Migration mode |
+| --- | --- |
+| SQL Server to Azure SQL Managed Instance	| Online or Offline | 
+| SQL Server to SQL Server on Azure Virtual Machine	| Online or Offline |
+| SQL Server to Azure SQL Database | Offline |
 
 ### Things to consider when using the Database Migration Service
 
-Let's examine how to use the Database Migration Service to migrate your databases to Azure and the cloud.
-
-#### Prerequisites
-
-For both online and offline migrations, you need to complete the following prerequisite tasks:
-
-- Download DMA.
-- Create an Azure Virtual Network instance.
-- Configure network security groups (NSGs).
-- Configure Azure Firewall.
-- Configure credentials.
-- Provision your target database in Azure (size the target database appropriately for the migrated workload).
-
-#### Step 1: Assess on-premises databases
-
-After you verify all prerequisites are met, you're ready to begin the migration. The first step is to assess your on-premises environment with DMA.
-
-The assessment generates a report with recommendations and alternate approaches for the migration. Review the report for compatibility issues between the source and destination databases that might cause the migration to fail. Address any issues, and then generate a new assessment report. Repeat this process until you confirm all issues are addressed.
-
-#### Step 2: Migrate schema with DMA
-
-Each database has a schema that represents its entire structure. The schema defines the rules for how the structured data is organized and the relationships between data elements. You migrate the schema before you migrate all the data in your database. By migrating the schema first, you accomplish two goals:
-
-- An empty structure is created on the new Azure SQL database. This structure matches the structure of the on-premises source database.
-
-- Connectivity is validated before you run the full data migration. DMA creates and runs a script to take the required actions.
-
-When the script completes, check the target server to make sure the database is configured correctly.
-
-#### Step 3: Migrate data and verify
-
-After you complete your assessment and migrate your schema, you can migrate the structured data with the Database Migration Service.
+When selecting a database migration solution, determine which features are important to you.
 
-When all migration steps are complete, your schema and structured data are migrated to the Azure SQL Database instance. You can then safely shut down and decommission your on-premises databases and servers.
+- Do you need an assessment to identify compatibility issues?
+- Do you need a SKU recommendation?
+- Do you need to migrate database logins and schemas?
+- Do you need to automate the process?
+- Do you have a specific product scenario?
+- Do you need to integrate with other migration tools?
diff --git a/learn-pr/wwl-azure/design-migrations/includes/9-knowledge-check.md b/learn-pr/wwl-azure/design-migrations/includes/9-knowledge-check.md
@@ -1,5 +1,6 @@
 
 
+
 Tailwind Traders is assessing their migration to Azure. You're asked to make recommendations and provide input to meet the system requirements.
 
 - **Large data transfers.** Large amounts of data need to be transferred between on-premises storage and an Azure storage account. There's a concern the transfer might monopolize network bandwidth. The executive committee requests an approach where Microsoft handles the shipping and logistics. 
diff --git a/learn-pr/wwl-azure/design-migrations/index.yml b/learn-pr/wwl-azure/design-migrations/index.yml
@@ -1,9 +1,11 @@
 ### YamlMime:Module
 uid: learn.wwl.design-migrations
 metadata:
+  adobe-target: true
+  prefetch-feature-rollout: true
   title: Design migrations
   description: "Azure Architect's design and recommend migration solutions."
-  ms.date: 12/09/2024
+  ms.date: 03/10/2025
   author: wwlpublish
   ms.author: cynthist
   ms.topic: module
