Skip to content

Commit af74825

Browse files
committed
incorporating feedback
1 parent c4cdee7 commit af74825

File tree

3 files changed

+4
-15
lines changed

3 files changed

+4
-15
lines changed

articles/migrate/best-practices-security.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -25,15 +25,15 @@ Set up a dedicated resource group for your Azure Migrate project. This practice
2525

2626
To avoid conflicts with other components, deploy the Azure Migrate appliance on a dedicated server. No other applications should be installed on the Azure Migrate appliance server.
2727

28-
## Stack selection
28+
## Appliance type
2929

30-
To choose the right stack of the Azure Migrate appliance, follow these best practices:
30+
To choose the right type of the Azure Migrate appliance, follow these best practices:
3131

3232
- To discover the VMware estate, use the VMware appliance that supports agentless dependency analysis. You can use the same appliance for agentless migration.
3333

3434
- To discover the Hyper-V estate, use the Hyper-V appliance that supports agentless dependency analysis. You can use the same appliance for migration, but it requires agent installation at Hyper-V hosts.
3535

36-
- To discover physical, AWS, and GCP servers, use a physical stack of the appliance that also supports agentless dependency analysis. For migration, a secondary replication appliance is required, and agents should be installed on the target machines.
36+
- To discover physical, AWS, and GCP servers, use a physical type of the appliance that also supports agentless dependency analysis. For migration, a secondary replication appliance is required, and agents should be installed on the target machines.
3737

3838
## Network
3939

articles/migrate/how-to-use-azure-migrate-with-private-endpoints.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.date: 02/06/2024
1212

1313
# Support requirements and considerations for private endpoint connectivity
1414

15-
This article describes how to use Azure Migrate to discover, assess, and migrate servers over a private network by using [Azure Private Link](../private-link/private-endpoint-overview.md). You can use the Azure Migrate Discovery and Assessment tool and the Azure Migrate and Modernize tool to connect to Azure Migrate over an Azure ExpressRoute private peering connection or a site-to-site VPN connection by using Private Link. For more information about these tools, see [What is Azure Migrate?](migrate-services-overview.md).
15+
This article describes how to use Azure Migrate to discover, assess, and migrate servers over a private network by using [Azure Private Link](../private-link/private-endpoint-overview.md). You can use the tools in Azure Migrate to connect to the service over an Azure ExpressRoute private peering connection or a site-to-site VPN connection by using Private Link. For more information about these tools, see [What is Azure Migrate?](migrate-services-overview.md).
1616

1717
We recommend the method of private endpoint connectivity when there's an organizational requirement to access Azure Migrate and other Azure resources without traversing public networks. By using Private Link, you can use your existing ExpressRoute private peering circuits for better bandwidth or latency requirements.
1818

articles/migrate/migrate-support-matrix.md

Lines changed: 0 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -110,17 +110,6 @@ Microsoft Azure operated by 21Vianet | China North 2
110110

111111
[Review](migrate-support-matrix-hyper-v.md) the support matrix for using the Azure Migrate Discovery and Assessment tool and the Azure Migrate and Modernize tool to assess Hyper-V VMs.
112112

113-
::: moniker range="migrate-classic"
114-
115-
## Azure Migrate versions
116-
117-
There are two versions of the Azure Migrate service:
118-
119-
- **Current version**: You can use the current version to create new projects, discover on-premises servers, and orchestrate assessments and migrations. [Learn more](whats-new.md).
120-
- **Previous version**: The previous version supported only the assessment of on-premises VMware VMs. You should now use the current version. In the previous version, you can't create new projects or perform new discoveries.
121-
122-
::: moniker-end
123-
124113
## Related content
125114

126115
- [Assess VMware VMs for migration to Azure](./tutorial-assess-vmware-azure-vm.md)

0 commit comments

Comments
 (0)