Study guide

12.6 Azure Relay & Hybrid Connections

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.6 Azure Relay & Hybrid Connections

Key Takeaways Explain This Topic AI

Azure Relay exposes an on-premises service to the cloud without opening any inbound firewall port, and can be scoped to a single application endpoint on a single machine rather than altering the network like a VPN.

Azure Relay has two features: Hybrid Connections, built on open-standard WebSockets and HTTP(S) and supported on any platform, and the legacy WCF Relay for existing Windows Communication Foundation programming models.

Hybrid connections live in a Relay namespace pinned to one Azure region and authenticate with shared access signature keys over TLS 1.2, using separate listener and sender rules plus primary and secondary keys for rotation.

The Hybrid Connection Manager connects outbound on TCP 443, uses local ports 4999-5001 on Windows and 5001 on Linux, and requires the GUI to run on Windows Server 2016 or later.

App Service Hybrid Connections are TCP-only and limited to 5 per plan on Basic, 25 per plan on Standard, and 220 per app on Premium v1-v4 and IsolatedV2; they cannot use UDP, mount drives, or support LDAP or Active Directory.

Last updated: August 2026

Azure Relay & Hybrid Connections

The technologies in sections 12.4 and 12.5 publish internal resources to users . Azure Relay solves the mirror-image problem: a cloud-native service — Azure App Service , Azure Functions , or Azure Logic Apps — needs to reach into the corporate network to query an on-premises SQL Server, Oracle database, or internal REST/SOAP API. Standing up a site-to-site VPN gateway or an ExpressRoute circuit for a single database connection is disproportionate, and both alter the network environment.

Azure Relay is deliberately narrower. As Microsoft frames it, "an Azure relay can be scoped to a single application endpoint on a single machine," whereas "the VPN technology is far more intrusive, as it relies on altering the network environment."

1. The Relayed Data Transfer Pattern +-----------------------------------------------------------------------------------+

  • | AZURE RELAY & HYBRID CONNECTIONS DATA PATH |
  • | |
  • | [AZURE PAAS ENVIRONMENT] [AZURE CLOUD] [INTERNAL NETWORK] |
  • | +-----------------------+ +---------------+ +------------------+ |
  • | | Azure App Service | ======> | Azure Relay | <====> | Hybrid Connection| |
  • | | (Web Front-End) | Outbound| Service | Out- | Manager (HCM) | |
  • | +-----------------------+ HTTPS | (WCF / Web- | bound | (Windows Server) | |
  • | Port | Sockets) | HTTPS +------------------+ |
  • | 443 +---------------+ 443 | |
  • | (Local TCP 1433) |
  • | v |
  • | +------------------+ |
  • | | On-Prem SQL Svr | |
  • | +------------------+ |
  • +-----------------------------------------------------------------------------------+

The mechanism has four steps:

The on-premises listener connects out to the relay service through an outbound port.

It creates a bi-directional socket tied to a particular address in the relay namespace.

The cloud sender communicates with the on-premises service by sending traffic to the relay service targeting that address.

The relay service relays data to the on-premises service through the dedicated socket.

The sender never needs a direct connection to the on-premises service, never needs to know where it lives, and the on-premises service never needs an inbound firewall port.

2. The Two Relay Features

  • Capability WCF Relay Hybrid Connections
  • Status Legacy offering Current, recommended
  • Protocol WCF relay bindings (RPC) Open-standard WebSockets and HTTP(S)
  • WCF programming model Yes No
  • .NET Framework Yes Yes
  • .NET Core No Yes
  • JavaScript / Node.js No Yes
  • Standards-based open protocol No Yes

Both features coexist in the Azure Relay service and share a common gateway, but they are otherwise different implementations. Hybrid Connections is the modern, multi-platform choice ; WCF Relay exists for customers with existing WCF programming models.

Naming trap: Azure Relay Hybrid Connections replaced the older BizTalk Services Hybrid Connections feature, which was itself built on WCF Relay. Exam items that mention BizTalk are describing the retired ancestor.

3. Namespaces and Shared Access Signature Authentication

Every hybrid connection lives inside a Relay namespace (a Service Bus namespace), and each namespace is pinned to one Azure region — always choose the region hosting the consuming app to avoid added latency. Authentication and authorization use shared access signature (SAS) keys , and the connection is protected with TLS 1.2 .

SAS rules are role-split: a listener key authorises the on-premises agent to accept relayed traffic, while a sender key authorises the cloud application to initiate it. A gateway connection string looks like this: Endpoint=sb://[NAMESPACE].servicebus.windows.net/;SharedAccessKeyName=defaultListener;SharedAccessKey=[KEY];EntityPath=[HYBRID-CONNECTION-NAME]

Each hybrid connection carries a primary and a secondary key so that keys can be rotated without an outage: repoint consumers at the secondary, regenerate the primary, then swap back.

4. The Hybrid Connection Manager (HCM)

The on-premises listener agent is the Hybrid Connection Manager , which runs as a service on Windows and Linux.

Requirement Detail

Windows version Windows Server 2012 or later (WebSockets dependency); the GUI requires Windows Server 2016 or later

  • Outbound access TCP 443 to Azure Relay — allow *.servicebus.windows.net
  • Local listening ports 4999–5001 on Windows , 5001 on Linux (configurable via HCM_GUI_PORT / HCM_SERVICE_PORT )
  • DNS Must resolve both the endpoint host and the Service Bus namespace
  • Reachability Must have TCP access to the target endpoint itself

For high availability, run multiple Hybrid Connection Managers on separate machines for the same hybrid connection; the relay service distributes traffic across them by random assignment. Conversely, a single HCM can serve many hybrid connections.

Troubleshooting order: a status of Not Connected means no HCM with Azure access is configured for that connection — test with Test-NetConnection <relay-namespace> -P 443 . A status of Connected while the app still fails points at the endpoint side: confirm the endpoint DNS name resolves from the HCM host and that Test-NetConnection <EndpointDNSname> -P <port> succeeds.

5. App Service Hybrid Connections: Limits and Hard Boundaries

Within App Service, each hybrid connection maps to exactly one host:port combination , and the feature is available only on Basic, Standard, Premium, and Isolated plans.

  • Pricing plan Hybrid connections
  • Basic 5 per plan
  • Standard 25 per plan
  • Premium (v1–v4) 220 per app
  • IsolatedV2 220 per app

Things Hybrid Connections cannot do — a rich source of distractors:

Mount a drive.

Use UDP — TCP only.

Reach TCP services that use dynamic ports , such as FTP Passive Mode.

Support LDAP , because LDAP can require UDP.

Support Active Directory , because an App Service worker cannot be domain-joined.

Exam trap: always configure a hybrid connection with a DNS name rather than an IP address . The redirection is triggered by the app's DNS lookup, so a client library that skips the lookup when given a literal IP will bypass the hybrid connection entirely and fail.