Skip to content

Commit 35c5e7f

Browse files
addressing github issue
1 parent 5c47b4d commit 35c5e7f

File tree

2 files changed

+6
-9
lines changed

2 files changed

+6
-9
lines changed

articles/migrate/resources-faq.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -57,14 +57,14 @@ You identify the tool you need, and add it to an Azure Migrate project. If you
5757
- In each tool, there's an option to connect to Azure Migrate. Follow the tool instructions and documentation, to connect the tool with Azure Migrate.
5858
You centrally track your migration journey from within the Azure Migrate project, across Azure and other tools.
5959

60-
### How do I delete a project?
60+
## How do I delete a project?
6161

6262
[Learn how to](how-to-delete-project.md) delete a project.
6363

6464

65+
## Do machines retain domain identity after migration?
6566

66-
67-
67+
Assuming that domain services are [integrated into Azure](https://docs.microsoft.com/azure/architecture/reference-architectures/identity/), then domain membership, and machine identity in the domain, is retained after migration.
6868

6969
## Next steps
7070
Read the [Azure Migrate overview](migrate-services-overview.md).

articles/migrate/tutorial-prepare-vmware.md

Lines changed: 3 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,8 @@
11
---
22
title: Prepare VMware VMs for assessment/migration with Azure Migrate
33
description: Learn how to prepare for assessment/migration of VMware VMs with Azure Migrate.
4-
author: rayne-wiselman
5-
ms.service: azure-migrate
64
ms.topic: tutorial
75
ms.date: 11/19/2019
8-
ms.author: raynew
96
ms.custom: mvc
107
---
118

@@ -37,7 +34,7 @@ You need these permissions.
3734
--- | ---
3835
**Create an Azure Migrate project** | Your Azure account needs permissions to create a project.
3936
**Register the Azure Migrate appliance** | Azure Migrate uses a lightweight Azure Migrate appliance 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/> - The first app communicates with Azure Migrate service endpoints.<br/> - The second app accesses an Azure Key Vault created during registration to store Azure AD app info and appliance configuration settings.
40-
**Create a Key Vault** | To migrate VMware VMs with 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 need role assignment permissions on the resource group in which the Azure Migrate project resides.
37+
**Create a Key Vault** | To migrate VMware VMs with 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 need permissions on the resource group in which the Azure Migrate project resides.
4138

4239

4340
### Assign permissions to create project
@@ -75,9 +72,9 @@ The tenant/global admin can grant permissions as follows
7572

7673
The tenant/global admin can assign the Application Developer role to an account. [Learn more](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-users-assign-role-azure-portal).
7774

78-
### Assign role assignment permissions
75+
### Assign permissions to create a Key Vault
7976

80-
To enable Azure Migrate to create a Key Vault, assign role assignment permissions as follows:
77+
To enable Azure Migrate to create a Key Vault, assign permissions as follows:
8178

8279
1. In the resource group in the Azure portal, select **Access control (IAM)**.
8380
2. In **Check access**, find the relevant account, and click it to view permissions.

0 commit comments

Comments
 (0)