Skip to content

Commit fb7f688

Browse files
committed
fixing blocking issues
1 parent 8cfd865 commit fb7f688

File tree

6 files changed

+33
-33
lines changed

6 files changed

+33
-33
lines changed

articles/migrate/best-practices-least-privileged-account.md

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Security Best Practices for Least Privileged Accounts in Azure Migrate.
3-
description: Learn how to securely configure Azure Migrate Appliance with least privilege access by setting up read-only VMware roles with guest operations and scoped permissions, enabling efficient workload discovery, software inventory, and agentless migration..
2+
title: Security Best Practices for Least Privileged Accounts in Azure Migrate
3+
description: Learn how to securely configure Azure Migrate Appliance with least privilege access by setting up read-only VMware roles with guest operations and scoped permissions, enabling efficient workload discovery, software inventory, and agentless migration.
44
author: molishv
55
ms.author: molir
66
ms.service: azure-migrate
@@ -13,7 +13,7 @@ ms.custom:
1313

1414
---
1515

16-
# Credentials-Security best practices for setting up least privileged accounts in Azure Migrate
16+
# Credentials: Security best practices for setting up least privileged accounts in Azure Migrate
1717

1818
Azure Migrate Appliance is a lightweight tool that discovers on-premises servers and sends their configuration and performance data to Azure. It also performs software inventory, agentless dependency analysis, and detects workloads like web apps and SQL/MySQL Server instances. To use these features, users add server and guest credentials in the Appliance Config Manager. Following the principle of least privilege helps keep the setup secure and efficient.
1919

@@ -23,17 +23,17 @@ To discover the basic settings of servers running in the VMware estate, the foll
2323

2424
### vCenter account permissions
2525

26-
1. **Discovery of server metadata**: To discover basic server configurations in a VMware environment, you need read-only permissions.
26+
- **Discovery of server metadata**: To discover basic server configurations in a VMware environment, you need read-only permissions.
2727
- **Read-only**: Use either the built-in read-only role or create a copy of it.
28-
1. To discover server metadata and enable software inventory, dependency analysis, and performance assessments.
28+
- To discover server metadata and enable software inventory, dependency analysis, and performance assessments.
2929
- **Read-only**- Use the built-in read-only role or create a copy of it.
3030
- **Guest operations** - Add guest operations privileges to the read-only role.
31-
1. Scoped discovery of VMware servers:
31+
- Scoped discovery of VMware servers:
3232
- To discover specific VMs, **assign read permissions at the individual VMs**. To discover all VMs in a folder, assign read permissions at the folder level and turn on the 'propagate to children' option.
3333
- Assign guest operations permissions to the vCenter account along with read permissions to enable software inventory, dependency analysis, and performance assessments.
3434
- Give **read-only access to all parent objects that host the virtual machines**, such as the host, cluster, hosts folder, clusters folder, and data center. You don’t need to apply these permissions to all child objects.
3535
- In the vSphere client, check that read permissions are set on parent objects in both the Hosts and *Clusters* view and the *VMs & Templates* view.
36-
1. Perform agentless migration: To perform agentless migration, ensure the vCenter account used by the Azure Migrate appliance has permissions at all required levels—datacenter, cluster, host, VM, and datastore. Apply permissions at each level to avoid replication errors.
36+
- Perform agentless migration: To perform agentless migration, ensure the vCenter account used by the Azure Migrate appliance has permissions at all required levels—datacenter, cluster, host, VM, and datastore. Apply permissions at each level to avoid replication errors.
3737

3838
| **vSphere privilege name**| **Privilege purpose**| **Required** | **API privilege name** |
3939
| --- | --- | --- | --- |
@@ -43,7 +43,7 @@ To discover the basic settings of servers running in the VMware estate, the foll
4343
| Change Configuration - Acquire disk lease | Allow disk lease operations on a VM to read the disk using the VMware vSphere Virtual Disk Development Kit (VDDK) | Virtual machines | VirtualMachine.Config.DiskLease |
4444
| Provisioning - Allow read-only disk access | Allow read-only disk access: Allow opening a disk on a VM to read the disk using the VDDK. | Virtual machines | VirtualMachine.Provisioning.DiskRandomRead |
4545
| Provisioning - Allow disk access | Allow opening a disk on a VM to read the disk using the VDDK. | Virtual machines | VirtualMachine.Provisioning.DiskRandomAccess |
46-
| Provisioning - Allow virtual machine download | AAllow virtual machine download to read VM files, get logs, and troubleshoot failures | Root host or vCenter Server | VirtualMachine.Provisioning.GetVmFiles |
46+
| Provisioning - Allow virtual machine download | Allow virtual machine download to read VM files, get logs, and troubleshoot failures | Root host or vCenter Server | VirtualMachine.Provisioning.GetVmFiles |
4747
| Snapshot management | Allow Discovery, Software Inventory, and Dependency Mapping on VMs. | Virtual machines | VirtualMachine.State.* |
4848
| Guest operations | Allow creation and management of VM snapshots for replication. | Virtual machines | VirtualMachine.GuestOperations.* |
4949
| Interaction Power Off | Allow the VM to be powered off during migration to Azure. | Virtual machines | VirtualMachine.Interact.PowerOff |
@@ -61,7 +61,7 @@ For quick discovery of software inventory, server dependencies, and database ins
6161

6262
| **Use case** | **Discovered metadata** | **Credential type** |**Secure permissions** |
6363
| --- | --- | --- |
64-
| Quick guest discovery | Software inventory <br /><br /> Server dependencies (limited data)* <br /><br />Inventory of Database instances | Windows <br /><br /> Linux | Local guest user account <br /><br /> Any non-sudo guest user account. |
64+
| Quick guest discovery | Software inventory <br /><br /> Server dependencies (limited data) <br /><br />Inventory of Database instances | Windows <br /><br /> Linux | Local guest user account <br /><br /> Any non-sudo guest user account. |
6565

6666
>[!Note]
6767
> - Limitations: You can use a Windows guest or a Linux non-sudo user account to get dependency mapping data, but the following limitation can happen.
@@ -74,7 +74,7 @@ For in-depth discovery of software inventory, server dependencies, and web apps
7474
| **Use case** | **Discovered metadata** | **Credential type**| **Required permissions** |
7575
| --- | --- | --- | --- |
7676
| In-depth guest discovery | Software inventory <br /><br /> Server dependencies (full data)<br /><br /> Inventory of Database instances <br /><br /> We apps like .NET, Java Tomcat | Windows | Administrator |
77-
|In-depth guest discovery | Software inventory <br /><br /> Server dependencies (full data)<br /><br /> Inventory of Database instances <br /><br /> We apps like .NET, Java Tomcat | Linux | Following sudo permissions are required to identify server dependencies. <br /><br /> /usr/bin/netstat, `/usr/bin/ls` <br /><br /> If netstat is not available, sudo permissions on ss is required. <br /><br /> For Java webapps discovery (Tomcat servers), the user should have read and execute (r-x) permissions on all Catalina homes. <br /><br /> Execute the following command to find out all catalina homes: <br /><br /> `ps -ef | grep catalina.home` <br /><br /> Here is a sample command to up least privileged user: <br /><br /> `setfacl -m u:johndoe:rx <catalina/home/path>` |
77+
|In-depth guest discovery | Software inventory <br /><br /> Server dependencies (full data)<br /><br /> Inventory of Database instances <br /><br /> We apps like .NET, Java Tomcat | Linux | Following sudo permissions are required to identify server dependencies. <br /><br /> /usr/bin/netstat, `/usr/bin/ls` <br /><br /> If netstat is not available, sudo permissions on is required. <br /><br /> For Java webapps discovery (Tomcat servers), the user should have read and execute (r-x) permissions on all Catalina homes. <br /><br /> Execute the following command to find out all catalina homes: <br /><br /> `ps -ef | grep catalina.home` <br /><br /> Here is a sample command to up least privileged user: <br /><br /> `setfacl -m u:johndoe:rx <catalina/home/path>` |
7878

7979
## Discovery of Hyper-V estate
8080

@@ -103,8 +103,8 @@ You need the following permissions for Quick discovery of software inventory, se
103103

104104
| **Use case** | **Discovered metadata** | **Credential type** | **Details** |
105105
| --- | --- | --- | --- |
106-
| Quick server discovery | Software inventory <br /><br /> Agentless dependency analysis (limited data)* <br /><br /> Workload inventory of databases and web apps| Windows |[Follow these steps](#windows-servers).|
107-
| Quick server discovery |Software inventory <br /><br /> Agentless dependency analysis (full data)* <br /><br /> Workload inventory of databases and web apps | Linux | [Follow these steps](#linux-servers) |
106+
| Quick server discovery | Software inventory <br /><br /> Agentless dependency analysis (limited data) <br /><br /> Workload inventory of databases and web apps| Windows |[Follow these steps](#windows-servers).|
107+
| Quick server discovery |Software inventory <br /><br /> Agentless dependency analysis (full data) <br /><br /> Workload inventory of databases and web apps | Linux | [Follow these steps](#linux-servers) |
108108

109109
#### Windows servers
110110

@@ -152,13 +152,13 @@ For in-depth discovery of software inventory, server dependencies, and web apps
152152

153153
| **Use case** | **Discovered metadata** | **Credentials type** | **Commands to configure** |
154154
| --- | --- | --- | --- |
155-
| In-dept server discovery | In-depth discovery of web apps such as .NET and Java Tomcat <br /><br />Agentless dependency analysis (full data)* <br /><br />In-depth discovery of web apps such as .NET and Java Tomcat. |Windows <br /><br /> Linux | Administrator <br /><br /> To discover Java webapps on Tomcat servers, the user account needs read and execute (r-x) permissions on all Catalina home directories.<br /><br />Execute the following command to find out all catalina homes: `ps -ef | grep catalina.home`<br /><br />Here is a sample command to set up least privileged user: `setfacl -m u:johndoe:rx <catalina/home/path>` |
155+
| In-dept server discovery | In-depth discovery of web apps such as .NET and Java Tomcat <br /><br />Agentless dependency analysis (full data) <br /><br />In-depth discovery of web apps such as .NET and Java Tomcat. |Windows <br /><br /> Linux | Administrator <br /><br /> To discover Java webapps on Tomcat servers, the user account needs read and execute (r-x) permissions on all Catalina home directories.<br /><br />Execute the following command to find out all catalina homes: `ps -ef | grep catalina.home`<br /><br />Here is a sample command to set up least privileged user: `setfacl -m u:johndoe:rx <catalina/home/path>` |
156156

157157
## Database discovery
158158

159159
Software inventory is required for initiating workload discovery. Ensure that guest credentials are added to enable it. The permissions to discover SQL and MySQL databases are the same for all appliance types—VMware, Hyper-V, and physical servers.
160160

161-
### Discover SQL server instances and database:
161+
### Discover SQL server instances and database
162162

163163
Create least privileged accounts on individual SQL server instance. Use Windows authentication and assign only the required permissions.
164164

articles/migrate/best-practices-security.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.custom:
1212
# Customer intent: As a cloud migration specialist, I want to implement security best practices for deploying the migration appliance, so that I can ensure a secure and efficient migration process while protecting sensitive data.
1313
---
1414

15-
# Appliance-Security best practices to deploy Azure Migrate Appliance
15+
# Appliance: Security best practices to deploy Azure Migrate Appliance
1616

1717
[Azure Migrate](./migrate-services-overview.md) provides a hub of tools that help you to discover, assess, and migrate apps, infrastructure, and workloads to Microsoft Azure. The hub includes Azure Migrate tools, and non-Microsoft independent software vendor (ISV) offerings.
1818

articles/migrate/toc.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,9 +23,9 @@ items:
2323
href: supported-geographies.md
2424
- name: Security baseline
2525
href: /security/benchmark/azure/baselines/azure-migrate-security-baseline?toc=/azure/migrate/toc.json&bc=/azure/migrate/breadcrumb/toc.json
26-
- name: Appliance-Security best practices
26+
- name: Appliance:Security best practices
2727
href: best-practices-security.md
28-
- name: Credentials-Security best practices
28+
- name: Credentials:Security best practices
2929
href: best-practices-least-privileged-account.md
3030
- name: Requirements for Private endpoints # Explain about private end points and support requirements
3131
href: how-to-use-azure-migrate-with-private-endpoints.md

articles/migrate/tutorial-discover-hyper-v.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ If you just created a free Azure account, you're the owner of your subscription.
5252

5353
1. In the Azure portal, search for "subscriptions", and under **Services**, select **Subscriptions**.
5454

55-
:::image type="content" source="./media/tutorial-discover-hyper-v/search-subscription.png" alt-text="Screenshot of Search box to search for the Azure subscription.":::
55+
:::image type="content" source="./media/tutorial-discover-hyper-v/search-subscription.png" alt-text="Screenshot of Search box to search for the Azure subscription.":::
5656

5757
1. In the **Subscriptions** page, select the subscription in which you want to create a project.
5858

@@ -207,7 +207,7 @@ In the configuration manager, select **Set up prerequisites**, and then complete
207207
2. The appliance will verify the key and start the auto-update service, which updates all the services on the appliance to their latest versions. When the auto-update has run, you can select **View appliance services** to see the status and versions of the services running on the appliance server.
208208
3. To register the appliance, you need to select **Login**. In **Continue with Azure Login**, select **Copy code & Login** to copy the device code (you must have a device code to authenticate with Azure) and open an Azure Login prompt in a new browser tab. Make sure you've disabled the pop-up blocker in the browser to see the prompt.
209209
210-
:::image type="content" source="./media/tutorial-discover-vmware/device-code.png" alt-text="Screenshot that shows where to copy the device code and log in.":::
210+
:::image type="content" source="./media/tutorial-discover-vmware/device-code.png" alt-text="Screenshot that shows where to copy the device code and log in.":::
211211
212212
4. In a new tab in your browser, paste the device code and sign in by using your Azure username and password. Signing in with a PIN isn't supported.
213213
> [!NOTE]

articles/migrate/tutorial-discover-vmware.md

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -211,29 +211,29 @@ In the configuration manager, select **Set up prerequisites**, and then complete
211211
- If you have added proxy details or disabled the proxy or authentication, select **Save** to trigger connectivity and check connectivity again.
212212

213213
Only HTTP proxy is supported.
214-
1. **Time sync**: Check that the time on the appliance is in sync with internet time for discovery to work properly.
215-
1. **Install updates and register appliance**: To run auto-update and register the appliance, follow these steps:
214+
1. **Time sync**: Check that the time on the appliance is in sync with internet time for discovery to work properly.
215+
1. **Install updates and register appliance**: To run auto-update and register the appliance, follow these steps:
216216

217-
:::image type="content" source="./media/tutorial-discover-vmware/prerequisites.png" alt-text="Screenshot that shows setting up the prerequisites in the appliance configuration manager.":::
217+
:::image type="content" source="./media/tutorial-discover-vmware/prerequisites.png" alt-text="Screenshot that shows setting up the prerequisites in the appliance configuration manager.":::
218218

219-
1. For the appliance to run auto-update, paste the project key that you copied from the portal. If you don't have the key, go to **Azure Migrate: Discovery and assessment** > **Overview** > **Manage existing appliances**. Select the appliance name you provided when you generated the project key, and then copy the key that's shown.
220-
2. The appliance will verify the key and start the auto-update service, which updates all the services on the appliance to their latest versions. When the auto-update has run, you can select **View appliance services** to see the status and versions of the services running on the appliance server.
221-
3. To register the appliance, you need to select **Login**. In **Continue with Azure Login**, select **Copy code & Login** to copy the device code (you must have a device code to authenticate with Azure) and open an Azure sign in prompt in a new browser tab. Ensure you've disabled the pop-up blocker in the browser to see the prompt.
219+
1. For the appliance to run auto-update, paste the project key that you copied from the portal. If you don't have the key, go to **Azure Migrate: Discovery and assessment** > **Overview** > **Manage existing appliances**. Select the appliance name you provided when you generated the project key, and then copy the key that's shown.
220+
1. The appliance will verify the key and start the auto-update service, which updates all the services on the appliance to their latest versions. When the auto-update has run, you can select **View appliance services** to see the status and versions of the services running on the appliance server.
221+
1. To register the appliance, you need to select **Login**. In **Continue with Azure Login**, select **Copy code & Login** to copy the device code (you must have a device code to authenticate with Azure) and open an Azure sign in prompt in a new browser tab. Ensure you've disabled the pop-up blocker in the browser to see the prompt.
222222

223-
:::image type="content" source="./media/tutorial-discover-vmware/device-code.png" alt-text="Screenshot that shows where to copy the device code and sign in.":::
223+
:::image type="content" source="./media/tutorial-discover-vmware/device-code.png" alt-text="Screenshot that shows where to copy the device code and sign in.":::
224224

225-
4. In a new tab in your browser, paste the device code and sign in by using your Azure username and password. Signing in with a PIN isn't supported.
225+
1. In a new tab in your browser, paste the device code and sign in by using your Azure username and password. Signing in with a PIN isn't supported.
226226

227227
> [!Note]
228228
> If you close the sign in tab accidentally without logging in, refresh the browser tab of the appliance configuration manager to display the device code and Copy code & Login button.
229229
230-
5. After you successfully sign in, return to the browser tab that displays the appliance configuration manager. If the Azure user account that you used to sign in has the required permissions for the Azure resources that were created during key generation, appliance registration starts.
230+
1. After you successfully sign in, return to the browser tab that displays the appliance configuration manager. If the Azure user account that you used to sign in has the required permissions for the Azure resources that were created during key generation, appliance registration starts.
231231

232-
After the appliance is successfully registered, to see the registration details, select **View details**.
232+
After the appliance is successfully registered, to see the registration details, select **View details**.
233233

234234
1. **Install the VDDK**: The appliance checks that VMware vSphere Virtual Disk Development Kit (VDDK) is installed. Download VDDK 6.7, 7, or 8(depending on the compatibility of VDDK and ESXi versions) from VMware. Extract the downloaded zip file contents to the specified location on the appliance, the default path is *C:\Program Files\VMware\VMware Virtual Disk Development Kit* as indicated in the *Installation instructions*.
235235

236-
The Migration and modernization tool uses the VDDK to replicate servers during migration to Azure.
236+
The Migration and modernization tool uses the VDDK to replicate servers during migration to Azure.
237237

238238
You can *rerun prerequisites* at any time during appliance configuration to check whether the appliance meets all the prerequisites.
239239

0 commit comments

Comments
 (0)