Group Assignments
DOCUMENT CATEGORY: Runbook
SCOPE: Active Directory group membership
PURPOSE: Map accounts to security groups
MASTER REFERENCE: Microsoft Learn - AD Prerequisites
Status: Active
Overview
📋 Optional Step: Group assignments are only required if you created optional security groups in Step 2.
Map accounts to security groups created in Step 2.
The active directory information in these documents should have been decided in the planning phase and discovery phases. These are just examples. Please update your scripts with the right OU information, right security groups, DNS, etc.
Prerequisites
- Security groups created (Step 2)
- Service and admin accounts created (Step 4)
- Domain admin access for group management
Values from infrastructure.yml
The script reads these keys from infrastructure.yml (schema 5). Each key, with its type, default and example, is in the variables reference.
scenario.identity, identity.active_directory.domain_fqdn
identity.active_directory.security_groups[].name, .members
Procedures
- Active Directory Users and Computers
- Orchestrated Script
- Open Active Directory Users and Computers.
- For each group below, right-click → Properties → Members → Add the listed accounts/groups:
| Security Group | Members to Add |
|---|---|
| SG-AzureLocal-Administrators | Break-glass admin, enterprise admin group |
| SG-AzureLocal-Operations | Operations team group |
| SG-AzureLocal-ReadOnly | Support / read-only group |
| SG-AzureLocal-WAC-Administrators | WAC admin group (may overlap with Administrators) |
| SG-AzureLocal-WAC-Users | Support / read-only group |
| SG-AzureLocal-HyperV-Administrators | Hyper-V admin group |
| SG-AzureLocal-Storage-Administrators | Storage admin group |
- Record membership snapshot in deployment tracking document.
PowerShell
When to use: Run the task from a management workstation or a pipeline. The script reads
infrastructure.ymland carries no values of its own.
Script
| Script | What it does |
|---|---|
scripts/deploy/03-onprem-readiness/phase-01-active-directory/task-05-group-assignments/powershell/Set-ADGroupMemberships.ps1 | Adds the members that identity.active_directory.security_groups[].members of infrastructure.yml lists to their Active Directory security groups. Supports -WhatIf. |
Requires: PowerShell 7.
Run
./Set-ADGroupMemberships.ps1 -InfrastructureFile ./infrastructure.yml -WhatIf
Verification
$groups = @(
"SG-AzureLocal-Administrators",
"SG-AzureLocal-Operations",
"SG-AzureLocal-ReadOnly",
"SG-AzureLocal-WAC-Administrators",
"SG-AzureLocal-WAC-Users",
"SG-AzureLocal-HyperV-Administrators",
"SG-AzureLocal-Storage-Administrators"
)
foreach ($g in $groups) {
Write-Host "`n$g" -ForegroundColor Cyan
Get-ADGroupMember $g -EA SilentlyContinue | Select-Object SamAccountName
}
Validation Checklist
- All 7 security groups have at least one member assigned
- Break-glass admin added to Administrators group
- Enterprise admin group mapped to Administrators
- Operations team mapped to Operations group
- Support/read-only group mapped to ReadOnly and WAC-Users
- WAC-Administrators, HyperV-Administrators, Storage-Administrators populated
- Membership snapshot documented in deployment tracking
Troubleshooting
Common Issues
"Member already exists": Add-ADGroupMember throws this when the member is already assigned. The scripts handle this with try/catch — safe to ignore.
"Cannot find an object with identity": The account or group name doesn't exist. Verify the SAM account name matches what was created in Steps 2 and 4.
Nested group membership not resolving: If you add a group as a member of another group, members of the nested group inherit permissions only if the application supports nested group evaluation. Azure Local and WAC both support this.
Support Resources
Data verified with internal source [Azure Local Provisioning Runbook] and Docusaurus documentation release note dated 2025-12-08.
Next Steps
After completing group assignments, proceed to Phase 09 - Enterprise Network Readiness Validation to validate network prerequisites, or review the Active Directory Preparation Overview for the complete process.
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.
Navigation
| ← Task 04: Service & Admin Accounts | ↑ Part 3: On-Premises Readiness | Phase 02: Enterprise Readiness → |
Version Control
| Version | Date | Author | Changes |
|---|---|---|---|
| 1.0 | 2026-01-31 | Azure Local Cloud | Initial document |
| 1.1 | 2026-03-03 | Azure Local Cloud | Standardized runbook format |
End of Task