Study guide

1.7 Forest and Domain Trust Relationships

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

1.7 Forest and Domain Trust Relationships

Key Takeaways Explain This Topic AI

The trusting domain holds the resources and the trusted domain holds the accounts; user access flows in the opposite direction to the trust arrow.

Parent-child and tree-root trusts are created automatically and are always two-way and transitive; shortcut, external, forest and realm trusts are created by an administrator.

A forest trust is transitive within the two forests it joins but never between forest trusts — Contoso trusting Fabrikam and Fabrikam trusting Northwind does not make Contoso trust Northwind.

Selective authentication blocks cross-trust authentication until the Allowed to Authenticate permission is granted on the specific computer object.

SID filtering is enabled by default on external and forest trusts and must be temporarily disabled with netdom trust /quarantine:no for ADMT SID history to be honoured.

Last updated: August 2026

Forest and Domain Trusts

A trust is the plumbing that lets a user account in one directory be recognised by a resource in another. Mergers and acquisitions, subsidiary forests kept deliberately separate, and Microsoft Entra Domain Services resource forests all raise the same three questions the exam tests repeatedly: which type of trust, in which direction , and with which security controls .

1. Active Directory Trust Architecture: Types and Directions

Trust relationships establish communication channels between separate Active Directory domains or forests, allowing security principals (users) in an account domain to be authenticated and authorized to access resources in a resource domain. +-----------------------------------------------------------------------------+

  • | ACTIVE DIRECTORY TRUST TYPOLOGY |
  • | |
  • | TRUST TYPE SCOPE TRANSITIVITY COMMON SCENARIOS |
  • | --------------+----------------------+---------------+--------------------|
  • | Forest Trust | Between two Forest | Transitive | M&A, enterprise |
  • | | Root domains | | forest integration |
  • | External | Between domains in | Non-transitive| Legacy NT4, isolated|
  • | | different forests | | single-domain link |
  • | Shortcut | Between domains in | Transitive | Optimizes Kerberos |
  • | | same forest / forest | | path in deep trees |
  • | Realm | AD DS domain to non- | Transitive or | UNIX / Linux MIT |
  • | | Windows Kerberos | Non-transitive| Kerberos realms |

+-----------------------------------------------------------------------------+ +-----------------------------------------------------------------------------+

  • | THE TRUST DIRECTION AXIOM |
  • | |
  • | [TRUSTING DOMAIN] (Resource Domain) ===(Trust Arrow)===> [TRUSTED DOMAIN] |
  • | - Contains File Shares, Apps, VMs (User Domain) |
  • | - TRUSTS the user domain's authentication - Contains Users|
  • | |
  • | * ACCESS FLOW: Users flow OPPOSITE to the Trust Arrow (Trusted -> Trusting)|
  • +-----------------------------------------------------------------------------+

Important

The Trust Direction Golden Rule: The Trusting Domain is the Resource Domain (where servers, shares, and applications reside). The Trusted Domain is the Account Domain (where user accounts reside). The direction of trust points from Trusting to Trusted, but the flow of user access is the exact opposite—from Trusted (users) to Trusting (resources).

2. Trust Security: Selective Authentication & SID Filtering

When establishing cross-forest trusts, identity administrators must implement defense-in-depth security controls to prevent unauthorized lateral movement and privilege escalation. +-----------------------------------------------------------------------------+

  • | SELECTIVE AUTHENTICATION VS FOREST-WIDE AUTH |
  • | |
  • | [FOREST-WIDE AUTHENTICATION] |
  • | - Default setting for intra-forest domains and trusted partners |
  • | - Any user in the trusted forest can authenticate to any server |
  • | - Access is governed purely by standard NTFS/share ACLs |
  • | |
  • | [SELECTIVE AUTHENTICATION] (High Security Boundary) |
  • | - Authentication requests across the trust are blocked by default |
  • | - Users in the trusted forest CANNOT authenticate to a resource server |
  • | unless explicitly granted the 'Allowed to Authenticate' permission on |
  • | the specific computer object in Active Directory Users and Computers |
  • +-----------------------------------------------------------------------------+
  • 1. Selective Authentication Implementation

When configuring a Forest Trust across organizational boundaries (e.g., between two independent enterprise subsidiaries), select Selective Authentication . When enabled:

Kerberos tickets presented by users from the foreign forest are validated at the domain boundary.

The domain controller checks if the user has been explicitly granted the Allowed to Authenticate permission on the target computer object's discretionary access control list (DACL).

If the permission is not granted, the user receives an Access Denied error before any application or service code executes.

2. SID Filtering (Quarantine) Mechanics

The Elevation Vulnerability: When a user logs on across a trust, their Kerberos Privilege Attribute Certificate (PAC) contains a list of their group SIDs. A malicious administrator in a trusted external forest could inject well-known administrative SIDs (e.g., S-1-5-21-...-512 Domain Admins) into a user's PAC, attempting to gain instant administrative rights in the trusting forest.

SID Filtering Defense: SID Filtering (enabled by default on all external and forest trusts) strips out all foreign, non-authoritative SIDs from the Kerberos ticket at the trust boundary.

  • Management Command: :: Enable SID filtering (quarantine) on a trust relationship
  • netdom trust TrustingDomain.com /domain:TrustedDomain.com /quarantine:yes
  • 3. Trusts Inside a Forest Are Automatic

Nothing in the previous sections applies to the trusts you never create. When a child domain is added to an existing domain, Active Directory automatically builds a parent-child trust ; when a second domain tree is added to a forest, it builds a tree-root trust . Both are two-way and transitive , and both are created and maintained by the system — you cannot delete them without removing the domain. Transitivity across the forest is exactly why a user in sales.eu.contoso.com can be granted rights on a server in corp.contoso.com with no administrator ever touching Active Directory Domains and Trusts.

The trust you do create inside a forest is the shortcut trust , and it exists purely for performance. Kerberos referrals normally walk the domain tree upward to the forest root and back down again; in a deep or wide forest that can be several referral hops. A shortcut trust between two heavily interoperating leaf domains short-circuits that path. It can be one-way (referrals accelerate in one direction only) or two-way.

  • Trust type Created by Transitive Scope
  • Parent-child Automatic Yes Between a parent and child domain in the same tree
  • Tree-root Automatic Yes Between forest root and the root of a new tree in the same forest
  • Shortcut Administrator Yes Between two domains in the same forest, to shorten the Kerberos referral path

External Administrator No A single domain to a single domain in another forest, or to a legacy Windows NT domain

Forest Administrator Yes (within the two forests) Between two forest root domains; requires Windows Server 2003 forest functional level or higher

Realm Administrator Configurable An AD DS domain to a non-Windows Kerberos v5 realm such as MIT Kerberos

Important

The transitivity trap. A forest trust is transitive inside the two forests it joins — every domain in Forest A can reach every domain in Forest B. It is not transitive between forest trusts. If Contoso trusts Fabrikam and Fabrikam trusts Northwind, Contoso does not trust Northwind. A third forest requires a third explicit trust.

4. Creating, Validating and Troubleshooting a Trust

There is no New-ADTrust cmdlet. Trusts are created in the Active Directory Domains and Trusts console, with netdom trust , or programmatically through the .NET System.DirectoryServices.ActiveDirectory classes. The ActiveDirectory PowerShell module can read trusts with Get-ADTrust — a distinction worth remembering, because an exam item that offers New-ADTrust as an answer is offering a cmdlet that does not exist. :: Create a two-way forest trust (run from a Domain Admin context in the local forest root)

  • netdom trust corp.contoso.com /domain:corp.fabrikam.com /twoway /transitive:yes /add ^
  • /userD:FABRIKAM\Administrator /passwordD:*
  • :: Validate an existing trust in both directions and reset the trust password if needed
  • netdom trust corp.contoso.com /domain:corp.fabrikam.com /verify /verbose

netdom trust corp.contoso.com /domain:corp.fabrikam.com /resetOneSide /userD:...

:: Enumerate every trust the local domain knows about

nltest /domain_trusts /all_trusts /v # Read trust objects, their direction and whether SID filtering (quarantine) is on

  • Get-ADTrust -Filter * |
  • Format-Table Name,Direction,ForestTransitive,IntraForest,SIDFilteringForestAware,SelectiveAuthentication

Name resolution is the usual failure point. Before a trust can be created, each forest must be able to resolve the other's domain names and locate its domain controllers. The supported options are a conditional forwarder in each forest pointing at the other's DNS servers, a secondary or stub zone , or a shared root DNS infrastructure. A trust creation wizard that fails with "the specified domain either does not exist or could not be contacted" is nearly always a DNS problem, not a credential problem.

Firewall requirements are broader than administrators expect, because trust traffic is ordinary directory and authentication traffic: DNS on TCP/UDP 53, Kerberos on TCP/UDP 88, LDAP on TCP/UDP 389 (and 636 for LDAPS), SMB on TCP 445, the RPC endpoint mapper on TCP 135, and the dynamic RPC range TCP 49152–65535.

Name Suffix Routing and SID History

Two forest-trust-only features round out the picture:

Name suffix routing controls which UPN suffixes are routed across the forest trust. If Fabrikam also owns the fabrikam-eu.com suffix, that suffix must be enabled on the trust before users signing in with it can be authenticated by Contoso. Suffixes that collide with a suffix the local forest already owns are disabled automatically and cannot be enabled — a genuine constraint during mergers where both companies claim the same namespace.

SID history carries a migrated user's former SID so that existing ACLs keep working after an Active Directory Migration Tool (ADMT) migration. SID filtering strips exactly those foreign SIDs, so during an active migration the trust must have quarantine disabled ( netdom trust ... /quarantine:no ) for SID history to be honoured — and it should be re-enabled the moment ACL re-permissioning is complete. :: Enable selective authentication on an existing forest trust

netdom trust corp.contoso.com /domain:corp.fabrikam.com /SelectiveAUTH:yes

  • :: Review and enable a UPN suffix routed across a forest trust
  • netdom trust corp.contoso.com /domain:corp.fabrikam.com /NameSuffixes

Loading diagram... Cross-Forest Trust Authentication & Selective Authentication Boundary