Merge pull request #307919 from MicrosoftDocs/release-migrate-enhancements

release-migrate-enhancements -> main -- 11/07 - 02:30 AM PST (11/07 04:00 PM IST)

Author: Albertyang0

articles/migrate/common-questions-wave-planning.md

@@ -0,0 +1,63 @@
+---
+title: Questions about Wave Planning in Azure Migrate
+description: Get answers to common questions about wave planning in Azure Migrate.
+author: shubhamJain1992
+ms.author: shuj
+ms.service: azure-migrate
+ms.reviewer: v-uhabiba
+ms.topic: concept-article
+ms.date: 11/04/2025
+monikerRange: migrate 
+# Customer intent: As a cloud migration specialist, this article help understand and clarify common questions about using Azure Migrate Wave Planning for migration projects.
+---
+
+
+# Wave Planning - Common questions (preview)
+
+This article answers common questions about Wave Planning in Azure Migrate. 
+
+## Is wave planning mandatory for migrations?
+
+No, wave planning isn't a mandatory to migrate with Azure Migrate. It's a guided, step-by-step process that helps you plan and execute large scale migrations on time. 
+
+## How do I ensure waves show latest data? 
+
+Create, edit, delete, and other wave operations can take time depending on the size of the wave. To see the latest data, do the following
+
+1. Ensure deployments for each operation are complete. 
+
+:::image type="content" source="./media/common-questions-wave-planning/notifications.png" alt-text="The screenshot shows the notifications." lightbox="./media/common-questions-wave-planning/notifications.png":::
+
+2. Refresh the page using the Refresh action.
+
+## Explain why can't I add an application to a wave?
+
+Each workload in a migration wave can have only unique  migration plan and be part of only one wave. If any workload of an application is part of another wave, you can add the entire application to a different wave. 
+
+Alternatively, switch to workload selection view, filter by the application name, and add the remaining workloads to the wave.  
+
+## Why does the number of workloads or apps in a wave differ from the count added to the wave?
+
+Following are the reasons why the workloads/apps selected for the wave may vary from the count, which is added to the wave:
+
+1. The workloads aren't supported in migration Waves. Unsupported workloads are omitted from the wave. Unsupported list includes: Postgre SQL.
+1. The workload is part of multiple applications. Migrating this workload moves parts of various applications, so the complete list of applications appears in the wave.
+1. The application contains an unsupported workload. This application is split into multiple workloads, and the remaining of workloads are added to the wave. 
+
+## Which migration executions are supported through Waves?
+
+There are two types of category tracking in Azure Migrate: 
+
+1. **Automated tracking**: When Azure Migrate supports the migration tool and approach (for example, Server Migration), you can perform migration and modernization tasks through Waves, and the status gets updated automatically.
+
+1. **Manually tracking**: When Azure Migrate doesn't natively support migration tooling (for example, DMS or other tools), you manually update task status (for example, select **Mark as complete**). This keeps Waves status up to date and reflects the current stage in the migration and modernization journey.
+
+## How can I export the Wave? 
+
+All Azure Migrate data, including waves, is available in Azure Resource Graph (ARG). It includes the following wave planning data:
+
+ - Wave: `microsoft.migrate/migrateprojects/waves`
+ - Workload in wave: `microsoft.migrate/migrateprojects/migrationentities`
+ - Application in wave: `microsoft.migrate/migrateprojects/migrationentitygroups`
+
+You can build queries as needed by using the Azure portal, Azure CLI, PowerShell, REST APIs, or the Power BI connector to generate reports. For more information, see [Azure Resource Graph](/azure/governance/resource-graph/overview).

articles/migrate/how-to-complete-wave-plan.md

@@ -0,0 +1,95 @@
+---
+title: High-Fidelity Azure Execution Planning for Modernization
+description: Learn how to plan Azure execution with high fidelity. Identify targets, tools, tasks, and prerequisites to ensure predictable modernization without delays.
+author: shubhamJain1992
+ms.author: shuj
+ms.service: azure-migrate
+ms.reviewer: v-uhabiba
+ms.topic: concept-article
+ms.date: 11/04/2025
+monikerRange: migrate 
+# Customer intent: Understand concepts such as migration targets, prerequisites, and wave planning. Also, plan and execute a predictable migration and modernization process using Azure Migrate.
+---
+
+# Plan high-fidelity execution for predictable migration and modernization (preview)
+
+This article explains how for creating a high-fidelity migration plan in Azure Migrate, including defining targets, configuring settings, adding tasks, and preparing prerequisites to ensure predictable migration and modernization.
+
+Creating a high-fidelity plan including all the migration details is essential for ensuring predictable migration and modernization without deviations and plans and outcomes. The primary details include:
+
+1. Azure services for hosting my applications and workloads.
+1. Tools and the approach required for migration and modernization.
+1. Activities to be performed during migration and modernization.
+1.  Timeline and prerequisites to prepare for migration.
+
+## Identify Azure migration targets before moving workloads 
+
+Before migrating workloads and applications, you should identify the Azure destination and determine the appropriate method for moving them. The assessment provides recommendations and details about migration targets in Azure.
+
+>[!Note]
+> At present, the assessment link suggests an Azure target for every workload, but specific configurations, such as storage or compute SKUs are only available for integrated server migrations.
+
+To review and update these settings in Azure Migrate Wave planning, follow these steps:
+
+1. Go to Azure Targets page and select **Configure** in the **Target Settings** tile.
+
+    :::image type="content" source="./media/wave-planning-overview/wave-overview.png" alt-text="The screenshot shows the overview of the wave planning." lightbox="./media/wave-planning-overview/wave-overview.png":::
+
+### Configure application targets and tasks
+
+Use the application target settings to link assessments and add migration tasks for your application.
+
+1. In **Target Setting** select **Link assessment** to review the link assessment. You can change assessment or link if none is currently linked.  
+
+To link an assessment to the application links the assessment to all workloads for that application across waves and reset the tasks.  
+
+:::image type="content" source="./media/how-to-complete-wave-plan/application-target-settings.png" alt-text="The screenshot shows how to select link assessment in target settings page." lightbox="./media/how-to-complete-wave-plan/application-target-settings.png"::: 
+
+2. Select **Add tasks** to add tasks that you need to perform as part of migration beyond the workload migrations. These tasks are manual, so you can add, update, and track manually.
+
+:::image type="content" source="./media/how-to-complete-wave-plan/application-tasks.png" alt-text="The screenshot shows how to select tasks that you need to perform." lightbox="./media/how-to-complete-wave-plan/application-tasks.png"::: 
+
+
+### Configure Workload Targets and migration tasks
+
+Use workload target settings to configure Azure targets, select migration tools, and add tasks for your migration plan.
+
+1. Select **Configure target** to review and configure the Azure target. The system sets the target by default when you select an assessment. 
+2. Select **None** for workloads that are planned for retirement and not to be migrated.
+3. Select the tool in **Migration tool** dropdown to define the migration path and tasks. 
+4. Select **Other** for workloads that you want to migrate outside Azure Migrate.
+   
+:::image type="content" source="./media/how-to-complete-wave-plan/workload-target-settings.png" alt-text="The screenshot shows how to review and configure." lightbox="./media/how-to-complete-wave-plan/workload-target-settings.png":::      
+ 
+5. Select **Save configuration**.
+6. Review and add tasks using **Add tasks** that need to be performed and tracked for migrations.
+7. Select **Save tasks** to save.
+    
+Refer to the [FAQ](common-questions-wave-planning.md) to learn about the supported tools and targets for the execute phase of migration and modernization.
+
+## Prepare your Wave for migration: Key prerequisites
+
+Azure Migrate identifies the prerequisites you need to complete before starting migration, based on the migration targets, tools, and tasks you define. To review and add other prerequisites for tracking and to make the wave ready for migration, do the following:
+
+1. Select **View details** in the Wave settings tile.  
+
+:::image type="content" source="./media/how-to-complete-wave-plan/wave-settings.png" alt-text="The screenshot shows how to view details in the wave settings tile." lightbox="./media/how-to-complete-wave-plan/wave-settings.png":::   
+
+2. Review the prerequisites and select **Add Task**.  
+
+:::image type="content" source="./media/how-to-complete-wave-plan/add-tasks-and-prereqs.png" alt-text="The screenshot shows how to add tasks in wave settings." lightbox="./media/how-to-complete-wave-plan/add-tasks-and-prereqs.png":::   
+
+3. Provide a description name of the task and **Description** about the task.
+4. Select **Add**, and then select **Save changes** to save the tasks as a prerequisite.
+
+The tasks appear in the Wave configuration stage of the migration and modernization journey. Complete these tasks before the Wave is ready for execution.
+
+After you identify all tasks and activities, review and update the planned start and end dates for the migration in the **Wave Settings** page.
+
+After you identify the migration and modernization activities, configure the target settings, and complete the prerequisites, the wave transitions to the **Ready for Execution** stage.
+
+You can perform the wave planning for multiple waves in a similar way.
+
+## Next steps
+
+- Learn more about [execute your wave using Azure Migrate](how-to-execute-track-waves.md).

articles/migrate/how-to-execute-track-waves.md

@@ -0,0 +1,71 @@
+---
+title: Execute and Track Waves in Azure Migrate
+description: Learn how to execute and track waves in Azure Migrate. Understand supported and manual execution flows, update statuses, and monitor migration progress efficiently.
+author: shubhamJain1992
+ms.author: shuj
+ms.service: azure-migrate
+ms.reviewer: v-uhabiba
+ms.topic: how-to
+ms.date: 11/04/2025
+monikerRange: migrate 
+# Customer intent: To understand how to execute and track migration waves in Azure Migrate, including supported and manual execution flows, and learn how to monitor migration progress and update statuses during the migration phase.
+---
+
+# Execute and track waves in Azure Migrate (preview)
+
+This article describes how to execute migration and modernization waves in Azure Migrate, including starting migration flows, performing tasks, and tracking progress for supported and unsupported workloads.
+
+This phase begins when you reach the planned start time and perform migration and modernization activities within the scheduled time window. Azure Migrate provides two types of execution and tracking flows, based on whether the workload migration from source to target is supported:
+
+1. **Azure Migrate supports execution activities**: When Azure Migrate supports execution, Wave Planning enables automated execution and tracking. You can start migration, and modernization flows through wave execution, take actions, and track statuses. For example, you can perform server migration tasks such as replication, test migration, and cutover, and monitor progress automatically.
+1. **Azure Migrate doesn't support these execution activities**: Azure Migrate doesn’t support several workload and application migration or modernization activities. In such cases, you plan and track the activities in Azure Migrate and manually update their status for centralized tracking. Execute these activities outside Azure Migrate.
+
+## Executing Waves
+
+This section explains how to execute a migration wave in Azure Migrate using the Wave Planning feature. When the wave is ready, follow these steps to execute it:
+
+1. Select **Execute wave** from **Wave Planning**.
+
+:::image type="content" source="./media/how-to-execute-track-waves/execute-waves.png" alt-text="The screenshot shows the overview of the execute wave details." lightbox="./media/how-to-execute-track-waves/execute-waves.png"::: 
+
+
+### Execute application migration tasks
+
+Use the application migration settings to review workloads, execute migration flows, and track tasks for completion.
+
+1. Select the application name. Azure Migrate groups the workload by source-to-target combinations that share a similar migration and modernization journey.
+2. For each source to target combination, select **Review and Execute**. If supported, Azure Migrate starts the execution flow for the workload.
+
+:::image type="content" source="./media/how-to-execute-track-waves/application-execute.png" alt-text="The screenshot shows the details of the application execute waves." lightbox="./media/how-to-execute-track-waves/application-execute.png"::: 
+
+3. If the application has tracked tasks, select the number under **Tasks**.
+
+:::image type="content" source="./media/how-to-execute-track-waves/application-tasks.png" alt-text="The screenshot shows the application task marked as complete." lightbox="./media/how-to-execute-track-waves/application-tasks.png"::: 
+
+4. After you complete the task out of band, select **Mark as Complete**.
+
+### Execute Workload migration flows
+
+Use workload migration settings to review source-to-target combinations, execute supported migrations, and update tasks for unsupported flows.
+
+1. For each source target combination select **Review and Execute.**  If supported, Azure Migrate starts the workload execution flow.
+1. For unsupported executions, update the tasks by selecting **View Execution Details**.    
+1. For supported executions, select **Execute** migrations for all to start the execution flow.
+  
+## Tracking wave executions
+
+Use the Migrations view in the Wave to track the migration execution of applications and workloads.
+
+:::image type="content" source="./media/how-to-execute-track-waves/workload-tracking-view.png" alt-text="The screenshot shows the workload tracking view." lightbox="./media/how-to-execute-track-waves/workload-tracking-view.png"::: 
+
+To view detailed workload status, follow the steps:
+
+1. Select **Execution Stage** and review the tasks in each migration and modernization stage. You can also perform activities and update the migration status here.
+
+:::image type="content" source="./media/how-to-execute-track-waves/workload-task-tracking-view.png" alt-text="The screenshot shows the workload task view in migration." lightbox="./media/how-to-execute-track-waves/workload-task-tracking-view.png"::: 
+    
+:::image type="content" source="./media/how-to-execute-track-waves/app-tracking-view.png" alt-text="The screenshot shows the app tracking details." lightbox="./media/how-to-execute-track-waves/app-tracking-view.png"::: 
+
+## Next steps
+
+Learn more to [Optimize work loads](/azure/cloud-adoption-framework/modernize/optimize-after-cloud-modernization).

articles/migrate/how-to-plan-create-waves.md

@@ -0,0 +1,58 @@
+---
+title: Create Migration Waves in Azure Migrate for Efficient Cloud Migration Planning
+description: Learn how to create migration waves in Azure Migrate to group workloads, sequence migrations, and reduce risk. Follow step-by-step guidance for efficient cloud migration planning.
+author: shubhamJain1992
+ms.author: shuj
+ms.service: azure-migrate
+ms.reviewer: v-uhabiba
+ms.topic: how-to
+ms.date: 11/04/2025
+monikerRange: migrate 
+# Customer intent: how to plan and execute cloud migration efficiently using Azure Migrate by creating migration waves that group workloads logically, sequence them based on priority, and optionally leverage assessments for optimized migration paths.
+---
+
+# Create waves in Azure Migrate for efficient planning (preview)
+
+This article explains how to create migration waves in Azure Migrate to group workloads, sequence migrations, and plan efficient execution for reduced risk and improved migration speed.
+
+To create migration waves, group your applications and workloads into logical sets that you can be migrated together. These groups called **waves** help you execute migrations in smaller, manageable batches, reduce risk and improving efficiency. The key planning actions include:
+
+- **Distribute workloads into waves**: Group workloads and applications that share dependencies or business. This ensures they migrate together without breaking application functionality.
+- **Sequence waves**: Prioritize waves based on factors such as business criticality, complexity, and migration impact.
+- **Parallelize where safe:** Run independent waves in parallel to accelerate migration speed without introducing risk.
+
+For more information on grouping and sequencing, see, [Azure Cloud Adoption Framework – Migration Wave Planning](/azure/cloud-adoption-framework/migrate/migration-wave-planning).
+
+## Create Waves using Azure portal
+
+To create Migration Waves manually using Azure Migrate portal, follow these steps:
+
+1. Select your project from **All Projects** in Azure portal.
+
+     :::image type="content" source="./media/how-to-plan-create-waves/project-listing-page.png" alt-text="The screenshot shows the project listing page." lightbox="./media/how-to-plan-create-waves/project-listing-page.png":::
+
+1. In **Overview** pane, select **Create Wave**
+
+    :::image type="content" source="./media/how-to-plan-create-waves/project-overview.png" alt-text="The screenshot shows the overview of the project." lightbox="./media/how-to-plan-create-waves/project-overview.png":::
+
+1. Enter a unique name in **Wave name** for execution and tracking purposes.
+1. Enter the planned start date for the wave migration in **Planned start date**.
+1. *Optional* Select an **Assessment** to get recommendations on the Azure targets and workload configurations. Use an assessment to accelerate wave planning.  
+1. Select the **Migration path** of the assessment based on your business strategy. If the assessment includes only single path, this option isn't available.
+
+     :::image type="content" source="./media/how-to-plan-create-waves/wave-create.png" alt-text="The screenshot shows how to create wave." lightbox="./media/how-to-plan-create-waves/wave-create.png":::
+
+1. Review, add, and remove workloads and applications that you want to include in the wave. You can use filters to refine the selection.  
+    If you select an assessment, the workloads and applications are limited to the scope of that assessment. You can add more workloads and applications later.
+
+8. After you finalized the wave components, select **Create Wave**.
+
+:::image type="content" source="./media/how-to-plan-create-waves/wave-create-completion.png" alt-text="The screenshot shows the completion of the wave creation." lightbox="./media/how-to-plan-create-waves/wave-create-completion.png":::
+
+In a few seconds, Azure Migrate creates the wave project. To view it, select **View Waves** in the Project overview.
+
+The created wave includes the workloads and applications you selected. If you selected an assessment, the workloads and applications default to the migration targets and configurations defined in that assessment.
+
+## Next steps
+
+Learn more about [complete your wave planning in Azure Migrate](how-to-complete-wave-plan.md).