Study guide

12.1 Remote Access Role, VPN Protocols & Site-to-Site VPN to Azure

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.1 Remote Access Role, VPN Protocols & Site-to-Site VPN to Azure

Key Takeaways Explain This Topic AI

The Remote Access role bundles DirectAccess and VPN, Routing (LAN routing, NAT, and BGP), and Web Application Proxy as selectable role services.

IKEv2 with MOBIKE survives a change of client IP address, which is why it is the correct client-to-site protocol for laptops roaming between Wi-Fi and cellular.

SSTP tunnels PPP inside TLS over TCP 443, which traverses restrictive firewalls but suffers TCP-over-TCP meltdown on lossy links; L2TP/IPsec and PPTP are legacy choices.

A Windows Server RRAS site-to-site tunnel to an Azure VPN Gateway must use an IKEv2 demand-dial interface and an Azure route-based gateway, because policy-based gateways do not support it.

Adding BGP on both ends replaces static route maintenance with dynamic prefix exchange across the tunnel.

Last updated: August 2026

Remote Access Role, VPN Protocols & Site-to-Site VPN to Azure

Hybrid enterprise architectures require seamless, secure, and resilient communication channels connecting on-premises data centers, branch offices, remote mobile workforces, and Microsoft Azure virtual networks. Windows Server provides enterprise-grade edge networking through the Remote Access (RRAS) server role and centralized authentication, authorization, and accounting (AAA) via the Network Policy and Access Services (NPAS) role.

This section covers the Remote Access edge itself: deploying Routing and Remote Access Service (RRAS) , selecting among the client VPN tunneling protocols, and configuring robust IPsec Site-to-Site (S2S) tunnels to an Azure Virtual Network Gateway with Border Gateway Protocol (BGP). The Network Policy and Access Services (NPAS) role and Network Policy Server RADIUS policy processing are covered in section 12.2.

1. Windows Server Remote Access Role Architecture

The Remote Access role in Windows Server unifies several critical perimeter networking and remote connectivity services under a single management surface. +-----------------------------------------------------------------------------------+

  • | WINDOWS SERVER REMOTE ACCESS ROLE |
  • | |
  • | +--------------------------+ +--------------------------+ +-----------------+ |
  • | | DirectAccess & VPN (RAS) | | Routing & NAT (RRAS) | | Web App Proxy | |
  • | |--------------------------| |--------------------------| |-----------------| |
  • | | - Client-to-Site VPN | | - LAN / WAN Routing | | - Reverse Proxy | |
  • | | - Demand-Dial S2S VPN | | - Network Address Trans. | | - AD FS Pre-auth| |
  • | | - IKEv2, SSTP, L2TP/IPsec| | - RIPv2 & BGP Routing | | - Kerberos KCD | |
  • | +--------------------------+ +--------------------------+ +-----------------+ |
  • +-----------------------------------------------------------------------------------+
  • Core Role Services

DirectAccess and VPN (RAS):

Remote Access VPN (Client-to-Site): Enables remote telecommuters to establish encrypted tunnels back to the corporate intranet using Point-to-Point Protocol (PPP) over secure encapsulation.

Demand-Dial Site-to-Site (S2S) VPN: Connects disparate physical networks or connects an on-premises data center to an Azure Virtual Network across the public internet.

DirectAccess: Legacy bi-directional, always-on IPv6-over-IPv4 transition technology (superseded in modern Zero Trust roadmaps by Microsoft Entra Private Access).

Routing:

LAN Routing & Static Routes: Routes packets between distinct network interfaces and subnets.

Network Address Translation (NAT): Allows multiple internal hosts on private IPv4 address spaces (RFC 1918) to share a single public IP address for outbound internet access.

Dynamic Routing Protocols: Supports Border Gateway Protocol (BGP) and Routing Information Protocol (RIPv2) for automated route advertisement and topology convergence.

Web Application Proxy (WAP):

Sits in the perimeter DMZ to publish internal HTTP/HTTPS web applications using Active Directory Federation Services (AD FS) pre-authentication (covered in Section 12.3).

Installing and Enabling the Remote Access Role via PowerShell # Install Remote Access role with DirectAccess-VPN and Routing services

Install-WindowsFeature -Name DirectAccess-VPN, Routing -IncludeManagementTools

  • # Initialize the VPN server configuration for IPv4 addressing
  • Install-RemoteAccess -VpnType Vpn

# Assign client IP addresses from a static address pool.

# The pool lives on Set-VpnIPAddressAssignment -- NOT on Set-VpnServerConfiguration,

# which only tunes IPsec/tunnel properties. -IPAddressRange takes start, end.

  • Set-VpnIPAddressAssignment `
  • IPAssignmentMethod StaticPool `
  • IPAddressRange '10.200.50.100', '10.200.50.200' `
  • PassThru

# Switch authentication from local Windows to an external RADIUS (NPS) server.

# -Type accepts ONLY Windows or ExternalRadius. The shared secret is a plain String.

  • Set-VpnAuthType -Type ExternalRadius -RadiusServer '10.100.1.50' `
  • SharedSecret 'EnterpriseSecret2026!' -PassThru

# Set-VpnAuthType only TOGGLES the authentication type; it cannot add further

# RADIUS servers. Additional servers are added explicitly:

  • Add-RemoteAccessRadius -ServerName '10.100.1.51' -Purpose Authentication `
  • SharedSecret 'EnterpriseSecret2026!' -PassThru
  • Exam trap -- the two RRAS authentication values. Set-VpnAuthType -Type accepts
  • exactly Windows and ExternalRadius . RadiusAuthentication is not a value of
  • this parameter -- it is a conflation with Add-RemoteAccessRadius -Purpose Authentication ,

where Authentication / Accounting / Otp are the legal purposes. Note also that -SharedSecret is typed String and is documented as being supplied in clear text, so

wrapping it in ConvertTo-SecureString binds the literal text System.Security.SecureString as the secret and silently breaks RADIUS authentication.

2. VPN Tunneling Protocols Comparison

Selecting the correct VPN tunneling protocol requires balancing cryptographic strength, firewall traversal capabilities, client operating system compatibility, and connection persistence.

Feature / Metric IKEv2 (IPsec) SSTP (SSL/TLS) L2TP / IPsec PPTP (Legacy)

Transport Layer & Ports UDP 500 (IKE), UDP 4500 (NAT-T), IP 50 (ESP) TCP 443 (SSL/TLS) UDP 500, UDP 4500, UDP 1701 TCP 1723, IP 47 (GRE)

Encryption Cipher AES-GCM-256, AES-CBC-256 AES-256 (TLS 1.2 / 1.3) 3DES, AES-256 (IPsec ESP) MPPE 128-bit (Weak)

Firewall Traversal Moderate (Requires UDP 500/4500 open) Excellent (Traverses virtually all firewalls/proxies) Moderate (Requires UDP 500/4500/1701) Poor (GRE is frequently blocked by ISPs)

MOBIKE (Fast Reconnect) Yes (Seamless network switching) No (Connection drops on IP change) No No

Authentication Support Machine Certs, EAP-TLS, MS-CHAPv2 Server SSL Cert + EAP-TLS / MS-CHAPv2 Machine Certs or Pre-shared Key (PSK) MS-CHAPv2 (Vulnerable)

Client OS Support Windows, macOS, iOS, Android, Linux Windows native, third-party clients Universal Universal

Security Recommendation Recommended (Corporate Default) Recommended (Remote Roaming) Acceptable fallback DEPRECATED (Do NOT Use)

  • Protocol Deep Dives
  • IKEv2 (Internet Key Exchange version 2 / IPsec)

MOBIKE Technology (RFC 4555): IKEv2 supports Mobility and Multihoming Protocol (MOBIKE). When a remote user switches from an office Wi-Fi network to a mobile 5G hotspot or home broadband, the underlying IPsec Security Association (SA) automatically updates its tunnel endpoints without dropping active TCP connections or requiring re-authentication.

Performance: Hardware-accelerated AES-NI cryptographic offloading provides the lowest CPU overhead and highest throughput of all VPN protocols.

Prerequisites: Requires a trusted Computer Certificate issued by an enterprise Public Key Infrastructure (PKI) installed on the VPN server, matching the external Fully Qualified Domain Name (FQDN).

SSTP (Secure Socket Tunneling Protocol)

Firewall Evasion: Encapsulates Point-to-Point Protocol (PPP) frames inside a standard HTTPS TLS tunnel over TCP port 443 . Because TCP 443 is universally open across corporate firewalls, hotel networks, and public Wi-Fi hotspots, SSTP serves as the ultimate fallback for restricted remote environments.

Certificate Validation: The client must trust the Certificate Authority (CA) that issued the VPN server's SSL certificate. If the Certificate Revocation List (CRL) distribution point is unreachable, the client will terminate the connection with error 0x80092013.

PPTP (Point-to-Point Tunneling Protocol)

Exam Warning: PPTP relies on MS-CHAPv2 and Microsoft Point-to-Point Encryption (MPPE). MS-CHAPv2 has known cryptographic flaws that allow trivial offline dictionary and hash-cracking attacks. PPTP is disabled by default in hardened baselines and must never be selected in modern enterprise architectures.

3. Site-to-Site IPsec VPN to Azure VPN Gateway

Connecting an on-premises Windows Server RRAS router to a Microsoft Azure Route-based Virtual Network Gateway establishes a secure hybrid network bridge. +-----------------------------------------------------------------------------------+

  • | S2S IPSEC VPN: ON-PREMISES RRAS TO AZURE VNET |
  • | |
  • | [ON-PREMISES DATA CENTER] [MICROSOFT AZURE] |
  • | +--------------------------+ +-------------------------+ |
  • | | Windows Server 2025 RRAS | | Azure VPN Gateway | |
  • | | - Demand-Dial Interface | ===(IKEv2 / IPsec)===> | - Route-Based (VpnGw1-5)| |
  • | | - Public IP: 203.0.113.10| UDP 500 / UDP 4500 | - Public IP: 52.168.1.5 | |
  • | | - Private: 192.168.10.0/24 | - Private: 10.100.0.0/16| |
  • | | - BGP ASN: 65010 | <---(BGP Peering)---> | - BGP ASN: 65515 | |
  • | +--------------------------+ TCP Port 179 +-------------------------+ |
  • +-----------------------------------------------------------------------------------+
  • Architecture and Cryptographic Proposals

Azure Route-Based VPN Gateways require IKEv2 . A custom IPsec policy must be negotiated matching Azure's cryptographic suites across Phase 1 (Main Mode) and Phase 2 (Quick Mode / Child SA). # 1. Create a Demand-Dial S2S Interface on the Windows Server RRAS Router

  • Add-VpnS2SInterface `
  • Name 'Azure-S2S-Tunnel' `
  • Destination '52.168.1.5' `
  • IPv4Subnet @('10.100.0.0/16:100') `
  • AuthenticationMethod PSKOnly `
  • SharedSecret 'PreSharedKeyAzure2026!Secure' `
  • Protocol IKEv2 `
  • Persistent `
  • AdminStatus $true

# 2. Configure Custom IPsec & IKE Cryptographic Parameters matching Azure.

  • # -CustomPolicy is its own parameter set: use -EncryptionMethod and
  • # -IntegrityCheckMethod. Because the ESP cipher is AEAD (GCMAES256), the

# authentication transform must be GCMAES256 as well.

  • Set-VpnServerConfiguration `
  • TunnelType IKEV2 `
  • CustomPolicy `
  • EncryptionMethod GCMAES256 `
  • CipherTransformConstants GCMAES256 `
  • AuthenticationTransformConstants GCMAES256 `
  • IntegrityCheckMethod SHA256 `
  • PfsGroup PFS2048 `
  • DHGroup Group14 `
  • SALifeTimeSeconds 27000 `
  • MMSALifeTimeSeconds 28800 `
  • PassThru

Exam trap -- three RRAS S2S naming pitfalls. (1) Add-VpnS2SInterface -AuthenticationMethod accepts only EAP , MachineCertificates , PSKOnly and MSCHAPv2 ; there is no PresharedKey value. (2) The cmdlet that carries the custom

IPsec policy on Windows Server 2019/2022/2025 is Set-VpnServerConfiguration -- Set-VpnServerIPsecConfiguration was the Windows Server 2012 name and is not the

current cmdlet. (3) A custom policy is selected with the -CustomPolicy switch, not

by passing Custom to -EncryptionType , whose only values are NoEncryption , RequireEncryption , OptionalEncryption and MaximumEncryption . Likewise the Main

Mode lifetime parameter is -MMSALifeTimeSeconds (not -MBLifeTimeSeconds ) and the

integrity parameter is -IntegrityCheckMethod (not -DataIntegrity ).

Dynamic Routing with Border Gateway Protocol (BGP)

In large-scale hybrid environments, static routing creates administrative overhead and lacks automated failover. BGP enables dynamic route exchange between Windows Server RRAS and Azure Virtual Network Gateways.

Azure Default BGP ASN: 65515 (Reserved private Autonomous System Number).

On-Premises ASN: Any private 16-bit ASN (e.g., 65010 ).

Transport: BGP peers establish a TCP session over TCP port 179 across the established IKEv2 tunnel. # Install Routing Role Service and Configure BGP Router on Windows Server

Install-WindowsFeature -Name Routing -IncludeManagementTools

  • # Define Local BGP Router instance
  • Add-BgpRouter -BgpIdentifier '192.168.10.1' -LocalASN 65010 -IPv4Routing 'Enabled'
  • # Add Azure VPN Gateway as a BGP Peer
  • Add-BgpPeer `
  • Name 'AzureVNetGateway' `
  • LocalIPAddress '192.168.10.1' `
  • PeerIPAddress '10.100.254.4' `
  • PeerASN 65515 `
  • OperationMode Mixed `
  • PeeringMode Automatic
  • # Advertise On-Premises Subnets to Azure
  • Add-BgpCustomRoute -Network '192.168.10.0/24'