Study guide

4.4 Group Policy in Microsoft Entra Domain Services & Fine-Grained Password Policies

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

4.4 Group Policy in Microsoft Entra Domain Services & Fine-Grained Password Policies

Key Takeaways Explain This Topic AI

Microsoft Entra Domain Services provides two built-in Group Policy Objects, 'AADDC Computers GPO' and 'AADDC Users GPO', which members of the AAD DC Administrators group edit in place from a domain-joined management VM.

Entra Domain Services managed domains use a flat OU structure: custom Organizational Units are created at the domain root and custom GPOs are linked to them, never nested beneath 'AADDC Computers' or 'AADDC Users'.

Management of Entra Domain Services GPOs is performed remotely using RSAT (Group Policy Management Console) from a domain-joined Azure IaaS VM by members of the 'AAD DC Administrators' group.

Fine-Grained Password Policies (FGPP) enable multiple distinct password and account lockout baselines within a single Active Directory domain using Password Settings Objects (PSOs) stored in the Password Settings Container.

PSO precedence rules dictate that direct user assignments always override group assignments, lower integer values in msDS-PasswordSettingsPrecedence win among group policies, and ties are resolved by the lowest objectGUID.

Last updated: August 2026

Group Policy in Microsoft Entra Domain Services & Fine-Grained Password Policies

Modern hybrid enterprises frequently combine on-premises Active Directory Domain Services (AD DS) with Microsoft Entra Domain Services (a managed PaaS domain service providing Kerberos, NTLM, LDAP, and Group Policy compatibility in Azure). While traditional on-premises AD DS grants enterprise administrators full domain-level autonomy, Entra Domain Services enforces strict administrative boundaries to maintain managed platform integrity.

Simultaneously, securing identity infrastructure requires granular password and lockout governance. Traditional AD DS enforced a single domain-wide password policy via the Default Domain Policy. Fine-Grained Password Policies (FGPP) overcome this constraint by introducing Password Settings Objects (PSOs) , allowing organizations to enforce strict password lengths and lockout thresholds for privileged accounts while maintaining standard baselines for general users.

1. Group Policy in Microsoft Entra Domain Services

In a Microsoft Entra Domain Services managed domain, domain controllers are deployed, patched, and managed entirely by Microsoft as a platform service. Administrators do not have access to domain controller VMs via RDP or SSH and are never granted Domain Admins or Enterprise Admins credentials. +-----------------------------------------------------------------------------------+

  • | ENTRA DOMAIN SERVICES OU LAYOUT & GPO PERMISSION BOUNDARIES |
  • | |
  • | [Managed Domain Root: DC=aadds,DC=contoso,DC=com] |
  • | * Managed DCs: no sign-in. Never Domain / Enterprise / Schema Admins * |
  • | | Managed domains are FLAT: every OU below hangs off the root. |
  • | | |
  • | +-- [Built-in: AADDC Computers] <- domain-joined VMs land here |
  • | | Linked GPO: AADDC Computers GPO (edited in place) |
  • | | |
  • | +-- [Built-in: AADDC Users] <- users/groups synced from Entra ID |
  • | | Linked GPO: AADDC Users GPO (edited in place) |
  • | | Objects here CANNOT be moved into a custom OU. |
  • | | |
  • | +-- [Custom OU: OU=WebServers] <- created AT THE ROOT, not nested |
  • | | Linked GPO: Custom-WebServer-GPO (created + linked by admins) |
  • | | |
  • | +-- [Custom OU: OU=AppServiceAccounts] |
  • | Linked GPO: Custom-SvcAcct-GPO |
  • +-----------------------------------------------------------------------------------+

Built-In GPOs & Delegation:

Entra Domain Services provides two built-in GPOs linked to the two default root containers:

AADDC Computers GPO : Linked to the OU=AADDC Computers container. Configures baseline computer settings for domain-joined VMs.

AADDC Users GPO : Linked to the OU=AADDC Users container. Configures baseline user environment settings.

Members of the AAD DC Administrators group have delegated permissions to edit these two built-in GPOs.

Platform Constraints & Custom GPO Linking:

No domain controller access: Microsoft deploys, patches, and owns the two managed DCs. You cannot sign in to them to perform management tasks, and AAD DC Administrators is never granted Domain Admins , Enterprise Admins , or Schema Admins . Every task runs remotely from a domain-joined management VM.

Custom OUs live at the domain root: Managed domains use a flat OU structure . The documented flow creates a custom OU directly under the domain — OU=WebServers,DC=aadds,DC=contoso,DC=com — and not as a child of OU=AADDC Computers or OU=AADDC Users .

Custom GPOs: Members of AAD DC Administrators hold Group Policy administration privileges: they edit the two built-in GPOs in place, and they create custom GPOs and link them to the custom OUs they create.

Objects cannot leave AADDC Users : Users and groups synchronized from Microsoft Entra ID stay in AADDC Users . Only accounts and resources created directly in the managed domain — typically application service accounts — can be moved into a custom OU.

Warning

Exam trap: the tempting answer is to nest a child OU beneath OU=AADDC Computers and link the GPO there. The documented model is the opposite — create the custom OU at the domain root and link the custom GPO to it. Equally, an on-premises OU hierarchy and on-premises GPOs are never synchronized into a managed domain.

2. Remote Management Workflow via RSAT

Because direct access to managed domain controllers is restricted, all Group Policy authoring, OU configuration, and DNS management in Microsoft Entra Domain Services must be performed remotely from a domain-joined management workstation or Azure IaaS VM. # Step 1: Install Remote Server Administration Tools (RSAT) on Azure IaaS Management VM

Install-WindowsFeature -Name RSAT-AD-Tools, GPMC -IncludeManagementTools

  • # Step 2: Verify Group Policy Management Module is Available
  • Get-Command -Module GroupPolicy

# Step 3: Create a Custom OU AT THE DOMAIN ROOT. Managed domains are flat --

# do NOT nest the OU under OU=AADDC Computers.

  • $DomainDN = (Get-ADDomain).DistinguishedName
  • New-ADOrganizationalUnit -Name "WebServers" `
  • Path $DomainDN `
  • ProtectedFromAccidentalDeletion $true
  • # Step 4: Create a New Custom GPO and Link it to the Custom OU
  • $Gpo = New-GPO -Name "GPO_WebServers_SecurityBaseline" -Comment "Hardening for Web Tier VMs"
  • New-GPLink -Name $Gpo.Name -Target "OU=WebServers,$DomainDN" -LinkOrder 1

# Step 5: Move a managed-domain computer object into the custom OU.

# Objects synced from Entra ID into AADDC Users cannot be moved this way.

Get-ADComputer -Identity "WEBVM01" | Move-ADObject -TargetPath "OU=WebServers,$DomainDN"

Management Prerequisites:

Deploy a Windows Server Azure VM in a virtual network that has network line-of-sight and DNS resolution to the Entra Domain Services managed domain.

Join the VM to the managed domain (e.g., aadds.contoso.com ).

Sign in using an account that is a member of the AAD DC Administrators group.

Open the Group Policy Management Console ( gpmc.msc ) or Active Directory Administrative Center ( dsac.exe ) to manage policies.

3. Fine-Grained Password Policies (FGPP) & Password Settings Objects (PSOs)

In standard Active Directory Domain Services, password complexity, minimum length, and lockout policies defined in the Default Domain Policy apply globally to all domain users. Historically, enforcing stronger password requirements for administrators required creating entirely separate Active Directory domains.

Fine-Grained Password Policies (FGPP) resolve this limitation by allowing multiple distinct password and account lockout policies to be defined within a single domain using Password Settings Objects (PSOs) . +-----------------------------------------------------------------------------------+

  • | FINE-GRAINED PASSWORD POLICIES (PSO) ARCHITECTURE |
  • | |
  • | Active Directory Database (NTDS.DIT) |
  • | Path: CN=Password Settings Container,CN=System,DC=corp,DC=contoso,DC=com |
  • | Object Class: msDS-PasswordSettings |
  • | |
  • | +-------------------------------------+ +------------------------------------+ |
  • | | PSO: PSO-Privileged-Admins | | PSO: PSO-Standard-Users | |
  • | | - Precedence: 10 | | - Precedence: 50 | |
  • | | - MinPasswordLength: 16 | | - MinPasswordLength: 12 | |
  • | | - PasswordHistory: 24 | | - PasswordHistory: 12 | |
  • | | - LockoutThreshold: 3 attempts | | - LockoutThreshold: 5 attempts | |
  • | | - LockoutDuration: 30 mins | | - LockoutDuration: 15 mins | |
  • | | - Applied To: SG-Domain-Admins | | - Applied To: SG-Standard-Users | |
  • | +-------------------------------------+ +------------------------------------+ |
  • +-----------------------------------------------------------------------------------+

Critical Scope Rule — Why PSOs Do Not Apply to OUs:

Important

PSOs Cannot Be Applied to Organizational Units (OUs): PSOs apply strictly to User objects and Global / Universal Security Groups via the msDS-PSOAppliesTo attribute. Linking or assigning a PSO to an Organizational Unit has zero effect and will not protect users inside that OU. This is one of the most heavily tested concepts on the AZ-800 exam.

Comparison: Default Domain Password Policy vs. Fine-Grained Password Policies (PSOs)

  • Feature Dimension Default Domain Password Policy Fine-Grained Password Policy (PSO)
  • Storage Location Default Domain Policy GPO in SYSVOL / AD CN=Password Settings Container,CN=System in AD DS
  • Object Class groupPolicyContainer msDS-PasswordSettings
  • Application Scope Entire Domain (all users without PSOs) Specific Users and Global/Universal Security Groups
  • OU Application Inherited through standard domain hierarchy Unsupported (Cannot be applied to OUs)
  • Multiplicity Exactly one policy per domain Unlimited PSOs per domain
  • Precedence Mechanism LSDOU GPO Precedence msDS-PasswordSettingsPrecedence integer attribute
  • Management Tools GPMC ( gpmc.msc ) / gpedit.msc AD Administrative Center ( dsac.exe ) / PowerShell

4. PSO Attributes, Precedence & Conflict Resolution Rules

When multiple PSOs are created within a domain, a user account might be assigned a direct PSO while simultaneously belonging to multiple security groups that each have different PSOs assigned. Active Directory uses a deterministic 4-step algorithm to calculate the Resultant Password Policy : +-----------------------------------------------------------------------------------+

  • | PSO PRECEDENCE RESOLUTION ALGORITHM |
  • | |
  • | [EVALUATION STEP 1: Direct User Assignment] |
  • | - Does the user account have a PSO assigned directly to its object? |
  • | --> YES: That PSO WINS IMMEDIATELY (Overrides ALL group PSOs). |
  • | --> NO: Proceed to Step 2. |
  • | |
  • | [EVALUATION STEP 2: Group Assignment Precedence Number] |
  • | - Is the user a member of one or more groups with assigned PSOs? |
  • | --> Compare the 'msDS-PasswordSettingsPrecedence' integer on each group PSO. |
  • | --> The PSO with the LOWEST NUMERIC VALUE (e.g., 10 beats 20) WINS. |
  • | |
  • | [EVALUATION STEP 3: Tie-Breaker by Object GUID] |
  • | - If multiple group PSOs share the exact same precedence number: |
  • | --> The PSO with the lowest binary/alphabetical objectGUID WINS. |
  • | |
  • | [EVALUATION STEP 4: Default Domain Policy Fallback] |
  • | - If NO PSOs are assigned directly or through group membership: |
  • | --> The domain-wide Default Domain Policy applies. |
  • +-----------------------------------------------------------------------------------+

Key PSO Attributes ( msDS-PasswordSettings Schema):

msDS-PasswordSettingsPrecedence : Integer value determining priority (e.g., 10 ).

msDS-PasswordReversibleEncryptionEnabled : Boolean ( $false standard).

msDS-PasswordHistoryLength : Number of past passwords remembered (e.g., 24 ).

msDS-PasswordComplexityEnabled : Enforces 3 of 4 complexity categories (uppercase, lowercase, digits, symbols).

msDS-MinimumPasswordLength : Minimum character length (e.g., 16 ).

msDS-MinimumPasswordAge : Time before a user can change their password again (e.g., 1.00:00:00 for 1 day, preventing rapid cycling through history).

msDS-MaximumPasswordAge : Password validity lifespan before expiration (e.g., 60.00:00:00 for 60 days).

msDS-LockoutThreshold : Number of failed logon attempts before account lockout (e.g., 5 ).

msDS-LockoutObservationWindow : Time window for tracking bad attempts (e.g., 00:30:00 for 30 minutes).

msDS-LockoutDuration : Lockout duration (e.g., 00:30:00 for 30 minutes; 0 requires administrator unlock).

5. PowerShell Management of Fine-Grained Password Policies

Active Directory PowerShell module provides dedicated cmdlets to create, configure, link, and evaluate PSOs without requiring legacy ADSI Edit. # 1. Create a New Fine-Grained Password Policy for Privileged Administrators

  • New-ADFineGrainedPasswordPolicy -Name "PSO-Privileged-Admins" `
  • Precedence 10 `
  • ComplexityEnabled $true `
  • MinPasswordLength 16 `
  • PasswordHistoryCount 24 `
  • MinPasswordAge "1.00:00:00" `
  • MaxPasswordAge "60.00:00:00" `
  • LockoutThreshold 3 `
  • LockoutObservationWindow "00:30:00" `
  • LockoutDuration "00:30:00" `
  • ProtectedFromAccidentalDeletion $true
  • # 2. Assign the PSO to a Global Security Group
  • Add-ADFineGrainedPasswordPolicySubject -Identity "PSO-Privileged-Admins" `
  • Subjects "SG-Tier1-Admins", "SG-Domain-Admins"
  • # 3. Create a Secondary PSO for Service Accounts with Lower Precedence (Higher Number)
  • New-ADFineGrainedPasswordPolicy -Name "PSO-Service-Accounts" `
  • Precedence 50 `
  • ComplexityEnabled $true `
  • MinPasswordLength 20 `
  • PasswordHistoryCount 12 `
  • MinPasswordAge "00:00:00" `
  • MaxPasswordAge "180.00:00:00" `
  • LockoutThreshold 0 # No lockout for service accounts
  • Add-ADFineGrainedPasswordPolicySubject -Identity "PSO-Service-Accounts" `
  • Subjects "SG-App-ServiceAccounts"
  • # 4. CRITICAL DIAGNOSTIC: Evaluate the Resultant Password Policy for a Specific User
  • Get-ADUserResultantPasswordPolicy -Identity "ranchen"

# Output displays the winning PSO details:

  • # Name : PSO-Privileged-Admins
  • # Precedence : 10
  • # ComplexityEnabled : True
  • # MinPasswordLength : 16
  • # LockoutThreshold : 3

Tip

Troubleshooting Effective Password Policies: When diagnosing why a user account was locked out prematurely or why an administrator cannot set an 8-character password, always execute Get-ADUserResultantPasswordPolicy -Identity <username> . If the cmdlet returns $null , the user is governed by the domain-wide Default Domain Policy GPO.