Merge pull request #291207 from v-sreedevank/29Nov-DateUpdate

v-ccolin · web-flow · commit 2f2e8190c838 · 2024-11-29T15:39:15.000Z
Date update - Till Scale
diff --git a/articles/migrate/hyper-v-migration-architecture.md b/articles/migrate/hyper-v-migration-architecture.md
@@ -6,8 +6,8 @@ ms.author: vibansa
 ms.manager: abhemraj
 ms.topic: conceptual
 ms.service: azure-migrate
-ms.date: 12/12/2022
-ms.custom: engagement-fy23
+ms.date: 06/30/2023
+ms.custom: engagement-fy25
 ---
 
 
diff --git a/articles/migrate/least-privilege-credentials.md b/articles/migrate/least-privilege-credentials.md
@@ -6,8 +6,8 @@ ms.author: ajaypar
 ms.manager: roopesh.nair
 ms.topic: how-to
 ms.service: azure-migrate
-ms.date: 08/02/2023
-ms.custom: engagement-fy23
+ms.date: 11/16/2023
+ms.custom: engagement-fy25
 ---
 
 # Provision custom accounts with least privileges for SQL Discovery and Assessment
diff --git a/articles/migrate/migrate-appliance.md b/articles/migrate/migrate-appliance.md
@@ -6,8 +6,8 @@ ms.author: vibansa
 ms.manager: abhemraj
 ms.topic: conceptual
 ms.service: azure-migrate
-ms.date: 10/23/2023
-ms.custom: engagement-fy24
+ms.date: 03/20/2024
+ms.custom: engagement-fy25
 ---
 
  
diff --git a/articles/migrate/migrate-replication-appliance.md b/articles/migrate/migrate-replication-appliance.md
@@ -6,8 +6,8 @@ ms.author: piyushdhore
 ms.manager: vijain
 ms.topic: conceptual
 ms.service: azure-migrate
-ms.date: 08/29/2023
-ms.custom: engagement-fy23
+ms.date: 09/26/2024
+ms.custom: engagement-fy25
 ---
 
 
diff --git a/articles/migrate/migrate-servers-to-azure-using-private-link.md b/articles/migrate/migrate-servers-to-azure-using-private-link.md
@@ -6,8 +6,8 @@ ms.author: vijain
 zone_pivot_groups: migrate-agentlessvmware-hyperv-agentbased
 ms.topic: how-to
 ms.service: azure-migrate
-ms.date: 12/14/2022
-ms.custom: engagement-fy23
+ms.date: 11/11/2024
+ms.custom: engagement-fy25
 ---
 
 # Migrate servers to Azure using Private Link
diff --git a/articles/migrate/migrate-support-matrix-hyper-v-migration.md b/articles/migrate/migrate-support-matrix-hyper-v-migration.md
@@ -6,7 +6,7 @@ ms.author: vibansa
 ms.manager: abhemraj
 ms.topic: conceptual
 ms.service: azure-migrate
-ms.date: 03/18/2024
+ms.date: 10/16/2024
 ms.custom: engagement-fy24
 ---
 
diff --git a/articles/migrate/migrate-support-matrix-physical-migration.md b/articles/migrate/migrate-support-matrix-physical-migration.md
@@ -6,8 +6,8 @@ ms.author: vijain
 ms.manager: kmadnani
 ms.topic: conceptual
 ms.service: azure-migrate
-ms.date: 06/18/2024
-ms.custom: engagement-fy24
+ms.date: 09/26/2024
+ms.custom: engagement-fy25
 ---
 
 # Support matrix for migration of physical servers, AWS VMs, and GCP VMs
diff --git a/articles/migrate/migrate-support-matrix.md b/articles/migrate/migrate-support-matrix.md
@@ -5,8 +5,8 @@ author: v-sreedevank
 ms.author: v-sreedevank
 ms.manager: abhemraj
 ms.topic: conceptual
-ms.date: 05/22/2024
-ms.custom: engagement-fy24
+ms.date: 08/08/2024
+ms.custom: engagement-fy25
 ---
 
 # Azure Migrate support matrix
diff --git a/articles/migrate/onboard-to-azure-arc-with-azure-migrate.md b/articles/migrate/onboard-to-azure-arc-with-azure-migrate.md
@@ -4,9 +4,9 @@ description: Onboard on-premises servers in VMware virtual environment to Azure
 author: vijain
 ms.author: vijain
 ms.topic: how-to
-ms.date: 01/31/2023
+ms.date: 09/18/2024
 ms.service: azure-migrate
-ms.custom: engagement-fy23
+ms.custom: engagement-fy25
 ---
 
 # Onboard on-premises servers in VMware virtual environment to Azure Arc   
diff --git a/articles/migrate/prepare-for-migration.md b/articles/migrate/prepare-for-migration.md
@@ -6,7 +6,7 @@ ms.author: sunishvohra
 ms.manager: vijain
 ms.service: azure-migrate
 ms.topic: how-to
-ms.date: 08/23/2024
+ms.date: 10/25/2024
 ms.custom: engagement-fy25
 ---
 
diff --git a/articles/migrate/prepare-windows-server-2003-migration.md b/articles/migrate/prepare-windows-server-2003-migration.md
@@ -6,8 +6,8 @@ ms.author: vijain
 ms.manager: kmadnani
 ms.topic: how-to
 ms.service: azure-migrate
-ms.date: 12/12/2022
-ms.custom: engagement-fy23
+ms.date: 06/30/2023
+ms.custom: engagement-fy25
 ---
 
 
diff --git a/articles/migrate/replicate-using-expressroute.md b/articles/migrate/replicate-using-expressroute.md
@@ -5,8 +5,8 @@ author: vijain
 ms.author: vijain
 ms.topic: how-to
 ms.service: azure-migrate
-ms.date: 11/17/2023
-ms.custom: engagement-fy23
+ms.date: 09/26/2024
+ms.custom: engagement-fy25
 ---
 
 # Replicate data over ExpressRoute for Azure Migrate projects with public endpoint connectivity
diff --git a/articles/migrate/resources-faq.md b/articles/migrate/resources-faq.md
@@ -4,8 +4,8 @@ description: Get answers to common questions about the Azure Migrate service.
 author: v-sreedevank
 ms.author: v-sreedevank
 ms.topic: faq
-ms.date: 05/22/2024
-ms.custom: engagement-fy23
+ms.date: 06/20/2024
+ms.custom: engagement-fy25
 ---
 
 # Azure Migrate: Common questions
diff --git a/articles/migrate/scale-hyper-v-assessment.md b/articles/migrate/scale-hyper-v-assessment.md
@@ -6,7 +6,7 @@ ms.author: rajosh
 ms.manager: abhemraj
 ms.service: azure-migrate
 ms.topic: how-to
-ms.date: 05/02/2022
+ms.date: 08/08/2024
 
 ---
 
diff --git a/articles/migrate/scale-physical-assessment.md b/articles/migrate/scale-physical-assessment.md
@@ -6,7 +6,7 @@ ms.author: rajosh
 ms.manager: abhemraj
 ms.service: azure-migrate
 ms.topic: how-to
-ms.date: 05/02/2022
+ms.date: 06/30/2023
 ---
 
 # Assess large numbers of physical servers for migration to Azure
diff --git a/articles/migrate/scale-vmware-assessment.md b/articles/migrate/scale-vmware-assessment.md
@@ -6,16 +6,16 @@ ms.author: rajosh
 ms.manager: abhemraj
 ms.service: azure-migrate
 ms.topic: how-to
-ms.date: 12/12/2022
-ms.custom: engagement-fy23
+ms.date: 06/30/2023
+ms.custom: engagement-fy25
 ---
 
 # Assess large numbers of servers in VMware environment for migration to Azure
 
 
 This article describes how to assess large numbers (1000-35,000) of on-premises servers in a VMware environment for migration to Azure, using the Azure Migrate Discovery and assessment tool.
 
-[Azure Migrate](migrate-services-overview.md) provides a hub of tools that help you to discover, assess, and migrate apps, infrastructure, and workloads to Microsoft Azure. The hub includes Azure Migrate tools, and third-party independent software vendor (ISV) offerings. 
+[Azure Migrate](migrate-services-overview.md) provides a hub of tools that help you to discover, assess, and migrate apps, infrastructure, and workloads to Microsoft Azure. The hub includes Azure Migrate tools, and partner independent software vendor (ISV) offerings. 
 
 In this article, you learn how to:
 > [!div class="checklist"]
@@ -30,11 +30,11 @@ In this article, you learn how to:
 
 ## Plan for assessment
 
-When planning for assessment of large number of servers in VMware environment, there are a couple of things to think about:
+When you plan for assessment of large number of servers in VMware environment, there are a couple of things to think about:
 
 - **Plan Azure Migrate projects**: Figure out how to deploy Azure Migrate projects. For example, if your data centers are in different geographies, or you need to store discovery, assessment, or migration-related metadata in a different geography, you might need multiple projects. 
 - **Plan appliances**: Azure Migrate uses an on-premises Azure Migrate appliance, deployed as a VMware VM, to continually discover servers. The appliance monitors environment changes such as adding servers, disks, or network adapters. It also sends metadata and performance data about them to Azure. You need to figure out how many appliances you need to deploy.
-- **Plan accounts for discovery**: The Azure Migrate appliance uses an account with access to vCenter Server in order to discover servers for assessment and migration. If you're discovering more than 10,000 servers, set up multiple accounts as it is necessary that there is no overlap among servers discovered from any two appliances in a project. 
+- **Plan accounts for discovery**: The Azure Migrate appliance uses an account with access to vCenter Server in order to discover servers for assessment and migration. If you're discovering more than 10,000 servers, set up multiple accounts as it is necessary that there's no overlap among servers discovered from any two appliances in a project. 
 
 > [!NOTE]
 > If you are setting up multiple appliances, ensure there is no overlap among the servers on the vCenter accounts provided. A discovery with such an overlap is an unsupported scenario. If a server is discovered by more than one appliance, this results in duplicates in discovery and in issues while enabling replication for the server using the Azure portal in the Migration and modernization tool.
@@ -55,9 +55,9 @@ With these limits in mind, here are some example deployments:
 **vCenter server** | **Servers to be discovered** | **Recommendation** | **Action** |
 --- |--- |--- |--- |
 One | < 10,000 | One Azure Migrate project.<br><br> One appliance can discover up to 10,000 servers running on up to 10 vCenter Servers.<br><br> Provide one or more vCenter Server accounts for discovery. | Set up an appliance to discover servers from up to 10 vCenter Servers mapped to one or more vCenter Server accounts, scoped to discover less than 10,000 servers. <br> <br>You can analyze dependencies on servers across vCenter Servers discovered from the same appliance.|
-One | > 10,000 | One Azure Migrate project.<br><br> One appliance can discover up to 10,000 servers running on up to 10 vCenter Servers.<br><br> Provide one or more vCenter Server accounts for discovery. | Set up an appliance to connect up to 10 vCenter Servers mapped to one or more vCenter Server accounts, scoped to discover less than 10,000 servers. You need to deploy additional appliances for every 10,000 servers.<br><br> If the number of servers is greater than 10,000, set up additional appliances with the vCenter Server accounts scoped accordingly. <br><br> You can analyze dependencies on servers across vCenter Servers discovered from the same appliance.<br> <br> Ensure there is no overlap among the servers on the vCenter accounts provided. A discovery with such an overlap is an unsupported scenario. If a server is discovered by more than one appliance, this results in a duplicate in discovery and in issues while enabling replication for the server using the Azure portal in the Migration and modernization tool. |
+One | > 10,000 | One Azure Migrate project.<br><br> One appliance can discover up to 10,000 servers running on up to 10 vCenter Servers.<br><br> Provide one or more vCenter Server accounts for discovery. | Set up an appliance to connect up to 10 vCenter Servers mapped to one or more vCenter Server accounts, scoped to discover less than 10,000 servers. You need to deploy additional appliances for every 10,000 servers.<br><br> If the number of servers is greater than 10,000, set up additional appliances with the vCenter Server accounts scoped accordingly. <br><br> You can analyze dependencies on servers across vCenter Servers discovered from the same appliance.<br> <br> Ensure there's no overlap among the servers on the vCenter accounts provided. A discovery with such an overlap is an unsupported scenario. If a server is discovered by more than one appliance, this results in a duplicate in discovery and in issues while enabling replication for the server using the Azure portal in the Migration and modernization tool. |
 Multiple | < 10,000 |  One Azure Migrate project.<br><br> One appliance can discover up to 10,000 servers running on up to 10 vCenter Servers.<br><br> Provide one or more vCenter Server accounts for discovery. | Set up an appliance to connect up to 10 vCenter Servers mapped to one or more vCenter Server accounts, scoped to discover less than 10,000 servers. <br><br> You need to deploy additional appliances for every 10 vCenter Servers.<br> <br> You can analyze dependencies on servers across vCenter Servers discovered from the same appliance. |
-Multiple | > 10,000 | One Azure Migrate project.<br><br> One appliance can discover up to 10,000 servers running on up to 10 vCenter Servers.<br><br> Provide one or more vCenter Server accounts for discovery. | Set up an appliance to discover VMs from up to 10 vCenter Servers mapped to one or more vCenter Server accounts, scoped to discover less than 10,000 servers. You need to deploy additional appliances for every 10 vCenter Servers. <br><br> If the number of servers is greater than 10,000, set up additional appliances with the vCenter Server accounts scoped accordingly. <br><br> You can analyze dependencies on servers across vCenter Servers discovered from the same appliance. <br><br> Ensure there is no overlap among the servers on the vCenter accounts provided. A discovery with such an overlap is an unsupported scenario. If a server is discovered by more than one appliance, this results in a duplicate in discovery and in issues while enabling replication for the server using the Azure portal in the Migration and modernization tool. |
+Multiple | > 10,000 | One Azure Migrate project.<br><br> One appliance can discover up to 10,000 servers running on up to 10 vCenter Servers.<br><br> Provide one or more vCenter Server accounts for discovery. | Set up an appliance to discover VMs from up to 10 vCenter Servers mapped to one or more vCenter Server accounts, scoped to discover less than 10,000 servers. You need to deploy additional appliances for every 10 vCenter Servers. <br><br> If the number of servers is greater than 10,000, set up additional appliances with the vCenter Server accounts scoped accordingly. <br><br> You can analyze dependencies on servers across vCenter Servers discovered from the same appliance. <br><br> Ensure there's no overlap among the servers on the vCenter accounts provided. A discovery with such an overlap is an unsupported scenario. If a server is discovered by more than one appliance, this results in a duplicate in discovery and in issues while enabling replication for the server using the Azure portal in the Migration and modernization tool. |
 
 
 
@@ -67,7 +67,7 @@ If you're planning for a multi-tenant environment, you can scope the discovery o
 
 - You can set the appliance discovery scope to a vCenter Server data centers, clusters, or folder of clusters, hosts or folder of hosts, or individual servers.
 - If your environment is shared across tenants and you want to discover each tenant separately, you can scope access to the vCenter account that the appliance uses for discovery. 
-    - You may want to scope by VM folders if the tenants share hosts. Azure Migrate can't discover servers if the vCenter account has access granted at the vCenter VM folder level. If you are looking to scope your discovery by VM folders, you can do so by ensuring the vCenter account has read-only access assigned at a server level. [Learn more](set-discovery-scope.md).
+    - You might want to scope by VM folders if the tenants share hosts. Azure Migrate can't discover servers if the vCenter account has access granted at the vCenter VM folder level. If you're looking to scope your discovery by VM folders, you can do so by ensuring the vCenter account has read-only access assigned at a server level. [Learn more](set-discovery-scope.md).
 
 ## Prepare for assessment
 
