Skip to main content
Version: Next

Service & Admin Accounts

Runbook Azure

DOCUMENT CATEGORY: Runbook SCOPE: Service and administrative accounts PURPOSE: Create break-glass and gMSA accounts MASTER REFERENCE: Microsoft Learn - AD Prerequisites

Status: Active


Overview

Create supplemental break-glass admin accounts and optional gMSA scaffold for enterprise environments.

What This Accomplishes

  • Break-glass administrative accounts for emergency access
  • Group Managed Service Accounts (gMSA) for secure service authentication
  • Secure password management and storage
  • Account configuration following security best practices
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

  • OU structure created (Step 1)
  • KDS Root Key replicated (from Step 1)
  • Domain admin access for account creation
  • Secure password storage solution (vault)

Variables from variables.yml

Variable PathTypeDescription
identity.active_directory.ad_service_accounts_ou_pathstringOU path for service account creation
identity.active_directory.ad_security_groups_ou_pathstringOU path for gMSA readers group
identity.accounts.account_lcm_usernamestringLCM account name (cluster ID extracted)
platform.kv_platform_namestringKey Vault name for break-glass password storage

Account Creation

Lifecycle Manager (LCM) user created in Step 1. Add break‑glass admin and optional gMSA scaffold.

  1. In Active Directory Users and Computers, inside instance OU create user: adm-AzureLocal-BreakGlass-<clusterId>.
  2. Set: Password never expires; User cannot change password; store password securely (vault).
  3. (Optional gMSA) After KDS root key replication completes, create gMSA via AD Administrative Center (if supported) targeting computer principals later.

Verification

Get-ADUser -LDAPFilter "(sAMAccountName=adm-AzureLocal-BreakGlass-*)" -SearchBase $OuPath | Select SamAccountName,Enabled
Get-ADServiceAccount -LDAPFilter "(sAMAccountName=gMSA-AzureLocal-*)" -SearchBase $OuPath | Select Name,Enabled

Notes

  • LCM user is created in Step 1; this step adds supplemental accounts
  • Break-glass accounts should have passwords stored securely in a vault
  • gMSA requires KDS root key replication to complete first
  • Use unique cluster IDs to avoid naming conflicts

Validation Checklist

  • Break-glass admin account created
  • Password stored securely in vault
  • Account properties configured correctly
  • gMSA created if required
  • Retrievers group configured for gMSA
  • Accounts enabled and accessible

Next Steps

After creating accounts, proceed to Task 5 - Group Assignments to assign accounts to security groups.

Troubleshooting

Common Issues

Account Creation Fails: Check OU permissions and naming policies.

gMSA Creation Fails: Ensure KDS root key has replicated.

Password Storage: Verify vault access and security policies.

Support Resources


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


Task 03: DNS Node A Records↑ Part 3: On-Premises ReadinessTask 05: Group Assignments →

Version Control

VersionDateAuthorChanges
1.02026-01-31Azure Local Cloud Azure Local CloudnologyInitial document
1.12026-03-03Azure Local Cloud Azure Local CloudnologyStandardized runbook format

End of Task