Set discovery scope for servers in VMware vSphere environment
This article describes how to limit the scope of discovery for servers in VMware vSphere environment when you are:
- Discovering servers with the Azure Migrate appliance when you're using the Azure Migrate: Discovery and assessment tool.
- Discovering servers with the Azure Migrate appliance when you're using the Migration and modernization tool, for agentless migration of servers from VMware vSphere environment to Azure.
When you set up the appliance, it connects to vCenter Server and starts discovery. Before you connect the appliance to vCenter Server, you can limit discovery to vCenter Server datacenters, clusters, a folder of clusters, hosts, a folder of hosts, or individual servers. To set the scope, you assign permissions on the account that the appliance uses to access the vCenter Server.
Before you start
Assign permissions and roles
You can assign permissions on VMware vSphere inventory objects using one of two methods:
- On the account used by the appliance, assign a role with the required permissions on the objects you want to scope.
- Alternatively, assign a role to the account at the data center level, and propagate to the child objects. Then give the account a No access role, for every object that you don't want in scope. We don't recommend this approach since it's cumbersome, and might expose access controls, because every new child object is automatically granted access inherited from the parent.
You can't scope inventory discovery at the vCenter Server folder level. If you need to scope discover to servers in a folder, create a user and grant access individually to each required server. Host and cluster folders are supported.
Assign a role for assessment
On the appliance vCenter Server account you're using for discovery, apply the Read-only role for all parent objects that host servers you want to discover and assess (host, cluster, hosts folder, clusters folder, up to datacenter).
Propagate these permissions to child objects in the hierarchy.
Assign a role for agentless migration
- On the appliance vCenter Server account you're using for migration, apply a user-defined role that has the permissions needed, to all parent objects that host servers you want to discover and migrate.
- You can name the role with something that's easier to identify. For example, Azure_Migrate.
Work around for server folder restriction
Currently, the Azure Migrate: Discovery and assessment tool can't discover servers if access is granted at the vCenter Server folder level. If you do want to scope your discovery and assessment by server folders, use this workaround.
- Assign read-only permissions on all servers located in the folders you want to scope for discovery and assessment.
- Grant read-only access to all the parent objects that host the servers host, cluster, hosts folder, clusters folder, up to data center). You don't need to propagate the permissions to all child objects.
- To use the credentials for discovery, select the datacenter as Collection Scope.
The role-based access control setup ensures that the corresponding vCenter user account has access to only tenant-specific servers.