Phase 01: Active Directory Preparation
DOCUMENT CATEGORY: Runbook
SCOPE: Active Directory domain preparation
PURPOSE: Configure AD infrastructure for Azure Local
MASTER REFERENCE: Microsoft Learn - AD Prerequisites
Status: Active
Overview
Prepare the Active Directory domain infrastructure required for Azure Local deployment. This stage establishes the foundational identity services, organizational structure, and security configuration needed for cluster operations.
What This Stage Accomplishes
- Active Directory organizational preparation
- Organizational Unit (OU) structure creation
- Security groups for access control
- DNS configuration for cluster nodes
- Service and administrative accounts
- Group assignments and permissions
Prerequisites
- Windows Server domain controllers deployed
- Domain admin access
- DNS server configuration
- Azure Local requirements documentation
Microsoft Learn 2610 supports domain-joining the Azure Local machines before deployment (starting with version 2604; the deployment user must then be added to the local Administrators group). If the machines are not pre-joined they are joined automatically during portal deployment. Either way, the OU prepared here is where the computer objects belong.
Active Directory Preparation Steps
Task 1: OU Creation & Pre-Creation Artifacts
Create the foundational OU structure in Active Directory and the Azure Local deployment (LCM) user.
- Create MGMT OU on root domain
- Create sub-OUs: Admins, Operations, Security Groups, Servers, Services
- Create Clusters AzureLocal OUs
- Create the LCM deployment user with
New-HciAdObjectsPreCreation(username 1-20 characters, password of at least 14 characters, interactive logon and Log on as a batch job rights, OU path without& " ' < >and not at the top level of the domain) - A preflight check and the full Learn 2610 requirements are in the task
- No KDS root key is required for this task; it is only needed for the optional gMSA in Task 4
Task 2: Security Groups
Create the security groups for role-based access control of Azure Local operations. Each group is an entry of identity.active_directory.security_groups[] in infrastructure.yml: name, purpose, members and local_groups. You choose the names. A typical set:
Example name | local_groups on every node | Purpose |
|---|---|---|
sg-iic-azl-01-admins | Administrators | Full admin access to cluster nodes |
sg-iic-azl-01-operations | Remote Management Users, Remote Desktop Users | PowerShell remoting and RDP; no full admin |
sg-iic-azl-01-readonly | Remote Desktop Users, Performance Monitor Users, Event Log Readers | View only; cannot change configuration |
sg-iic-azl-01-hyperv-admins | Hyper-V Administrators, Remote Management Users | VM management through PowerShell remoting |
sg-iic-azl-01-storage-admins | Administrators | CSV and Storage Spaces Direct management |
Task 3: DNS Node A Records
Configure DNS A records for cluster node resolution.
- Create forward and reverse lookup zones
- Configure A records for cluster nodes
- If the DNS server does not support secure dynamic updates, also create Host A records for the cluster CNO and the cluster VCO before deployment
- Handle a disjoint namespace (append the DNS suffix on each node)
- Set up CNAME records for management endpoints
- Verify DNS resolution
Task 4: Service & Admin Accounts
Create supplemental service and administrative user accounts.
- Break-glass emergency admin account
- Optional gMSA (Group Managed Service Account) scaffold, including the KDS root key it needs (not mentioned in the Learn 2610 AD-preparation articles)
- Configure account properties and secure password storage
Note: The LCM deployment account is created in Task 01.
Task 5: Group Assignments
Assign users and service accounts to security groups.
- Add users to appropriate security groups
- Configure group memberships
- Assign group permissions
- Validate group policies
Validation Checklist
- Active Directory domain deployed and functional
- OU structure created and verified
- LCM deployment user meets the username, password and logon-right rules
- All security groups created
- DNS records configured and resolving (CNO and VCO records too if secure dynamic updates are not available)
- Service and admin accounts created
- Group assignments completed
- Domain controller replication verified
Next Steps
After completing Active Directory preparation, proceed to Phase 09 - Enterprise Network Readiness Validation to validate network prerequisites.
Support Resources
- Prepare Active Directory for Azure Local deployment
- Custom Active Directory configuration for Azure Local
- Active Directory Best Practices
- Contact Azure Local Cloud Azure Local Cloud team for assistance
Navigation
| ← Part 3: On-Premises Readiness | ↑ Part 3: On-Premises Readiness | Task 01: OU Creation → |
Version Control
| Version | Date | Author | Changes |
|---|---|---|---|
| 1.0 | 2025-06-01 | Azure Local Cloud | Initial document |
| 1.1 | 2026-03-03 | Azure Local Cloud | Standardized runbook format |
| 1.2 | 2026-11-08 | Azure Local Cloud | Aligned to Microsoft Learn 2610 (LCM user rules, CNO/VCO DNS records, KDS scoped to optional gMSA, view=azloc-2610 links) |