You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Azure VMware Solution private clouds are provisioned with a vCenter Server and NSX Manager. You use vCenter Server to manage virtual machine (VM) workloads and NSX Manager to manage and extend the private cloud. The CloudAdmin role is used for vCenter Server, the CloudAdmin role (with restricted permissions) is used for NSX Manager.
13
+
Azure VMware Solution private clouds are provisioned with a vCenter Server and NSX Manager. You use vCenter Server to manage virtual machine (VM) workloads and NSX Manager to manage and extend the private cloud. The Cloud admin role is used for vCenter Server. With restricted permissions, the Cloud admin role is used for NSX Manager.
14
14
15
15
## vCenter Server access and identity
16
16
@@ -21,15 +21,15 @@ Azure VMware Solution private clouds are provisioned with a vCenter Server and N
21
21
22
22
### View the vCenter Server privileges
23
23
24
-
To view the privileges granted to the Azure VMware Solution CloudAdmin role on your Azure VMware Solution private cloud vCenter, use the following steps:
24
+
To view the privileges granted to the Azure VMware Solution Cloud admin role on your Azure VMware Solution private cloud vCenter, use the following steps:
25
25
26
26
1. Sign in to the vSphere Client and go to **Menu** > **Administration**.
27
27
1. Under **Access Control**, select **Roles**.
28
28
1. From the list of roles, select **CloudAdmin** and then select **Privileges**.
29
29
30
-
:::image type="content" source="media/concepts/role-based-access-control-cloudadmin-privileges.png" alt-text="Screenshot shows the roles and privileges for CloudAdmin in the vSphere Client.":::
30
+
:::image type="content" source="media/concepts/role-based-access-control-cloudadmin-privileges.png" alt-text="Screenshot shows the roles and privileges for Cloud admin in the vSphere Client.":::
31
31
32
-
The CloudAdmin role in Azure VMware Solution has the following privileges on vCenter Server. For more information, see the [VMware product documentation](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/vsphere-security-8-0/defined-privileges.html).
32
+
The Cloud admin role in Azure VMware Solution has the following privileges on vCenter Server. For more information, see the [VMware product documentation](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/vsphere-security-8-0/defined-privileges.html).
33
33
34
34
| Privilege | Description |
35
35
| --------- | ----------- |
@@ -54,15 +54,15 @@ The CloudAdmin role in Azure VMware Solution has the following privileges on vCe
54
54
55
55
### Create custom roles on vCenter Server
56
56
57
-
Azure VMware Solution supports the use of custom roles with equal or lesser privileges than the CloudAdmin role. Use the CloudAdmin role to create, modify, or delete custom roles with privileges less than or equal to their current role.
57
+
Azure VMware Solution supports the use of custom roles with equal or lesser privileges than the Cloud admin role. Use the Cloud admin role to create, modify, or delete custom roles with privileges less than or equal to their current role.
58
58
59
59
>[!NOTE]
60
-
>You can create roles with privileges greater than CloudAdmin. However, you can't assign the role to any users or groups or delete the role. Roles that have privileges greater than CloudAdmin is unsupported.
60
+
>You can create roles with privileges greater than Cloud admin. However, you can't assign the role to any users or groups or delete the role. Roles that have privileges greater than Cloud admin aren't supported.
61
61
62
-
To prevent creating roles that can't be assigned or deleted, clone the CloudAdmin role as the basis for creating new custom roles.
62
+
To prevent creating roles that can't be assigned or deleted, clone the Cloud admin role as the basis for creating new custom roles.
63
63
64
64
#### Create a custom role
65
-
1. Sign in to vCenter Server with [email protected] or a user with the CloudAdmin role.
65
+
1. Sign in to vCenter Server with [email protected] or a user with the Cloud admin role.
66
66
67
67
1. Navigate to the **Roles** configuration section and select **Menu** > **Administration** > **Access Control** > **Roles**.
68
68
@@ -87,7 +87,7 @@ To prevent creating roles that can't be assigned or deleted, clone the CloudAdmi
87
87
88
88
1. Select the role you want to apply to the user or group.
89
89
>[!NOTE]
90
-
>If you attempt to apply a user or group to a role with privileges greater than CloudAdmin, you get the result of an error.
90
+
>If you attempt to apply a user or group to a role with privileges greater than Cloud admin, you get the result of an error.
91
91
92
92
1. Check the **Propagate to children** if needed, and select **OK**. The added permission displays in the **Permissions** section.
You can access VMware NSX Manager using the built-in local user 'cloudadmin' assigned to a custom role that gives limited privileges to a user to manage VMware NSX. While Microsoft manages the lifecycle of VMware NSX, certain operations aren't allowed to a user. Operations not allowed include editing the configuration of host and edge transport nodes or starting an upgrade. For new users, Azure VMware Solution deploys them with a specific set of permissions needed by that user. The purpose is to provide a clear separation of control between the Azure VMware Solution control plane configuration and Azure VMware Solution private cloud user.
108
+
You can access VMware NSX Manager using the built-in local user Cloud admin assigned to a custom role that gives limited privileges to a user to manage VMware NSX. While Microsoft manages the lifecycle of VMware NSX, certain operations aren't allowed to a user. Operations not allowed include editing the configuration of host and edge transport nodes or starting an upgrade. For new users, Azure VMware Solution deploys them with a specific set of permissions needed by that user. The purpose is to provide a clear separation of control between the Azure VMware Solution control plane configuration and Azure VMware Solution private cloud user.
109
109
110
-
For new private cloud deployments, VMware NSX access is provided with a built-in local user cloudadmin assigned to the **cloudadmin** role with a specific set of permissions to use VMware NSX functionality for workloads.
110
+
For new private cloud deployments, VMware NSX access is provided with a built-in local user Cloud admin assigned to the **cloudadmin** role with a specific set of permissions to use VMware NSX functionality for workloads.
111
111
112
112
### VMware NSX cloudadmin user permissions
113
113
@@ -135,7 +135,7 @@ The following permissions are assigned to the **cloudadmin** user in Azure VMwar
135
135
| System | Configuration<br>Settings<br>Settings<br>Settings | Identity firewall<br>Users and Roles<br>Certificate Management (Service Certificate only)<br>User Interface Settings | Full Access<br>Full Access<br>Full Access<br>Full Access |
136
136
| System | All other || Read-only |
137
137
138
-
You can view the permissions granted to the Azure VMware Solution cloudadmin role on your Azure VMware Solution private cloud VMware NSX.
138
+
You can view the permissions granted to the Azure VMware Solution Cloud admin role on your Azure VMware Solution private cloud VMware NSX.
139
139
140
140
1. Sign in to the NSX Manager.
141
141
1. Navigate to **Systems** and locate **Users and Roles**.
@@ -152,14 +152,14 @@ In an Azure VMware Solution deployment, the VMware NSX can be integrated with ex
152
152
Unlike on-premises deployment, not all predefined NSX RBAC roles are supported with Azure VMware solution to keep Azure VMware Solution IaaS control plane config management separate from tenant network and security configuration. For more information, see the next section, Supported NSX RBAC roles.
153
153
154
154
> [!NOTE]
155
-
> VMware NSX LDAP Integration is supported only with SDDCs with VMware NSX 'cloudadmin' user.
155
+
> VMware NSX LDAP Integration is supported only with SDDCs with VMware NSX Cloud admin user.
156
156
157
157
### Supported and unsupported NSX RBAC roles
158
158
159
159
In an Azure VMware Solution deployment, the following VMware NSX predefined RBAC roles are supported with LDAP integration:
160
160
161
161
- Auditor
162
-
-Cloudadmin
162
+
-Cloud admin
163
163
- LB Admin
164
164
- LB Operator
165
165
- VPN Admin
@@ -173,10 +173,10 @@ Unlike on-premises deployment, not all predefined NSX RBAC roles are supported w
173
173
- NetX Partner Admin
174
174
- GI Partner Admin
175
175
176
-
You can create custom roles in NSX with permissions lesser than or equal to CloudAdmin role created by Microsoft. Following are examples on how to create a supported 'Network Admin' and 'Security Admin' role.
176
+
You can create custom roles in NSX with permissions lesser than or equal to the Cloud admin role created by Microsoft. Following are examples on how to create a supported 'Network Admin' and 'Security Admin' role.
177
177
178
178
> [!NOTE]
179
-
> Custom role creation fails if you assign a permission not allowed by CloudAdmin role.
179
+
> Custom role creation fails if you assign a permission not allowed by the Cloud admin role.
180
180
181
181
#### Create 'AVS network admin' role
182
182
@@ -218,7 +218,7 @@ You can create custom roles in NSX with permissions lesser than or equal to Clou
218
218
> The VMware NSX custom role doesn't support the VMware NSX Traceflow feature. The recommendation is to assign the **Auditor** role to the user along with the custom role to enable Traceflow feature for that user.
219
219
220
220
> [!NOTE]
221
-
> VMware Aria Operations Automation integration with the NSX component of the Azure VMware Solution requires the 'auditor' role to be added to the user with the NSX Manager cloudadmin role.
221
+
> VMware Aria Operations Automation integration with the NSX component of the Azure VMware Solution requires the 'auditor' role to be added to the user with the NSX Manager Cloud admin role.
0 commit comments