Skip to content

Commit 9b0f6c5

Browse files
authored
Merge pull request #299746 from MicrosoftDocs/release-remove-vmware-scenario
[Out of Band Publish] azure-docs-pr - release-remove-vmware-scenario - 05/13- 11:00AM IST (1:30 PM CST)
2 parents b34633f + 2c68192 commit 9b0f6c5

File tree

48 files changed

+359
-705
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

48 files changed

+359
-705
lines changed

articles/migrate/.openpublishing.redirection.migrate.json

Lines changed: 0 additions & 115 deletions
Original file line numberDiff line numberDiff line change
@@ -20,111 +20,6 @@
2020
"redirect_url": "discovered-metadata",
2121
"redirect_document_id": false
2222
},
23-
{
24-
"source_path_from_root": "/articles/migrate/migrate-support-matrix-vmware-migration.md",
25-
"redirect_url": "/azure/migrate/vmware/migrate-support-matrix-vmware-migration",
26-
"redirect_document_id": false
27-
},
28-
{
29-
"source_path_from_root": "/articles/migrate/migrate-support-matrix-vmware.md",
30-
"redirect_url": "/azure/migrate/vmware/migrate-support-matrix-vmware?context=/azure/migrate/context/migrate-context",
31-
"redirect_document_id": true
32-
},
33-
{
34-
"source_path_from_root": "/articles/migrate/tutorial-discover-vmware.md",
35-
"redirect_url": "/azure/migrate/vmware/tutorial-discover-vmware?context=/azure/migrate/context/migrate-context",
36-
"redirect_document_id": true
37-
},
38-
{
39-
"source_path_from_root": "/articles/migrate/set-discovery-scope.md",
40-
"redirect_url": "/azure/migrate/vmware/set-discovery-scope?context=/azure/migrate/context/migrate-context",
41-
"redirect_document_id": true
42-
},
43-
{
44-
"source_path_from_root": "/articles/migrate/how-to-set-up-appliance-vmware.md",
45-
"redirect_url": "/azure/migrate/vmware/how-to-set-up-appliance-vmware?context=/azure/migrate/context/migrate-context",
46-
"redirect_document_id": true
47-
},
48-
{
49-
"source_path_from_root": "/articles/migrate/tutorial-import-vmware-using-rvtools-xlsx.md",
50-
"redirect_url": "/azure/migrate/vmware/tutorial-import-vmware-using-rvtools-xlsx?context=/azure/migrate/context/migrate-context",
51-
"redirect_document_id": true
52-
},
53-
{
54-
"source_path_from_root": "/articles/migrate/tutorial-assess-vmware-azure-vm.md",
55-
"redirect_url": "/azure/migrate/vmware/tutorial-assess-vmware-azure-vm?context=/azure/migrate/context/migrate-context",
56-
"redirect_document_id": true
57-
},
58-
{
59-
"source_path_from_root": "/articles/migrate/tutorial-assess-vmware-azure-vmware-solution.md",
60-
"redirect_url": "/azure/migrate/vmware/tutorial-assess-vmware-azure-vmware-solution?context=/azure/migrate/context/migrate-context",
61-
"redirect_document_id": true
62-
},
63-
{
64-
"source_path_from_root": "/articles/migrate/server-migrate-overview.md",
65-
"redirect_url": "/azure/migrate/vmware/server-migrate-overview?context=/azure/migrate/context/migrate-context",
66-
"redirect_document_id": true
67-
},
68-
{
69-
"source_path_from_root": "/articles/migrate/concepts-vmware-agentless-migration.md",
70-
"redirect_url": "/azure/migrate/vmware/concepts-vmware-agentless-migration?context=/azure/migrate/context/migrate-context",
71-
"redirect_document_id": true
72-
},
73-
{
74-
"source_path_from_root": "/articles/migrate/prepare-for-agentless-migration.md",
75-
"redirect_url": "/azure/migrate/vmware/prepare-for-agentless-migration?context=/azure/migrate/context/migrate-context",
76-
"redirect_document_id": true
77-
},
78-
{
79-
"source_path_from_root": "/articles/migrate/tutorial-migrate-vmware.md",
80-
"redirect_url": "/azure/migrate/vmware/tutorial-migrate-vmware",
81-
"redirect_document_id": true
82-
},
83-
{
84-
"source_path_from_root": "/azure/migrate/vmware/tutorial-migrate-vmware.md",
85-
"redirect_url": "tutorial-migrate-vmware?context=/azure/migrate/context/migrate-context",
86-
"redirect_document_id": true
87-
},
88-
{
89-
"source_path_from_root": "/articles/migrate/tutorial-migrate-vmware-powershell.md",
90-
"redirect_url": "/azure/migrate/vmware/tutorial-migrate-vmware-powershell?context=/azure/migrate/context/migrate-context",
91-
"redirect_document_id": true
92-
},
93-
{
94-
"source_path_from_root": "/articles/migrate/troubleshoot-changed-block-tracking-replication.md",
95-
"redirect_url": "/azure/migrate/vmware/troubleshoot-changed-block-tracking-replication?context=/azure/migrate/context/migrate-context",
96-
"redirect_document_id": true
97-
},
98-
{
99-
"source_path_from_root": "/articles/migrate/troubleshoot-replication-vmware.md",
100-
"redirect_url": "/azure/migrate/vmware/troubleshoot-replication-vmware?context=/azure/migrate/context/migrate-context",
101-
"redirect_document_id": true
102-
},
103-
{
104-
"source_path_from_root": "/articles/migrate/agent-based-migration-architecture.md",
105-
"redirect_url": "/azure/migrate/vmware/agent-based-migration-architecture?context=/azure/migrate/context/migrate-context",
106-
"redirect_document_id": true
107-
},
108-
{
109-
"source_path_from_root": "/articles/migrate/tutorial-migrate-vmware-agent.md",
110-
"redirect_url": "/azure/migrate/vmware/tutorial-migrate-vmware-agent?context=/azure/migrate/context/migrate-context",
111-
"redirect_document_id": true
112-
},
113-
{
114-
"source_path_from_root": "/articles/migrate/how-to-migrate-vmware-vms-with-cmk-disks.md",
115-
"redirect_url": "/azure/migrate/vmware/how-to-migrate-vmware-vms-with-cmk-disks?context=/azure/migrate/context/migrate-context",
116-
"redirect_document_id": true
117-
},
118-
{
119-
"source_path_from_root": "/articles/migrate/how-to-automate-migration.md",
120-
"redirect_url": "/azure/migrate/vmware/how-to-automate-migration?context=/azure/migrate/context/migrate-context",
121-
"redirect_document_id": true
122-
},
123-
{
124-
"source_path_from_root": "/articles/migrate/how-to-test-replicating-virtual-machines.md",
125-
"redirect_url": "/azure/migrate/vmware/how-to-test-replicating-virtual-machines?context=/azure/migrate/context/migrate-context",
126-
"redirect_document_id": true
127-
},
12823
{
12924
"source_path_from_root": "/articles/migrate/migrate-scenarios-assessment.md",
13025
"redirect_url": "contoso-migration-assessment",
@@ -255,11 +150,6 @@
255150
"redirect_url": "scale-hyper-v-assessment",
256151
"redirect_document_id": false
257152
},
258-
{
259-
"source_path_from_root": "/articles/migrate/scale-vmware-assessment.md",
260-
"redirect_url": "/azure/migrate/vmware/scale-vmware-assessment",
261-
"redirect_document_id": false
262-
},
263153
{
264154
"source_path_from_root": "/articles/migrate/troubleshooting-general.md",
265155
"redirect_url": "troubleshoot-general",
@@ -320,11 +210,6 @@
320210
"redirect_url": "/azure/migrate/migrate-hyper-v-servers-to-azure-using-private-link",
321211
"redirect_document_id": false
322212
},
323-
{
324-
"source_path_from_root": "/articles/migrate/tutorial-assess-sql-vmware.md",
325-
"redirect_url": "/azure/migrate/vmware/tutorial-assess-sql-vmware",
326-
"redirect_document_id": false
327-
},
328213
{
329214
"source_path_from_root": "/articles/migrate/tutorial-assess-webapps-hyper-v.md",
330215
"redirect_url": "tutorial-assess-webapps",

articles/migrate/vmware/agent-based-migration-architecture.md renamed to articles/migrate/agent-based-migration-architecture.md

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -6,16 +6,15 @@ ms.author: vijain
66
ms.manager: kmadnani
77
ms.service: azure-migrate
88
ms.topic: concept-article
9-
ms.date: 09/26/2024
9+
ms.date: 05/08/2025
1010
ms.custom: vmware-scenario-422, engagement-fy23
1111
---
1212

1313
# Agent-based migration architecture
1414

1515

16-
This article provides an overview of the architecture and processes used for agent-based replication of VMware VMs with the [Migration and modernization](../migrate-services-overview.md) tool.
16+
This article provides an overview of the architecture and processes used for agent-based replication of VMware VMs with the [Migration and modernization](migrate-services-overview.md) tool.
1717

18-
[!INCLUDE [scenario-banner.md](../includes/scenario-banner.md)]
1918

2019
Using the Migration and modernization tool, you can replicate VMware VMs with a couple of options:
2120

@@ -27,14 +26,14 @@ Learn more about [selecting and comparing](server-migrate-overview.md?context=/a
2726

2827
## Agent-based migration
2928

30-
Agent-based migration is used to migrate on-premises VMware VMs and physical servers to Azure. It can also be used to migrate other on-premises virtualized servers, as well as private and public cloud VMs, including AWS instances, and GCP VMs. Agent-based migration in Azure Migrate uses some backend functionality from the [Azure Site Recovery](../../site-recovery/site-recovery-overview.md) service.
29+
Agent-based migration is used to migrate on-premises VMware VMs and physical servers to Azure. It can also be used to migrate other on-premises virtualized servers, as well as private and public cloud VMs, including AWS instances, and GCP VMs. Agent-based migration in Azure Migrate uses some backend functionality from the [Azure Site Recovery](../site-recovery/site-recovery-overview.md) service.
3130

3231

3332
## Architectural components
3433

3534
The diagram illustrates the components involved in agent-based migration.
3635

37-
![Diagram shows the components for agent-based migration, which are explained in a table.](../media/agent-based-replication-architecture/architecture.png)
36+
![Diagram shows the components for agent-based migration, which are explained in a table.](./media/agent-based-replication-architecture/architecture.png)
3837

3938
The table summarizes the components used for agent-based migration.
4039

@@ -86,7 +85,7 @@ By default, you deploy a single replication appliance that runs both the configu
8685

8786
### Plan VMware deployment
8887

89-
If you're replicating VMware VMs, you can use the [Site Recovery Deployment Planner for VMware](../../site-recovery/site-recovery-deployment-planner.md?context=/azure/migrate/context/vmware-context), to help determine performance requirements, including the daily data change rate, and the process servers you need.
88+
If you're replicating VMware VMs, you can use the [Site Recovery Deployment Planner for VMware](../site-recovery/site-recovery-deployment-planner.md?context=/azure/migrate/context/vmware-context), to help determine performance requirements, including the daily data change rate, and the process servers you need.
9089

9190
### Replication appliance capacity
9291

articles/migrate/assessment-prerequisites.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: ankitsurkar06
55
ms.author: ankitsurkar
66
ms.service: azure-migrate
77
ms.topic: concept-article
8-
ms.date: 04/17/2025
8+
ms.date: 05/08/2025
99
monikerRange: migrate
1010
---
1111

@@ -23,8 +23,8 @@ Azure Migrate assessments identifies the readiness and right-sized Azure targets
2323

2424
The discovery source might vary for different workloads depending on the data required for creating the assessments. You can discover your on-premises servers by using either of the following methods:
2525

26-
- [[Deploying](vmware/tutorial-discover-vmware.md)] a light-weight Azure Migrate appliance to perform agentless discovery.
27-
- [Importing](vmware/tutorial-import-vmware-using-rvtools-xlsx.md) the workload information using predefined templates.
26+
- [Deploying](tutorial-discover-vmware.md) a light-weight Azure Migrate appliance to perform agentless discovery.
27+
- [Importing](tutorial-import-vmware-using-rvtools-xlsx.md) the workload information using predefined templates.
2828

2929
The recommended discovery source is the Azure Migrate appliance as it provides an in-depth view of your machines and ensures regular flow of configuration and performance data, and accounts for changes in the source environment.
3030

@@ -33,4 +33,4 @@ The recommended discovery source is the Azure Migrate appliance as it provides a
3333
If you're using the Azure Migrate appliance for assessment, see [metadata and performance data](discovered-metadata.md) collected as an input for the assessment.
3434

3535
## Next steps
36-
Migrate [VMware VMs](tutorial-migrate-vmware.md), [Hyper-V VMs](tutorial-migrate-hyper-v.md), and [physical servers](tutorial-migrate-physical-virtual-machines.md).
36+
Migrate [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/assessments-overview-migrate-to-azure-db-mysql.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how to assess your on-premises MySQL database instances for m
44
author: ankitsurkar06
55
ms.author: ankitsurkar
66
ms.topic: concept-article
7-
ms.date: 02/24/2025
7+
ms.date: 05/08/2025
88
monikerRange: migrate-classic
99
---
1010

@@ -22,10 +22,10 @@ The Azure Migrate: Discovery and assessment tool supports the following types of
2222

2323
**Assessment Type** | **Details**
2424
--- | ---
25-
**Azure VM** | Assessments to migrate your on-premises servers to Azure virtual machines.<br/><br>You can assess your on-premises servers in [VMware environment](vmware/how-to-set-up-appliance-vmware.md), [Hyper-V environment](how-to-set-up-appliance-hyper-v.md), and [physical servers](how-to-set-up-appliance-physical.md) for migration to Azure VMs using this assessment type.
25+
**Azure VM** | Assessments to migrate your on-premises servers to Azure virtual machines.<br/><br>You can assess your on-premises servers in [VMware environment](how-to-set-up-appliance-vmware.md), [Hyper-V environment](how-to-set-up-appliance-hyper-v.md), and [physical servers](how-to-set-up-appliance-physical.md) for migration to Azure VMs using this assessment type.
2626
**Azure Databases** | Assessments to migrate your on-premises [SQL servers to Azure SQL Database or Azure SQL Managed Instance](concepts-azure-sql-assessment-calculation.md), or on-premises MySQL database instances to Azure Database for MySQL.
2727
**Web apps on Azure** | Assessments to migrate your on-premises [Spring Boot apps to Azure Spring Apps](concepts-azure-spring-apps-assessment-calculation.md) or [ASP.NET/Java web apps to Azure App Service](concepts-azure-webapps-assessment-calculation.md).
28-
**Azure VMware Solution (AVS)** | Assessments to migrate your on-premises [VMware VMs](vmware/how-to-set-up-appliance-vmware.md) to [Azure VMware Solution (AVS)](/azure/azure-vmware/introduction). [Learn more](concepts-azure-vmware-solution-assessment-calculation.md).
28+
**Azure VMware Solution (AVS)** | Assessments to migrate your on-premises [VMware VMs](how-to-set-up-appliance-vmware.md) to [Azure VMware Solution (AVS)](/azure/azure-vmware/introduction). [Learn more](concepts-azure-vmware-solution-assessment-calculation.md).
2929

3030

3131
## MySQL assessments - Overview and sizing criteria

articles/migrate/azure-migrate-unsupported-regions.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: v-uhabiba
66
ms.manager: ankitsurkar
77
ms.service: azure-migrate
88
ms.topic: troubleshooting
9-
ms.date: 04/24/2025
9+
ms.date: 05/08/2025
1010
ms.custom: reference_regions
1111

1212
---
@@ -23,14 +23,14 @@ Azure provides multiple methods to facilitate seamless migration to a new region
2323

2424
### Agentless migration for VMware (recommended)
2525

26-
- VMware Virtual Machines without using an agent by utilizing the Migration and Modernization tool. See, [Azure Migrate documentation](vmware/tutorial-migrate-vmware.md).
26+
- VMware Virtual Machines without using an agent by utilizing the Migration and Modernization tool. See, [Azure Migrate documentation](tutorial-migrate-vmware.md).
2727
- When using Azure Migrate’s replication wizard for the first time, specify the *new region* as the target region for migration.
2828
- Create the storage account used for replication in the new region.
2929
- For private endpoint configurations, manually create and configure the storage account in the new region with a Private Endpoint and associate it with the migration project.
3030

3131
### Agent-based migration
3232

33-
- **VMware**: Migrate VMware vSphere Virtual Machines using the agent-based Migration and Modernization tool. See, [Azure Migrate documentation](vmware/tutorial-migrate-vmware-agent.md).
33+
- **VMware**: Migrate VMware vSphere Virtual Machines using the agent-based Migration and Modernization tool. See, [Azure Migrate documentation](tutorial-migrate-vmware-agent.md).
3434
- **Hyper-V**: Migrate Hyper-V Virtual Machines to Azure using the Migration and Modernization tool. See, [Azure Migrate documentation](tutorial-migrate-hyper-v.md).
3535
- **Physical machines**: Migrate physical servers to Azure using the Migration and Modernization tool. See, [Azure Migrate documentation](tutorial-migrate-physical-virtual-machines.md).
3636

articles/migrate/breadcrumb/toc.yml

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,10 +5,6 @@
55
- name: Migrate
66
tocHref: /azure/migrate/
77
topicHref: /azure/migrate/index
8-
items:
9-
- name: VMware
10-
tocHref: /azure/migrate/vmware/
11-
topicHref: /azure/migrate/vmware/start-here-vmware
128

139
- name: Azure
1410
tocHref: /sql/

articles/migrate/common-questions-discovery-assessment.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Questions about assessments in Azure Migrate
33
description: Get answers to common questions about assessments in Azure Migrate.
44
ms.topic: concept-article
55
ms.service: azure-migrate
6-
ms.date: 08/06/2024
6+
ms.date: 05/08/2025
77
ms.custom: engagement-fy25
88
---
99

@@ -301,4 +301,4 @@ For machines imported via a CSV file, the default migration tool in an AVS asses
301301

302302
## Next steps
303303

304-
Learn more about discovering [VMware VMs](./vmware/tutorial-discover-vmware.md?context=/azure/migrate/context/migrate-context), [Hyper-V VMs](tutorial-discover-hyper-v.md), and [Physical servers](tutorial-discover-physical.md).
304+
Learn more about discovering [VMware VMs](tutorial-discover-vmware.md), [Hyper-V VMs](tutorial-discover-hyper-v.md), and [Physical servers](tutorial-discover-physical.md).

articles/migrate/vmware/concepts-vmware-agentless-migration.md renamed to articles/migrate/concepts-vmware-agentless-migration.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: piyushdhore
66
ms.manager: vijain
77
ms.topic: concept-article
88
ms.service: azure-migrate
9-
ms.date: 02/03/2025
9+
ms.date: 05/12/2025
1010
ms.custom: vmware-scenario-422, engagement-fy24
1111
---
1212
# Agentless migration architecture
@@ -17,7 +17,7 @@ This article describes the replication concepts when migrating VMware VMs using
1717

1818
The agentless replication option works by using VMware snapshots and VMware changed block tracking (CBT) technology to replicate data from virtual machine disks. The following block diagram shows you various steps involved when you migrate your virtual machines using the Migration and modernization tool.
1919

20-
![Migration steps.](../media/concepts-vmware-agentless-migration/migration-phases.png)
20+
![Migration steps.](./media/concepts-vmware-agentless-migration/migration-phases.png)
2121

2222
When replication is configured for a virtual machine, it first goes through an initial replication phase. During initial replication, a VM snapshot is taken, and a full copy of data from the snapshot disks is replicated to managed disks in your target subscription.
2323

@@ -169,7 +169,7 @@ We use the following constraints to ensure that we don't exceed the IOPS limits
169169

170170
Azure Migrate supports concurrent replication of 500 virtual machines. When you're planning to replicate more than 300 virtual machines, you must deploy a scale-out appliance. The scale-out appliance is similar to an Azure Migrate primary appliance but consists only of gateway agent to facilitate data transfer to Azure. The following diagram shows the recommended way to use the scale-out appliance.
171171

172-
![Scale-out configuration.](../media/concepts-vmware-agentless-migration/scale-out-configuration.png)
172+
![Scale-out configuration.](./media/concepts-vmware-agentless-migration/scale-out-configuration.png)
173173

174174

175175
You can deploy the scale-out appliance anytime after configuring the primary appliance, but isn't required until there are 300 VMs replicating concurrently. When there are 300 VMs replicating concurrently, you must deploy the scale-out appliance to proceed.
@@ -199,7 +199,7 @@ You could create a policy on the Azure Migrate appliance to throttle replication
199199
> [!NOTE]
200200
> This is applicable to all the replicating VMs from the Azure Migrate appliance simultaneously.
201201
202-
You can also increase and decrease replication bandwidth based on a schedule using the [sample script](../common-questions-server-migration.md).
202+
You can also increase and decrease replication bandwidth based on a schedule using the [sample script](common-questions-server-migration.md).
203203

204204
### Blackout window
205205

articles/migrate/context/vmware-context.yml

Lines changed: 0 additions & 4 deletions
This file was deleted.

0 commit comments

Comments
 (0)