Skip to main content

Security Groups

Runbook Azure

DOCUMENT CATEGORY: Runbook
SCOPE: Active Directory security groups
PURPOSE: Create role-based access control groups
MASTER REFERENCE: Microsoft Learn - AD Prerequisites

Status: Active

Overview​

Create optional security groups for role-based access control in Azure Local administration.

What This Accomplishes​

  • Role-based access control for Azure Local operations
  • Delegated administration capabilities
  • Separation of duties for different administrative roles
info

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 OU exists in Active Directory
  • Domain admin access for group creation
  • Understanding of group scope and security requirements

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.


Security Group Model​

Each group is an entry of identity.active_directory.security_groups[] in infrastructure.yml: name, purpose, members (filled in Task 05) and local_groups (applied to the nodes after the deployment). You choose the names; put the cluster in the name so groups stay unique per cluster in the same domain. The earlier object-by-role form (security_groups_by_role, with org_prefix and cluster_id) is removed from the registry.

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
identity:
active_directory:
security_groups:
- { name: "sg-iic-azl-01-admins", purpose: "Administrators of the instance", local_groups: ["Administrators"] }
- { name: "sg-iic-azl-01-operations", purpose: "PowerShell remoting and RDP", local_groups: ["Remote Management Users", "Remote Desktop Users"] }
- { name: "sg-iic-azl-01-readonly", purpose: "View only", local_groups: ["Remote Desktop Users", "Performance Monitor Users", "Event Log Readers"] }
- { name: "sg-iic-azl-01-hyperv-admins", purpose: "VM management", local_groups: ["Hyper-V Administrators", "Remote Management Users"] }
- { name: "sg-iic-azl-01-storage-admins", purpose: "Storage and CSV management", local_groups: ["Administrators"] }

Security Group Creation​

Core Azure Local instance security groups in the enterprise Security Groups OU (pre-determined OU for security groups).

  1. Open Active Directory Users and Computers.
  2. Navigate to the OU for the groups (the toolkit script uses the dedicated OU of the instance, identity.active_directory.ou_path, for example OU=iic-azl-01,OU=AzureLocal,DC=improbability,DC=cloud).
  3. Right‑click OU → New → Group.
  4. Create each group of identity.active_directory.security_groups[] (Global / Security), with its name, for example:
  • sg-iic-azl-01-admins
  • sg-iic-azl-01-operations
  • sg-iic-azl-01-readonly
  • sg-iic-azl-01-hyperv-admins
  • sg-iic-azl-01-storage-admins
  1. For each group: Properties → Protection: enable "Protect object from accidental deletion".
  2. Document intended membership policy (who owns adds/removals).

Verification​

# The OU of identity.active_directory.ou_path; the names of identity.active_directory.security_groups[]
$GroupsOuDn = "OU=iic-azl-01,OU=AzureLocal,DC=improbability,DC=cloud"
Get-ADGroup -LDAPFilter "(cn=sg-iic-azl-01-*)" -SearchBase $GroupsOuDn | Select-Object Name

Validation Checklist​

  • Security Groups OU accessible
  • All required security groups created
  • Groups configured as Global/Security scope
  • Protection from accidental deletion enabled
  • Membership policies documented

Next Steps​

After creating security groups, proceed to Task 3 - DNS Node A Records for optional DNS record creation.

Troubleshooting​

Common Issues​

Group Creation Fails: Check permissions and OU access.

Scope Configuration: Ensure Global scope is appropriate for your domain structure.

Protection Setting: Verify "Protect object from accidental deletion" is enabled.

Support Resources​


Data verified with internal source [Azure Local Provisioning Runbook] and Docusaurus documentation release note dated 2025-12-08.



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.

← Task 01: OU Creation↑ Part 3: On-Premises ReadinessTask 03: DNS Node A Records →

Version Control​

VersionDateAuthorChanges
1.02026-01-31Azure Local CloudInitial document
1.12026-03-03Azure Local CloudStandardized runbook format

End of Task