Skip to main content

Task 03: Security Groups Applied to Nodes

Runbook Cluster Deployment

Optional

DOCUMENT CATEGORY: Implementation Runbook
SCOPE: Azure Local post-deployment node configuration
PURPOSE: Add domain security groups to local Administrators and Remote Management Users on every cluster node to enforce least-privilege RBAC MASTER REFERENCE: Active Directory Security Groups

Status: Active

Add domain Active Directory security groups to the local Administrators and Remote Management Users groups on each cluster node. This enforces least-privilege access so domain identities inherit consistent cluster permissions without using shared local accounts.

Optional Task

This task is optional but strongly recommended for production environments. Without it, cluster node access relies on individual local accounts or Domain Admins only — neither of which provides the scoped, auditable access model required for production operations.


Security Group Requirements​

The following groups must exist in Active Directory before running this task (created in Phase 01 Task 02). Groups are the entries of identity.active_directory.security_groups[] in infrastructure.yml. Each entry's local_groups lists the local groups of every node it goes into. An entry with no local_groups is not applied to the nodes. For example:

Example namelocal_groups on every nodePurpose
sg-iic-azl-01-adminsAdministratorsFull admin access to cluster nodes
sg-iic-azl-01-operationsRemote Management Users, Remote Desktop UsersPowerShell remoting and RDP; no full admin
sg-iic-azl-01-readonlyRemote Desktop Users, Performance Monitor Users, Event Log ReadersView only; cannot change configuration
sg-iic-azl-01-hyperv-adminsHyper-V Administrators, Remote Management UsersVM management through PowerShell remoting
sg-iic-azl-01-storage-adminsAdministratorsCSV and Storage Spaces Direct management
Idempotent Operation

The script handles the "already a member" condition gracefully — re-running on a node where groups are already applied is safe and will not produce errors.


Values from infrastructure.yml​

The values for this task come from infrastructure.yml (schema 5). Every key, with its type, default and example, is in the variables reference.


Execution Options​

Local Users and Groups (lusrmgr.msc)​

When to use: Single node verification, confirming group membership, or manual remediation on one node

Prerequisites​

  • RDP or console access to each cluster node
  • Domain credentials with local admin rights

Procedure​

Repeat the following steps on every cluster node:

  1. Connect to the node via RDP or console

  2. Open Local Users and Groups:

  • Press Win + R, type lusrmgr.msc, press Enter
  • Navigate to Groups
  1. For each group that has local_groups, add the AD group to the corresponding local group:
AD Group (identity.active_directory.security_groups[].name)Local Group (local_groups)
sg-iic-azl-01-adminsAdministrators
sg-iic-azl-01-operationsRemote Management Users, Remote Desktop Users
sg-iic-azl-01-readonlyRemote Desktop Users, Performance Monitor Users, Event Log Readers
sg-iic-azl-01-hyperv-adminsHyper-V Administrators, Remote Management Users
sg-iic-azl-01-storage-adminsAdministrators

For each entry: double-click the local group → Add... → enter <domain-netbios>\<AD group name> → Check Names → OK

  1. Repeat on all remaining cluster nodes

Validation​

  • Every AD group with local_groups is present in its local groups on every node
  • PSRemoting works for a member of a group in Remote Management Users: Enter-PSSession -ComputerName <node>
  • RDP works for a member of a group in Remote Desktop Users

Validation Summary​

CheckCommandExpected Result
Administrators membershipGet-LocalGroupMember -Group 'Administrators' | Where-Object ObjectClass -eq 'Group'The groups whose local_groups name Administrators (for example sg-iic-azl-01-admins) listed on every node
Remote Management UsersGet-LocalGroupMember -Group 'Remote Management Users' | Where-Object ObjectClass -eq 'Group'The groups whose local_groups name it (for example sg-iic-azl-01-operations, sg-iic-azl-01-hyperv-admins) listed on every node
Remote Desktop UsersGet-LocalGroupMember -Group 'Remote Desktop Users' | Where-Object ObjectClass -eq 'Group'The groups whose local_groups name it (for example sg-iic-azl-01-operations, sg-iic-azl-01-readonly) listed on every node
Hyper-V AdministratorsGet-LocalGroupMember -Group 'Hyper-V Administrators' | Where-Object ObjectClass -eq 'Group'The groups whose local_groups name it (for example sg-iic-azl-01-hyperv-admins) listed on every node
PSRemoting testEnter-PSSession -ComputerName <node> -Credential <ops-user>Session opens without error

Troubleshooting​

IssueCauseResolution
Security group not listed in local group membershipGPO not applied or AD replication delayRun gpupdate /force on the node; verify AD group exists: Get-ADGroup -Identity <groupname>
PSRemoting test fails with access deniedUser not in Remote Management Users groupAdd the user's group to Remote Management Users: Add-LocalGroupMember -Group "Remote Management Users" -Member "<domain>\<group>"
Group membership shows SID instead of nameDomain controller unreachable for name resolutionVerify DC connectivity: Test-ComputerSecureChannel; check DNS resolution to domain controllers


Alternatives​

The procedures in this task use the methods shown in the tabs above. The toolkit is PowerShell 7 only and has no Bash scripts. A few tasks that act on Azure also have an Azure CLI script written in PowerShell. The script status page of the toolkit lists which task has which script.

PreviousUpNext
Task 02: Cluster QuorumPhase 06 IndexTask 04: SSH Connectivity

Version Control​

VersionDateAuthorChanges
1.0.02025-03-25Azure Local CloudInitial release