Study guide

2.4 Creating & Managing Users, Groups and Organizational Units at Scale

Administering Windows Server Hybrid Core Infrastructure AZ-800

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

About Exam AZ-800: Format, Scoring & the September 2026 Retirement

2 Chapter 1: Active Directory Domain Services Architecture & Deployment

1.1 Deploying & Managing Domain Controllers On-Premises 1.2 Domain Controllers in Azure IaaS & Virtualized DC Cloning 1.3 Read-Only Domain Controllers (RODCs) & Password Replication Policies 1.4 Flexible Single Master Operation (FSMO) Roles & Troubleshooting 1.5 Active Directory Sites, Subnets & Site Link Topology 1.6 AD DS Replication: Topology Generation, Convergence & Diagnostics 1.7 Forest and Domain Trust Relationships

3 Chapter 2: AD DS Security Principals, Service Accounts & Domain Join

2.1 Managing Users, Groups & Objects in Multi-Domain and Multi-Forest Environments 2.2 Service Account Types & Group Managed Service Accounts (gMSA) 2.3 Joining Windows Server to AD DS, Microsoft Entra Domain Services & Microsoft Entra ID 2.4 Creating & Managing Users, Groups and Organizational Units at Scale

4 Chapter 3: Hybrid Identity & Microsoft Entra Integration

3.1 Microsoft Entra Connect Sync Architecture, Installation & Filtering 3.2 SourceAnchor, Synchronization Rules & Microsoft Entra Connect Health 3.3 Microsoft Entra Cloud Sync & Disconnected Multi-Forest Topologies 3.4 Hybrid Authentication Methods & Staged Rollout 3.5 Microsoft Entra Domain Services 3.6 Integrating Microsoft Entra ID, AD DS & Entra Domain Services: Choosing an Architecture

5 Chapter 4: Group Policy in AD DS and Hybrid Environments

4.1 Group Policy Architecture & Processing Order (LSDOU) 4.2 Group Policy Filtering, Loopback Processing & Client-Side Extensions 4.3 Group Policy Preferences, Item-Level Targeting & Central Store 4.4 Group Policy in Microsoft Entra Domain Services & Fine-Grained Password Policies

6 Chapter 5: Remote Server Management in Hybrid Environments

5.1 Windows Admin Center (WAC) Deployment On-Premises and in Azure 5.2 PowerShell Remoting, WinRM & the Kerberos Double-Hop Problem 5.3 Just Enough Administration (JEA) for Constrained PowerShell Endpoints 5.4 OpenSSH on Windows Server & PowerShell Remoting over SSH 5.5 Secure RDP Access, Remote Desktop Gateway & Azure Bastion

7 Chapter 6: Hybrid Management with Azure Arc and Azure Services

6.1 Azure Arc-Enabled Servers Architecture & Onboarding 6.2 Azure Machine Configuration & VM Extensions on Arc Servers 6.3 Azure Update Manager: Assessment, Maintenance Configurations & Dynamic Scoping 6.4 Azure Automation for Hybrid Workloads: Runbooks & Hybrid Runbook Workers

8 Chapter 7: Hyper-V Virtualization & Virtual Machine Configuration

7.1 Hyper-V Type 1 Architecture, Installation & Hardware Prerequisites 7.2 VM Generations, Secure Boot, vTPM, Enhanced Session Mode & Direct VM Access 7.3 Compute, Dynamic Memory & Hardware Acceleration 7.4 VM Resource Controls, CPU Groups & Host Compute Partitioning 7.5 Hyper-V Virtual Hard Disks & Checkpoint Management 7.6 Hyper-V Virtual Switches, NIC Teaming & Switch Embedded Teaming (SET) 7.7 Integration Services, Guest Components & Time Synchronization

9 Chapter 8: Hyper-V High Availability, Security & Containers

8.1 Hyper-V Failover Clustering & Cluster Shared Volumes (CSV) 8.2 Hyper-V Replica & Azure Site Recovery (ASR) 8.3 Guarded Fabric & Shielded Virtual Machines 8.4 Windows Server Container Hosts, Isolation Models & Images 8.5 Managing Container Instances & Linux Containers with WSL 8.6 Windows Container Networking & AKS Enabled by Azure Arc 8.7 Managing Container Images, Tags & Azure Container Registry

10 Chapter 9: Azure IaaS Virtual Machine Administration

9.1 Azure VM Sizing, Series Selection & Managed Disk Tiers 9.2 Azure VM Host Caching, Disk Bursting, Ephemeral OS Disks & Disk Operations 9.3 Azure VM High Availability: Availability Sets, Zones & Proximity Placement Groups 9.4 Virtual Machine Scale Sets, Autoscale & Azure Dedicated Hosts 9.5 Azure VM Networking, NSGs & Connectivity

11 Chapter 10: Hybrid DNS Infrastructure & Name Resolution

10.1 Active Directory-Integrated DNS Architecture, Dynamic Updates & Zone Types 10.2 DNS Records, Aging & Scavenging and the GlobalNames Zone 10.3 DNS Forwarding, Conditional Forwarding & Azure DNS Zone Integration 10.4 Hybrid Name Resolution with Azure DNS Private Resolver 10.5 Windows Server DNS Policies & DNSSEC

12 Chapter 11: IP Addressing, DHCP & IPAM Management

11.1 DHCP Server Role, the DORA Lifecycle & Active Directory Authorization 11.2 DHCP Scopes, Option Hierarchy, Reservations & Relay Agents 11.3 DHCP High Availability & Failover Configurations 11.4 IP Address Management (IPAM) Deployment & Auditing 11.5 Resolving IP Address Issues in Hybrid Environments

13 Chapter 12: Hybrid Network Connectivity, Remote Access & Private Access

12.1 Remote Access Role, VPN Protocols & Site-to-Site VPN to Azure 12.2 Network Policy and Access Services (NPAS), RADIUS & Policy Processing 12.3 Azure Network Adapter & Azure Extended Network 12.4 Web Application Proxy & Microsoft Entra Application Proxy 12.5 Microsoft Entra Private Access & Global Secure Access 12.6 Azure Relay & Hybrid Connections

14 Chapter 13: File Services, DFS, SMB & Azure File Sync

13.1 Windows Server File Share Access, NTFS Permissions & Access-Based Enumeration 13.2 File Server Resource Manager: Quotas, File Screens & Storage Reports 13.3 DFS Namespaces (DFS-N) & DFS Replication (DFS-R) 13.4 BranchCache: Distributed Cache and Hosted Cache Modes 13.5 Modern SMB Protocols, SMB Multichannel & SMB over QUIC 13.6 Azure File Shares, Tiers & Hybrid Permissions 13.7 Azure File Sync, Cloud Tiering & Monitoring 13.8 Migrating DFS Namespaces & DFS Replication to Azure File Sync

15 Chapter 14: Windows Server Storage Infrastructure & High Availability

14.1 Disk Partitioning, Volumes & Enterprise File Systems (NTFS vs ReFS) 14.2 Data Deduplication Architecture, Usage Types & Management 14.3 Storage Spaces & Storage Spaces Direct (S2D) 14.4 Storage Replica & Storage Quality of Service 14.5 iSCSI Target Server, IQNs, CHAP Authentication & Multipath I/O

2.4 Creating & Managing Users, Groups and Organizational Units at Scale

Key Takeaways Explain This Topic AI

The default CN=Users and CN=Computers objects are containers, not organizational units, so Group Policy Objects cannot be linked to them; redirusr and redircmp redirect new object creation to real OUs.

New-ADUser creates a disabled account unless -Enabled $true and an -AccountPassword SecureString are supplied in the same command.

Search-ADAccount surfaces stale, locked-out, disabled, expired and password-expired accounts without writing a custom LDAP filter.

Alternative UPN suffixes are added at the forest level with Set-ADForest -UPNSuffixes before they can be selected on a user account.

The Active Directory Administrative Center PowerShell History pane emits the exact cmdlet for any action performed in the GUI, which is the fastest route from a one-off click to a repeatable script.

Last updated: August 2026

Creating & Managing Users, Groups and Organizational Units at Scale

The previous sections covered what security principals are and how their scopes behave across domains. This one covers the operational reality: an administrator provisions dozens of accounts from a human-resources export, restructures organizational units so that Group Policy and delegated administration both land where they should, and periodically hunts down the accounts that stopped being used two years ago. Every one of those tasks is testable, and every one of them has a specific tool.

1. Organizational Unit Design: Containers Are Not OUs

An organizational unit (OU) is a directory object designed to hold other objects for two purposes only: Group Policy linkage and delegation of administration . It has nothing to do with permissions on files or membership in groups.

The distinction that trips people up is that a brand-new domain does not place objects in OUs. CN=Users and CN=Computers are containers , a different object class, and they carry a hard limitation:

Object Class GPO can be linked? Can be renamed or moved?

  • CN=Users , CN=Computers , CN=Builtin container No No
  • OU=Corp , OU=Finance organizationalUnit Yes Yes
  • OU=Domain Controllers organizationalUnit Yes Should not be moved

Because a domain join with no target specified drops the computer object into CN=Computers , a freshly joined server receives no OU-linked Group Policy — only domain-linked and site-linked policy. The fix is to redirect the default creation targets, which requires a Windows Server 2003 or higher domain functional level: :: Redirect the default creation containers to real OUs so GPOs apply to new objects

  • redircmp "OU=Servers,OU=Corp,DC=corp,DC=contoso,DC=com"
  • redirusr "OU=Staff,OU=Corp,DC=corp,DC=contoso,DC=com"

Two design patterns dominate: a geographic top level (OU=EMEA, OU=AMER) when administration is delegated by region, and a functional top level (OU=Finance, OU=Engineering) when policy differs by role. Most production forests use a hybrid — geography for delegation, function beneath it for policy. Depth is not free: every additional OU level is another link in the LSDOU processing chain and another place for an inheritance block to hide.

Protecting Objects from Accidental Deletion

Active Directory Users and Computers offers a "Protect object from accidental deletion" checkbox, and Active Directory Administrative Center selects it by default on new OUs. It is not a special flag — it writes an explicit Deny access control entry for Delete and Delete Subtree against Everyone on the object. That is why a Domain Admin who deletes a protected OU gets Access Denied, and why the protection must be removed before a legitimate restructure: # Find every unprotected OU and protect it

  • Get-ADOrganizationalUnit -Filter * -Properties ProtectedFromAccidentalDeletion |
  • Where-Object { -not $_.ProtectedFromAccidentalDeletion } |
  • Set-ADObject -ProtectedFromAccidentalDeletion $true
  • # Temporarily unprotect a single OU so it can be moved
  • Set-ADObject -Identity 'OU=Legacy,DC=corp,DC=contoso,DC=com' -ProtectedFromAccidentalDeletion $false

Move-ADObject -Identity 'OU=Legacy,DC=corp,DC=contoso,DC=com' -TargetPath 'OU=Archive,DC=corp,DC=contoso,DC=com'

2. Delegation of Control

Delegation is what makes OUs worth designing. The Delegation of Control Wizard in Active Directory Users and Computers writes access control entries onto the OU's ACL, granting a group the right to perform specific operations on specific object classes within that OU — reset passwords on user objects, create and delete computer objects, modify group membership — without any membership in Domain Admins.

For anything the wizard's canned task list does not cover, or for auditing what has already been granted, use dsacls : :: Show every ACE currently on the OU

dsacls "OU=Branch-Helpdesk,DC=corp,DC=contoso,DC=com"

  • :: Grant a group the right to reset passwords and force password change at next logon
  • dsacls "OU=Branch-Helpdesk,DC=corp,DC=contoso,DC=com" /I:S ^
  • /G "CORP\Tier1-HelpDesk:CA;Reset Password;user"
  • dsacls "OU=Branch-Helpdesk,DC=corp,DC=contoso,DC=com" /I:S ^
  • /G "CORP\Tier1-HelpDesk:WP;pwdLastSet;user"

Tip

Delegated rights are inherited down the OU tree, so a delegation applied at OU=Corp reaches every child OU. Moving a user object into a delegated OU therefore silently hands that object to a different administrative team — which is precisely why "move the account to the branch OU" is never a purely cosmetic change.

3. Bulk Provisioning and Attribute Management

The reference pattern for provisioning is a CSV export from the authoritative source system piped through New-ADUser . Two details cause most failures: the password must be a SecureString , and an account created without -Enabled $true is created disabled . # newhires.csv columns: FirstName,LastName,SamAccountName,Department,Title,Manager

$DefaultPwd = ConvertTo-SecureString 'Tr@nsientP@ss2026!' -AsPlainText -Force

  • Import-Csv -Path 'C:\HR\newhires.csv' | ForEach-Object {
  • New-ADUser `
  • Name "$($_.FirstName) $($_.LastName)" `
  • GivenName $_.FirstName `
  • Surname $_.LastName `
  • SamAccountName $_.SamAccountName `
  • UserPrincipalName "$($_.SamAccountName)@corp.contoso.com" `
  • Path 'OU=Staff,OU=Corp,DC=corp,DC=contoso,DC=com' `
  • Department $_.Department `
  • Title $_.Title `
  • AccountPassword $DefaultPwd `
  • ChangePasswordAtLogon $true `
  • Enabled $true
  • }
  • # Bulk-add the new hires to a role group in one operation
  • Add-ADGroupMember -Identity 'GG_Staff_AllUsers' `

-Members (Get-ADUser -Filter { Department -eq 'Finance' } -SearchBase 'OU=Staff,OU=Corp,DC=corp,DC=contoso,DC=com')

Alternative sign-in suffixes must exist at the forest level before a user object can use one: Set-ADForest -Identity 'contoso.com' -UPNSuffixes @{ Add = 'contoso.co.uk','fabrikam-eu.com' }

  • Get-ADUser -Filter { Department -eq 'EMEA-Sales' } |
  • Set-ADUser -UserPrincipalName { "$($_.SamAccountName)@contoso.co.uk" }
  • 4. Finding the Accounts That Should Not Exist

Stale accounts are both an audit finding and an attack surface. Search-ADAccount answers the common questions without hand-written LDAP filters:

  • Command Returns
  • Search-ADAccount -AccountInactive -TimeSpan 90.00:00:00 -UsersOnly User accounts with no logon in 90 days
  • Search-ADAccount -LockedOut Currently locked-out accounts
  • Search-ADAccount -PasswordExpired Accounts whose password has expired
  • Search-ADAccount -AccountDisabled -ComputersOnly Disabled computer objects

Search-ADAccount -AccountExpiring -TimeSpan 14.00:00:00 Accounts expiring in the next 14 days # Disable and move stale accounts rather than deleting them outright

  • Search-ADAccount -AccountInactive -TimeSpan 120.00:00:00 -UsersOnly |
  • Where-Object { $_.Enabled } |
  • ForEach-Object {
  • Disable-ADAccount -Identity $_.DistinguishedName
  • Move-ADObject -Identity $_.DistinguishedName -TargetPath 'OU=Disabled,OU=Corp,DC=corp,DC=contoso,DC=com'
  • }

Two properties behave unintuitively when auditing: LastLogon is not replicated and is only accurate on the domain controller that processed the logon, whereas LastLogonTimestamp is replicated but is deliberately imprecise — it updates only when the value is older than roughly 9 to 14 days. For inactivity reporting, LastLogonTimestamp (which is what Search-ADAccount -AccountInactive consumes) is the correct attribute; for a precise answer you must query every domain controller.

Tip

Open Active Directory Administrative Center , expand the Windows PowerShell History pane at the bottom, and perform the action in the GUI. ADAC prints the exact cmdlet and parameters it executed — the quickest way to convert an unfamiliar one-off task into a script you can schedule.