Merge pull request #8197 from MicrosoftDocs/users/chcomley/uuf-475727

UUF fix Migration docs

Author: prmerger-automator[bot]

docs/migrate/migration-get-started.md

@@ -8,7 +8,7 @@ ai-usage: ai-assisted
 ms.author: chcomley
 author: chcomley
 monikerRange: '<= azure-devops'
-ms.date: 05/20/2024
+ms.date: 08/07/2025
 ---
 
 # Get started with Azure DevOps Data Migration Tool
@@ -58,7 +58,27 @@ When you migrate a team project collection SQL database, the Data Migration Tool
 
 ## Choose data center 
 
-When you set up your Azure DevOps Services organization, you can choose the location for your data. During initial sign-up and organization creation, select a region that suits your needs. To use later for migration, make a note of the region’s shorthand code. For more information, see Supported regions for migration. 
+When you set up your Azure DevOps Services organization, you can choose the location for your data. During initial sign-up and organization creation, select a region that suits your needs. To use later for migration, make a note of the region's shorthand code.
+
+> [!IMPORTANT]
+> Not all Azure regions support the Data Migration Tool. Setting up temporary SQL VMs or other migration infrastructure in unsupported regions can cause delays and require reconfiguration. Review the supported regions before proceeding with your migration planning.
+
+### Supported Azure regions for migration
+
+The following table lists the Azure regions that support the Azure DevOps Data Migration Tool:
+
+| Region | Shorthand code |
+|--------|----------------|
+| Central US | CUS |
+| East US 2 | EUS2 |
+| West Europe | WE |
+| Australia East | AE |
+| Brazil South | BS |
+| South India | SI |
+| Asia Pacific (Hong Kong) | APE |
+| Canada Central | CC |
+
+For the complete migration process and detailed region considerations, see [Supported Azure regions for migration](migration-test-run.md#supported-azure-regions-for-migration).
 
 ## Understand pricing 
 

docs/migrate/migration-overview.md

@@ -7,7 +7,7 @@ ms.contentid: 3d6edd06-ceed-43b4-9e77-4a121864594c
 ms.author: chcomley
 author: chcomley
 monikerRange: '<= azure-devops'
-ms.date: 02/18/2025
+ms.date: 08/07/2025
 ---
 
 # Migration overview 
@@ -51,25 +51,23 @@ Before you initiate the migration process, the tools can perform a premigration
 
 ## Migration Tool limitations
 
-The tool allows you to "lift and shift" one Azure DevOps Server Collection to one new Azure DevOps Service Organization, with no modifications for the following reasons: 
-
-- Data integrity and consistency: 
-  - When you migrate data, maintaining integrity and consistency is crucial. Allowing modifications during migration could lead to data corruption or inconsistencies. 
-  - The tool ensures that data remains intact during the transfer process, minimizing the risk of errors. 
-- Source data preservation: 
-  - The migration tool aims to faithfully replicate the source data in the target environment. 
-  - Modifications could alter the original data, potentially causing discrepancies between the migrated data and the source data. 
-- Predictable behavior: 
-  - By restricting modifications, the tool ensures predictable behavior during migration. 
-  - Users can rely on consistent results without unexpected changes. 
-- Migration focus, not transformation: 
-  - The primary purpose of the migration tool is to move data from one location to another. 
-  - Data transformation, such as modifying values, typically gets handled separately after migration.
-- Supported migration scenarios:
-  - Moving projects from one Azure DevOps Services organization to another Azure DevOps Services organization isn't currently supported.
-  - Migrating from one Azure DevOps Server instance to another isn't supported. 
-
-You can purge data that you don’t need before or after the migration. 
+The tool allows you to "lift and shift" one Azure DevOps Server Collection to one new Azure DevOps Services Organization, with no modifications for the following reasons:
+
+### Why no modifications are allowed
+
+- **Data integrity and consistency**: Modifications during migration could lead to data corruption or inconsistencies.
+- **Source data preservation**: The tool faithfully replicates source data without alterations that could cause discrepancies.
+- **Predictable behavior**: Restricting modifications ensures consistent, reliable migration results.
+- **Migration focus, not transformation**: The tool moves data; transformation happens separately after migration.
+
+### Unsupported migration scenarios
+
+- Moving projects from one Azure DevOps Services organization to another Azure DevOps Services organization
+- Migrating from one Azure DevOps Server instance to another Azure DevOps Server instance
+
+### Regional limitations
+
+The Data Migration Tool is only supported in specific Azure regions. Organizations must be created in supported regions, and any temporary infrastructure (such as SQL VMs for large migrations) must also be deployed in these regions. See [Supported regions for migration](migration-get-started.md#supported-azure-regions-for-migration) for the complete list.
 
 ## Migration Tool process
 
@@ -81,9 +79,12 @@ You can purge data that you don’t need before or after the migration.
 1. Carry out a migration. 
 1. Confirm that your users and data got migrated, and the collection is functioning as expected.
 
+> [!TIP]
+> You can purge data that you don't need before or after the migration to reduce migration time and storage requirements.
+
 ## Option 3: API-based migration
 
-If you can't use the Data Migration Tool but still want a higher fidelity migration than [Option 2](#option-2-azure-devops-data-migration-tool), consider using various tools that leverage public APIs to move data. These tools include extensions available at the [Visual Studio Marketplace](https://marketplace.visualstudio.com/azuredevops).
+If you can't use the Data Migration Tool but still want a higher fidelity migration than [Option 2](#option-2-azure-devops-data-migration-tool), consider using various tools that use public APIs to move data. These tools include extensions available at the [Visual Studio Marketplace](https://marketplace.visualstudio.com/azuredevops).
 
 ## API-based migration limitations