Study guide

12.5 Microsoft Entra Private Access & Global Secure Access

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

12.5 Microsoft Entra Private Access & Global Secure Access

Key Takeaways Explain This Topic AI

Microsoft Entra Private Access is Microsoft's Zero Trust Network Access solution, delivered with Microsoft Entra Internet Access as Microsoft Entra Security Service Edge under the Global Secure Access umbrella.

Unlike Entra Application Proxy, Private Access is protocol-agnostic and secures any private TCP or UDP resource, including RDP (3389), SMB (445), SSH (22), Kerberos, and custom ERP traffic.

Private Access exposes resources through Quick Access (one primary tenant-wide group of FQDNs and IP ranges) or per-app Global Secure Access apps used when a subset of resources needs different Conditional Access policies.

The Microsoft Entra private network connector requires Windows Server 2016 or later with .NET Framework 4.7.2 or later, TLS 1.2 enabled, and outbound TCP 443 and 80 only — no inbound ports are ever opened.

Connector groups provide high availability because connectors are stateless; moving a connector into a dedicated maintenance connector group drains its sessions gracefully before patching.

Last updated: August 2026

Microsoft Entra Private Access & Global Secure Access

Web Application Proxy and Microsoft Entra Application Proxy (section 12.4) share a hard limitation: both speak only HTTP and HTTPS. Real hybrid estates still depend on Remote Desktop, SMB file shares, SSH, Kerberos, LDAP, SQL Server, and bespoke client-server ERP systems. Historically the only way to reach those from outside the corporate network was a full-tunnel VPN, which places the remote device on the corporate network and therefore grants far more reach than the user's task requires.

Microsoft Entra Private Access is Microsoft's Zero Trust Network Access (ZTNA) answer. It is delivered as one half of Microsoft Entra Security Service Edge (SSE) — the other half being Microsoft Entra Internet Access — under the umbrella product name Global Secure Access (GSA) .

1. Where Private Access Sits in Global Secure Access +-----------------------------------------------------------------------------------+

  • | MICROSOFT ENTRA PRIVATE ACCESS (ZTNA) FABRIC |
  • | |
  • | [REMOTE ENDPOINT] [MICROSOFT SSE EDGE (PoP)] [ON-PREM / CLOUD LAN] |
  • | +---------------------+ +-----------------------+ +-------------------+ |
  • | | Global Secure Access| | Global Secure Access | | Private Network | |
  • | | Client | ===>| Cloud Processing Edge | <== | Connector Group | |
  • | | - Traffic Filter Drv| Enc | - Conditional Access | Out | (Outbound 443) | |
  • | +---------------------+ tun | - Identity Validation | +-------------------+ |
  • | | +-----------------------+ | |
  • | | Intercepts: Routes to: | |
  • | | - RDP (TCP 3389) ---------------------------------------->| [RDP Host]|
  • | | - SMB (TCP 445) ---------------------------------------->| [File Svr]|
  • | | - SSH (TCP 22) ---------------------------------------->| [Linux VM]|
  • | | - ERP (TCP/UDP) ---------------------------------------->| [SQL/ERP] |
  • +-----------------------------------------------------------------------------------+

The Global Secure Access client installs a kernel-level network filter driver on the endpoint. That driver inspects outbound connections and, when a destination matches a configured traffic forwarding profile , tunnels the connection to the nearest Microsoft SSE point of presence instead of letting it take the normal network path. The user never launches a VPN client and the physical network adapter is never bridged into a corporate subnet.

2. Quick Access vs. Per-App Global Secure Access Apps

Private Access offers two ways to describe the private resources you want to tunnel. Both create a real enterprise application object in Microsoft Entra ID, which is what makes user/group assignment and Conditional Access possible.

Aspect Quick Access Global Secure Access (per-app)

Purpose The primary group of private resources you always want tunnelled A narrow subset carved out for different treatment

Quantity One per tenant Many — create as many as you need

Typical use Broad "replace the VPN" onboarding A subset needing stricter Conditional Access, a different user population, or a time-boxed pilot

Granularity Coarse Fine — one app per application or per team

Choose a per-app Global Secure Access app when you need to apply a different set of Conditional Access policies to a subset of users, when a handful of resources deserve stricter policy than the rest, or when you want to secure resources only for a specific time frame.

3. Application Segments

Inside either app type you define application segments , which are what the GSA client actually matches against:

Fully qualified domain names , including wildcard forms for whole internal namespaces.

Individual IP addresses .

IP address ranges , expressed in CIDR or start–end form.

Port and port ranges paired with each destination, and the protocol (TCP, UDP, or both).

Because a segment binds a destination to specific ports, an administrator can publish RDP (TCP 3389) to a jump host without simultaneously publishing SMB (TCP 445) on that same host. This is the concrete mechanism behind the "least privilege" claim: the tunnel is per-application, not per-network.

4. The Microsoft Entra Private Network Connector

Private Access reuses the same on-premises agent as Entra Application Proxy — the Microsoft Entra private network connector .

  • Requirement Value
  • Operating system Windows Server 2016 or later
  • .NET Framework v4.7.2 or later
  • Minimum connector build for Private Access 1.5.3417.0
  • TLS TLS 1.2 must be enabled on the connector server before installation
  • Outbound TCP 443 All communication with the service; *.msappproxy.net and *.servicebus.windows.net
  • Outbound TCP 80 Certificate revocation list (CRL) download during TLS validation
  • Inbound ports None

Two Windows services are installed: Microsoft Entra private network connector (which carries traffic) and Microsoft Entra private network connector updater (which self-updates the agent). Verify both are Running in services.msc after installation.

Connector groups are the unit of high availability and traffic steering. Each application is assigned to a group, and the service load-balances across the healthy connectors in that group; if one connector goes offline, new requests are routed to its peers automatically because connectors are stateless. A useful operational pattern for patching is a dedicated maintenance connector group bound only to a test application — moving a connector into it stops new sessions being routed to that connector while existing sessions drain gracefully, after which you patch, validate, and move it back.

Deployment note: for SSO with Integrated Windows Authentication, the connector server and the backend application servers should be in the same Active Directory domain or in trusting domains. If they are in different domains, use resource-based constrained delegation instead.

5. Conditional Access for Protocols That Never Had It

The strategic payoff is that Conditional Access — historically a control that only applied to web and modern-auth applications — now gates raw protocols. An administrator can require phishing-resistant MFA (FIDO2) and a compliant device before an RDP session to a domain controller is permitted, or block SMB access from non-compliant devices entirely. Neither control is expressible with a traditional IPsec VPN, which authenticates once at tunnel establishment and then forwards packets indiscriminately.

6. Exam Decision Table

  • Scenario in the question Correct answer
  • Browser access to an internal web app, no inbound ports Entra Application Proxy
  • RDP, SMB, SSH, or a custom TCP/UDP app with Conditional Access Entra Private Access
  • Internal web app fronted by AD FS in a DMZ Web Application Proxy
  • Azure App Service reaching one on-premises TCP endpoint Azure Relay / Hybrid Connections (12.6)
  • Whole-network Layer 3 connectivity between sites Site-to-site VPN (12.1)

Exam trap: Private Access requires the Global Secure Access client on the endpoint, whereas Application Proxy is clientless (browser only). If a question specifies that no agent may be installed on the user's device, Private Access is eliminated regardless of how well it otherwise fits.