Study guide
2.1 Managing Users, Groups & Objects in Multi-Domain and Multi-Forest Environments
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.1 Managing Users, Groups & Objects in Multi-Domain and Multi-Forest Environments
Key Takeaways Explain This Topic AI
Group scopes dictate membership and permission boundaries: Domain Local groups aggregate permissions in their local domain, Global groups organize accounts sharing similar business roles, and Universal groups span across multiple domains in a forest.
The AGDLP (Single Domain) and AGUDLP (Multi-Domain) role-based nesting models decouple account lifecycle management from resource Access Control Lists (ACLs), preventing Kerberos token bloat and administrative overhead.
Universal group membership is cached in the Global Catalog (GC); frequent changes to Universal group membership cause forest-wide replication traffic, whereas Domain Local and Global group membership changes replicate only within their local domain.
The Active Directory Recycle Bin preserves deleted objects with all attributes intact for the duration of msDS-deletedObjectLifetime (default 180 days) without requiring an authoritative backup restore or domain controller reboot.
Cross-forest resource access relies on Foreign Security Principals (FSPs) created in the target domain's Domain Local groups, subject to SID filtering to prevent elevation of privilege attacks.
Last updated: August 2026
Managing Users, Groups & Objects in Multi-Domain and Multi-Forest Environments
In enterprise Active Directory Domain Services (AD DS) deployments, identity and access management rests upon the proper configuration and lifecycle governance of security principals . A security principal is any entity that can be authenticated by the operating system and assigned permissions to access resources. Security principals include user accounts, computer accounts, and security groups. Each security principal is assigned an immutable, unique Security Identifier (SID) composed of a domain identifier and a Relative Identifier (RID).
When designing and administering complex multi-domain and multi-forest architectures, systems administrators must master group scopes, nesting strategies, cross-boundary object mapping, administrative toolsets, and disaster recovery mechanisms such as the Active Directory Recycle Bin.
1. AD DS Security Principals & Group Types
Active Directory distinguishes between two fundamental group types:
Security Groups: Assigned a unique SID and can be listed in Discretionary Access Control Lists (DACLs) to grant or deny permissions to file shares, printers, registry keys, and Active Directory objects. Security groups can also be mail-enabled in Microsoft Exchange or Exchange Online environments for email distribution.
Distribution Groups: Lack a SID and cannot be used in DACLs. They are strictly utilized by email systems (such as Exchange Server) to send messages to collections of recipients. +-----------------------------------------------------------------------------------+
- | ACTIVE DIRECTORY GROUP SCOPES |
- | |
- | [DOMAIN LOCAL GROUP] |
- | - Purpose: Assign permissions to resources in the LOCAL domain. |
- | - Members: Users, Global Groups, Universal Groups from ANY domain in forest, |
- | plus trusted external forest accounts (Foreign Security Principals). |
- | - Scope of Permissions: Local domain only. |
- | |
- | [GLOBAL GROUP] |
- | - Purpose: Group users/computers sharing common business roles or job functions.|
- | - Members: Users and Global Groups from the SAME domain only. |
- | - Scope of Permissions: ANY domain in the forest or trusting external forests. |
- | |
- | [UNIVERSAL GROUP] |
- | - Purpose: Aggregate Global Groups across multiple domains for enterprise roles.|
- | - Members: Users, Global Groups, Universal Groups from ANY domain in forest. |
- | - Scope of Permissions: ANY domain in the forest or trusting external forests. |
- | - Replication: Membership is stored in the GLOBAL CATALOG (GC). |
- +-----------------------------------------------------------------------------------+
- 2. Group Scopes: Membership, Conversion & Replication Impact
The three group scopes— Domain Local , Global , and Universal —serve distinct architectural purposes in single-domain and multi-domain environments.
Comprehensive Group Scope Comparison
Scope Member Allowed From Where Group Can Be Assigned Permissions Global Catalog Replication
Domain Local Any domain in the forest, any trusted domain/forest (Users, Global Groups, Universal Groups, and other Domain Local groups from the same domain) Only in the domain where the Domain Local group exists Group object is replicated to GC; member list is NOT replicated
Global Only from the same domain where the Global group exists (Users, Computers, other Global groups from same domain) Any domain in the forest, any trusting domain/forest Group object is replicated to GC; member list is NOT replicated
Universal Any domain in the entire forest (Users, Global Groups, Universal Groups) Any domain in the forest, any trusting domain/forest Both group object AND member list are replicated to every GC
Group Scope Conversion Rules
Active Directory permits converting group scopes under specific constraints, provided the functional level is at least Windows 2000 Native or higher:
Global to Universal: Allowed only if the Global group is not a member of any other Global group.
Domain Local to Universal: Allowed only if the Domain Local group does not contain another Domain Local group.
Universal to Global: Allowed only if the Universal group does not contain another Universal group or members from another domain.
Universal to Domain Local: Allowed only if the Universal group is not a member of any other Domain Local group.
Global directly to Domain Local (or vice versa): Prohibited. Must first convert to Universal as an intermediate step.
Global Catalog and Replication Considerations
Because Universal group memberships are stored in the Global Catalog (GC) , any modification to a Universal group's membership causes the entire membership attribute to replicate to every Global Catalog server across the entire multi-domain forest .
In contrast, modifications to Global or Domain Local group memberships replicate only to domain controllers within the group's local domain. Therefore, placing individual user accounts directly into Universal groups creates unnecessary wide-area network (WAN) replication overhead. The best practice is to place users into Global groups, and nest those Global groups into Universal groups, as Global group membership changes do not trigger forest-wide GC replication.
Tip
Universal Group Membership Caching (UGMC): In branch offices with domain controllers that do not host the Global Catalog role, enable Universal Group Membership Caching (UGMC) on the branch site. During initial user logon, the local DC queries a remote GC for the user's Universal group memberships and caches the token locally, allowing subsequent logons even across WAN outages without requiring a full local GC deployment.
3. Group Nesting Strategies: AGDLP and AGUDLP
To enforce the principle of least privilege and streamline access governance, Microsoft establishes standardized role-based group nesting models: +-----------------------------------------------------------------------------------+
- | AGUDLP NESTING ARCHITECTURE (MULTI-DOMAIN) |
- | |
- | [A] Accounts --> User objects (e.g., alice@na.contoso.com) |
- | | |
- | v |
- | [G] Global Group --> Domain-specific role (e.g., G_NA_FinancialAuditors) |
- | | |
- | v |
- | [U] Universal Group--> Forest-wide role (e.g., U_Enterprise_Auditors) |
- | | |
- | v |
- | [DL] Domain Local --> Resource permission group (e.g., DL_FinanceShare_Read) |
- | | |
- | v |
- | [P] Permissions --> Assigned to Access Control List (ACL) on File Share |
- +-----------------------------------------------------------------------------------+
- AGDLP (Single-Domain Environments)
A (Accounts): User and computer accounts are created in their respective organizational units.
G (Global Groups): Accounts are placed into Global groups that represent business roles (e.g., G_MarketingStaff ).
DL (Domain Local Groups): Domain Local groups are created to represent specific access permissions on specific resources (e.g., DL_MarketingShare_Modify ).
P (Permissions): Permissions (Read, Modify, Full Control) are assigned to the Domain Local group on the resource's NTFS/Share DACL.
The Global group G_MarketingStaff is added as a member of DL_MarketingShare_Modify .
AGUDLP (Multi-Domain Forest Environments)
In multi-domain enterprises, the Universal group tier is added:
Accounts in Domain A are placed into Global Group A ( G_DomainA_Engineers ).
Accounts in Domain B are placed into Global Group B ( G_DomainB_Engineers ).
Both Global groups are nested into a single Universal Group ( U_Enterprise_Engineers ).
The Universal group is added to the Domain Local group in the resource domain ( DL_CadFiles_ReadWrite ).
Permissions are assigned exclusively to DL_CadFiles_ReadWrite .
Key Benefit: When an employee joins or leaves a team, administrators only update membership in the user's local Global group. Resource ACLs never need modification, preventing token bloat and eliminating cross-domain administrative churn.
4. Cross-Forest Object Administration & Security
When two separate Active Directory forests establish a trust relationship (e.g., Forest Trust), administrators can grant access to resources in Forest B for users located in Forest A.
Foreign Security Principals (FSPs)
When a user or group from a trusted external forest is added to a Domain Local group in the trusting domain, Active Directory creates a Foreign Security Principal (FSP) object in the CN=ForeignSecurityPrincipals,DC=domain,DC=com container. The FSP stores the external object's foreign SID.
SID History and SID Filtering
During domain migrations using tools such as the Active Directory Migration Tool (ADMT), user and group accounts are migrated to a new target domain while retaining their historical SIDs in the sIDHistory attribute. This allows users to retain access to legacy resources without immediate ACL re-permissioning.
Warning
SID Filtering on Forest Trusts: By default, cross-forest trusts enable SID Filtering (quarantining). SID Filtering strips any foreign SID from the Kerberos authorization data (PAC) that does not match the relative domain identifier of the trusted domain. This prevents malicious domain administrators in a trusted domain from injecting well-known privileged SIDs (such as Enterprise Admins S-1-5-21-...-519 ) into a user's sIDHistory to gain unauthorized access in the trusting forest.
5. Active Directory Administrative Center (ADAC) & PowerShell Automation
The Active Directory Administrative Center (ADAC) provides an administrative GUI built entirely on top of the ActiveDirectory PowerShell module. ADAC introduces advanced capabilities:
PowerShell History Viewer: Displays the exact PowerShell cmdlets generated by every GUI operation in ADAC, providing an ideal mechanism for building automation scripts.
Dynamic Access Control (DAC): Enables centralized claim-based authorization policies.
Fine-Grained Password Policies (FGPP): Allows creating and assigning Password Settings Objects (PSOs) to specific users and global security groups without requiring separate domain boundaries.
- Core PowerShell ActiveDirectory Cmdlets # 1. Create a new department User account
- New-ADUser -Name "Marcus Vance" `
- SamAccountName "mvance" `
- UserPrincipalName "mvance@contoso.com" `
- AccountPassword (ConvertTo-SecureString "P@ssw0rd2026!" -AsPlainText -Force) `
- Enabled $true `
- Department "Finance" `
- Path "OU=Finance,OU=Users,DC=contoso,DC=com"
- # 2. Create Global and Domain Local groups
- New-ADGroup -Name "G_Finance_Users" `
- GroupScope Global `
- GroupCategory Security `
- Path "OU=Groups,DC=contoso,DC=com"
- New-ADGroup -Name "DL_LedgerShare_Modify" `
- GroupScope DomainLocal `
- GroupCategory Security `
- Path "OU=Groups,DC=contoso,DC=com"
- # 3. Nest user into Global Group, and Global Group into Domain Local Group
- Add-ADGroupMember -Identity "G_Finance_Users" -Members "mvance"
- Add-ADGroupMember -Identity "DL_LedgerShare_Modify" -Members "G_Finance_Users"
- # 4. Enumerate recursive group membership
- Get-ADGroupMember -Identity "DL_LedgerShare_Modify" -Recursive | Select-Object Name, SamAccountName
- # 5. Identify inactive accounts for security auditing
- Search-ADAccount -AccountInactive -TimeSpan (New-TimeSpan -Days 90) -UsersOnly | `
- Select-Object Name, LastLogonDate, DistinguishedName
- 6. Active Directory Recycle Bin Lifecycle
The Active Directory Recycle Bin allows administrators to recover deleted objects without restoring backups from system state media or restarting domain controllers in Directory Services Restore Mode (DSRM). +-----------------------------------------------------------------------------------+
- | ACTIVE DIRECTORY OBJECT DELETION LIFECYCLE |
- | |
- | [1. LIVE OBJECT] |
- | | |
- | | Object is deleted by administrator |
- | v |
- | [2. DELETED OBJECT STATE] |
- | - Moved to 'CN=Deleted Objects,DC=contoso,DC=com' |
- | - Retains ALL attributes, group memberships, and SIDs |
- | - Remains for msDS-deletedObjectLifetime (Default: 180 days) |
- | - CAN BE RESTORED WITH ONE POWERSHELL COMMAND |
- | | |
- | | msDS-deletedObjectLifetime expires |
- | v |
- | [3. RECYCLED OBJECT STATE] |
- | - Most attributes are stripped (only GUID, SID, isRecycled remain) |
- | - Stays in CN=Deleted Objects for tombstoneLifetime (Default: 180 days) |
- | - CANNOT BE RESTORED VIA RECYCLE BIN (Requires authoritative backup) |
- | | |
- | | tombstoneLifetime expires |
- | v |
- | [4. PERMANENT PHYSICAL REMOVAL] |
- | - Garbage collection process removes record from NTDS.dit database |
- +-----------------------------------------------------------------------------------+
- Enabling and Operating AD Recycle Bin
To enable the AD Recycle Bin, the forest functional level must be at least Windows Server 2008 R2 or higher. Enabling the feature is irreversible. # Enable AD Recycle Bin across the forest
- Enable-ADOptionalFeature -Identity "Recycle Bin Feature" `
- Scope ForestOrConfigurationSet `
- Target "contoso.com"
- # Search for deleted user objects
- Get-ADObject -Filter 'isDeleted -eq $true -and name -like "Marcus*"' `
- IncludeDeletedObjects `
- Properties distinguishedName, lastKnownParent, sAMAccountName
- # Restore deleted object with full original attributes and group memberships
- Get-ADObject -Filter 'isDeleted -eq $true -and sAMAccountName -eq "mvance"' `
- IncludeDeletedObjects | `
- Restore-ADObject