Skip to content

Commit 64daaa2

Browse files
Update end-to-end-portal-experience-server-migrations.md
1 parent fde3a79 commit 64daaa2

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

articles/migrate/end-to-end-portal-experience-server-migrations.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ Before you begin, ensure the following:
3434
- [Discover physical servers and servers running in AWS and GCP](tutorial-discover-physical.md)
3535

3636
>[!NOTE]
37-
> Use the link on the Migrations page by navigating to **Execute** > **Migrations** in your Azure Migrate Project to switch to the classic portal for discovery and execution of agent-based and Hyper-V migrations using the replication appliance without the Azure Migrate appliance. These servers will not be visible for tracking in the end-to-end portal experience. We recommend starting discovery with the Azure Migrate appliance to take advantage of the benefits of the end-to-end portal experience.
37+
> Migrations using other tools (agent-based replication appliance, Hyper-V replication provider) without installing Azure Migrate appliance (VMWare, Hyper-V, Physical) is not supported in the new end-to-end experience. Navigate to Azure Migrate Project>Execute>Migrations and switch to the old classic portal for these scenarios.
3838
3939
## Execute migrations using the end-to-end portal
4040

@@ -74,4 +74,4 @@ To track migration progress for your servers, follow the steps:
7474

7575
## Related content
7676

77-
[Learn more](server-migrate-overview.md) about different migration methods in Azure Migrate.
77+
[Learn more](server-migrate-overview.md) about different migration methods in Azure Migrate.

0 commit comments

Comments
 (0)