Merge pull request #301032 from habibaum/09Jun-faq-docs

FAQ doc updates

Author: prmerger-automator[bot]

articles/migrate/common-questions-server-migration.md

@@ -394,6 +394,30 @@ You can work out the bandwidth requirement based on:
 
 Ideally, you'd want initial replication to complete at least 3-4 days before the actual migration window. This timeline gives you sufficient time to perform a test migration before the actual window and keep downtime during the window to a minimum.
 
+## How do I roll back if something goes wrong during the migration process?
+
+Azure Migrate doesn't support rollback now, which means after users migrate, they can't go back to on-premises.
+
+## What strategies do I use to reduce downtime during migration?
+
+| **Practice** | **How it helps** | **Benefit** |
+| --- | --- | --- |
+| Use Agent-Based Replication for Continuous Sync | It continuously replicates on-premises VMs to Azure| This helps you cut over with minimal data loss (RPO of a few seconds) and reduces downtime (RTO of a few minutes). |
+| Perform Test Migrations  | Azure Migrate lets you run test migrations without affecting the production VM.  | You check boot success, network connectivity, and application functionality in Azure before the final cutover. |
+| Use Replication Groups for Dependency-Aware Migration  | You group VMs based on application or service dependencies and migrate them together. | This lowers the risk of broken dependencies during migration and helps keep services running smoothly. |
+| Schedule Cutovers During Maintenance Windows  | **: You plan the final cutover (switching users to the Azure-hosted app) during a known low-traffic period. | This minimizes the user impact and gives time for rollback if needed.|
+| Do a Phased Migration  | You migrate and modernize workloads in stages instead of all at once. | Smaller changes minimize the risk and help keep services available throughout the process. |
+
+## How do I measure the success of my cloud migration execution?
+
+| Metric  | Description |
+| --- | --- |
+| Cutover success rate | Percentage of workloads successfully migrated without rollback or issues. |
+| Downtime duration | Total unplanned downtime occurs during cutover; the goal is minimal or zero. |
+| Data integrity | Post-migration validation of data completeness and accuracy. |
+| Application functionality |Post-migration, apps work exactly as expected (functional testing, and UAT pass). |
+| Migration completion timeline | Actual vs planned migration schedule adherence. |
+
 ## Related content
 
 * Learn more about migrating [VMware VMs](tutorial-migrate-vmware.md), [Hyper-V VMs](tutorial-migrate-hyper-v.md), and [physical servers](tutorial-migrate-physical-virtual-machines.md).

articles/migrate/resources-faq.md

@@ -90,6 +90,36 @@ Learn how to [delete a project](how-to-delete-project.md).
 
 No, Azure Migrate doesn't support moving resources. To move resources created by Azure Migrate, consider creating a new project in the desired region.
 
+## What skills and expertise help manage migration effectively with Azure Migrate?
+
+Customers who want to migrate must be familiar with the Azure portal and understand basic migration concepts like the 6Rs. They also need the following technical skills, which vary depending on what they migrate: 
+
+- **Application migration**: Understand application architecture, dependencies, and code refactoring.
+- **Cloud migration**: Know Azure roles, networking, and security.
+- **Infrastructure migration**: Work with virtualization (VMware, Hyper-V), servers, storage, and backup.
+- **Scripting**: Use Bash, PowerShell, or Python to automate parts of the migration and testing.
+- **Integration**: Use APIs, middleware, and tools like MuleSoft or Boomi toto maintain interoperability.
+
+
+## What migration approaches do I have with Azure Migrate, such as rehosting, replatforming, or refactoring?
+
+Azure Migrate now offers options to create business cases and assessment reports for workloads that users want to rehost, replatform, or refactor.
+
+For actual migration execution, Azure Migrate supports rehosting (also known as lift-and-shift).
+
+For rehosting:
+
+- **Server migration**: It helps move virtual machines (VMware, Hyper-V, or physical servers).
+- **Database migration service (DMS)**: It supports migrating SQL Server and other databases.
+
+This approach works best for:
+
+- Legacy applications
+- Quick migrations with minimal testing
+- Time-sensitive lift-and-shift projects
+- Applications with complex code that still run well on Azure
+
+
 ## Next steps
 
 Read the [Azure Migrate overview](migrate-services-overview.md).