Skip to content

Commit 5fc7232

Browse files
authored
Updated "Configure role assignments" section
The "Configure role assignments for the VM" has incorrect instructions to apply the RBAC policy at the VM level. The roles "Virtual Machine Administrator Login" and "Virtual Machine User Login" also require access to the following resource types Microsoft.Network/virtualNetworks, Microsoft.Network/publicIPAddresses, Microsoft.Network/networkInterfaces, Microsoft.Network/loadBalancers in addition to Microsoft.Compute/virtualMachines. Assigning these roles at the VM level does not provide the required access for a user to sign in to the VM.
1 parent 731ca82 commit 5fc7232

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

articles/active-directory/devices/howto-vm-sign-in-azure-ad-windows.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -155,7 +155,7 @@ Now that you have created the VM, you need to configure Azure RBAC policy to det
155155
- **Virtual Machine User Login**: Users with this role assigned can log in to an Azure virtual machine with regular user privileges.
156156

157157
> [!NOTE]
158-
> To allow a user to log in to the VM over RDP, you must assign either the Virtual Machine Administrator Login or Virtual Machine User Login role. An Azure user with the Owner or Contributor roles assigned for a VM do not automatically have privileges to log in to the VM over RDP. This is to provide audited separation between the set of people who control virtual machines versus the set of people who can access virtual machines.
158+
> To allow a user to log in to the VM over RDP, you must assign either the Virtual Machine Administrator Login or Virtual Machine User Login role to the Resource Group containing the VM and its associated Virtual Network, Network Interface, Public IP Address or Load Balancer resources. An Azure user with the Owner or Contributor roles assigned for a VM do not automatically have privileges to log in to the VM over RDP. This is to provide audited separation between the set of people who control virtual machines versus the set of people who can access virtual machines.
159159
160160
There are multiple ways you can configure role assignments for VM:
161161

@@ -169,6 +169,8 @@ There are multiple ways you can configure role assignments for VM:
169169

170170
To configure role assignments for your Azure AD enabled Windows Server 2019 Datacenter VMs:
171171

172+
1. Select the **Resource Group** containing the VM and its associated Virtual Network, Network Interface, Public IP Address or Load Balancer resource.
173+
172174
1. Select **Access control (IAM)**.
173175

174176
1. Select **Add** > **Add role assignment** to open the Add role assignment page.
@@ -188,12 +190,12 @@ The following example uses [az role assignment create](/cli/azure/role/assignmen
188190

189191
``` AzureCLI
190192
$username=$(az account show --query user.name --output tsv)
191-
$vm=$(az vm show --resource-group myResourceGroup --name myVM --query id -o tsv)
193+
$rg=$(az group show --resource-group myResourceGroup --query id -o tsv)
192194
193195
az role assignment create \
194196
--role "Virtual Machine Administrator Login" \
195197
--assignee $username \
196-
--scope $vm
198+
--scope $rg
197199
```
198200

199201
> [!NOTE]

0 commit comments

Comments
 (0)