Skip to content

Commit e0613b9

Browse files
fixing links
1 parent 35c5e7f commit e0613b9

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

articles/migrate/migrate-support-matrix.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ For Azure Migrate to work with Azure you need these permissions before you start
6262
--- | --- | ---
6363
Create an Azure Migrate project | Your Azure account needs permissions to create a project. | Set up for [VMware](tutorial-prepare-vmware.md#assign-permissions-to-create-project), [Hyper-V](tutorial-prepare-hyper-v.md#assign-permissions-to-create-project), or [physical servers](tutorial-prepare-physical.md#assign-permissions-to-create-project).
6464
Register the Azure Migrate appliance | Azure Migrate uses a lightweight [Azure Migrate appliance](migrate-appliance.md) to assess VMware VMs with Azure Migrate Server Assessment, and to run [agentless migration](server-migrate-overview.md) of VMware VMs with Azure Migrate Server Migration. This appliance discovers VMs, and sends VM metadata and performance data to Azure Migrate.<br/><br/> During registration, Azure Migrate creates two Azure Active Directory (Azure AD) apps that uniquely identify the appliance, and needs permissions to create these apps.<br/><br/> - The first app communicates with Azure Migrate service endpoints.<br/><br/> - The second app accesses an Azure Key Vault created during registration to store Azure AD app info and appliance configuration settings. | Set up for [VMware](tutorial-prepare-vmware.md#assign-permissions-to-register-the-appliance), [Hyper-V](tutorial-prepare-hyper-v.md#assign-permissions-to-register-the-appliance), or [physical servers](tutorial-prepare-physical.md#assign-permissions-to-register-the-appliance).
65-
Create a key vault for VMware agentless migration | To migrate VMware VMs with agentless Azure Migrate Server Migration, Azure Migrate creates a Key Vault to manage access keys to the replication storage account in your subscription. To create the vault, you to set permissions (Owner, or Contributor and User Access Administrator) on the resource group in which the Azure Migrate project resides. | [Set up](tutorial-prepare-vmware.md#assign-role-assignment-permissions) permissions.
65+
Create a key vault for VMware agentless migration | To migrate VMware VMs with agentless Azure Migrate Server Migration, Azure Migrate creates a Key Vault to manage access keys to the replication storage account in your subscription. To create the vault, you to set permissions (Owner, or Contributor and User Access Administrator) on the resource group in which the Azure Migrate project resides. | [Set up](tutorial-prepare-vmware.md#assign-permissions-to-create-a-key-vault) permissions.
6666

6767
## Supported geographies
6868

articles/migrate/tutorial-migrate-vmware.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -179,7 +179,7 @@ If this is the first VM you're replicating in the Azure Migrate project, Azure M
179179
- **Service bus**: Azure Migrate Server Migration uses the service bus to send replication orchestration messages to the appliance.
180180
- **Gateway storage account**: Server Migration uses the gateway storage account to store state information about the VMs being replicated.
181181
- **Log storage account**: The Azure Migrate appliance uploads replication logs for VMs to a log storage account. Azure Migrate applies the replication information to the replica managed disks.
182-
- **Key vault**: The Azure Migrate appliance uses the key vault to manage connection strings for the service bus, and access keys for the storage accounts used in replication. You should have set up the permissions that the key vault needs to access the storage account when you prepared. [Review these permissions](tutorial-prepare-vmware.md#assign-role-assignment-permissions).
182+
- **Key vault**: The Azure Migrate appliance uses the key vault to manage connection strings for the service bus, and access keys for the storage accounts used in replication. You should have set up the permissions that the key vault needs to access the storage account when you prepared. [Review these permissions](tutorial-prepare-vmware.md#assign-permissions-to-create-a-key-vault).
183183

184184

185185
## Track and monitor

0 commit comments

Comments
 (0)