Study guide

6.4 Azure Automation for Hybrid Workloads: Runbooks & Hybrid Runbook Workers

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

6.4 Azure Automation for Hybrid Workloads: Runbooks & Hybrid Runbook Workers

Key Takeaways Explain This Topic AI

The agent-based (V1) Hybrid Runbook Worker retired on 31 August 2024 and all jobs on agent-based workers stopped on 1 April 2025; the extension-based (V2) worker is the only supported platform.

Extension-based workers authenticate with a system-assigned managed identity and have no dependency on the Log Analytics agent or a Log Analytics workspace.

Workers poll for jobs every 30 seconds and a single worker generally accepts about four jobs per poll; if no worker in a group pings for 30 minutes, jobs suspend after three retries.

Runbook jobs on a Windows Hybrid Runbook Worker execute under the local SYSTEM account, so local resource access does not require stored credentials.

Hybrid Runbook Workers are not subject to the Azure sandbox fair-share three-hour limit, which is the usual reason for choosing them over cloud jobs.

Last updated: August 2026

Azure Automation for Hybrid Workloads: Runbooks & Hybrid Runbook Workers

Azure Update Manager solves patching. Everything else operational — restarting a stuck service on a branch file server at 03:00, exporting an Active Directory system state before a change window, reclaiming space on a Hyper-V host — is a runbook problem. Runbooks live in an Azure Automation account , but by default they execute in an Azure-hosted sandbox that cannot see a single on-premises resource. The Hybrid Runbook Worker closes that gap by moving execution onto a machine inside your network while leaving authoring, scheduling and credential storage in Azure.

1. The Hybrid Runbook Worker Model

While Azure Update Manager handles operating system patching, complex operational automation—such as stopping database services prior to patching, restarting clustered Hyper-V nodes sequentially, or managing local Active Directory accounts—requires Azure Automation .

The Extension-Based Hybrid Runbook Worker (HRW) Model

A Hybrid Runbook Worker (HRW) executes PowerShell and Python runbooks hosted in an Azure Automation Account directly within the on-premises operating system. +-----------------------------------------------------------------------------------------+

  • | EXTENSION-BASED HYBRID RUNBOOK WORKER ARCHITECTURE |
  • | |
  • | [AZURE AUTOMATION ACCOUNT] |
  • | - PowerShell Runbooks (e.g., Invoke-ClusterPatching.ps1) |
  • | - Shared Assets: Credentials, Variables, Certificates |
  • | | |
  • | | (Job Dispatched via ARM) |
  • | v |
  • | [ON-PREMISES ARC-ENABLED SERVER] |
  • | +---------------------------------------------------------------------------------+ |
  • | | Azure Connected Machine Agent | |
  • | | - Extension Manager (extmd) installs: | |
  • | | 'AzureAutomationWindowsWorkforceExtension' (Hybrid Worker VM Extension) | |
  • | | | |
  • | | In-Guest Execution Engine: | |
  • | | - Executes Runbook locally under NT AUTHORITY\SYSTEM context | |
  • | | - Authenticates to Azure via Server's System-Assigned Managed Identity | |
  • | | - Interacts with Local Active Directory, Hyper-V, IIS, and Local Storage | |
  • | +---------------------------------------------------------------------------------+ |
  • +-----------------------------------------------------------------------------------------+

Extension-Based HRW vs Legacy Agent-Based HRW:

Legacy Agent-Based HRW: Depended on the legacy Microsoft Monitoring Agent (MMA) and required configuring complex Azure Automation "Run As Accounts" (Service Principals with certificates expiring annually).

Extension-Based HRW (Current Standard): Deployed as a native VM extension ( AzureAutomationWindowsWorkforceExtension ) on Arc-enabled servers. It utilizes the machine's System-Assigned Managed Identity for authentication to Azure resources, eliminating certificate rotation and credential management.

  • Authoring & Executing Runbooks with Shared Assets <#
  • .SYNOPSIS

PowerShell Runbook executed on an on-premises Hybrid Runbook Worker.

Backs up local Active Directory and purges temporary maintenance files.

#>

  • # Retrieve shared automation variable and credentials from Azure Automation Account
  • $BackupPath = Get-AutomationVariable -Name 'LocalADBackupRootPath'
  • $AdminCred = Get-AutomationPSCredential -Name 'OnPremServiceAccountCred'

Write-Output "Starting local maintenance runbook on worker: $env:COMPUTERNAME"

  • # Perform local operating system and workload tasks
  • if (Test-Path -Path $BackupPath) {
  • Write-Output "Exporting AD System State to $BackupPath..."
  • # Execute local PowerShell commands against on-premises subsystems
  • Get-Service -Name NTDS | Restart-Service -Force
  • Write-Output "NTDS Service verified successfully."
  • } else {
  • Write-Error "Target backup directory $BackupPath does not exist locally!"
  • }

Tip

Hybrid Worker Groups for High Availability: In production environments, always deploy multiple Arc-enabled servers into a Hybrid Worker Group . When an Azure Automation job is dispatched to a Hybrid Worker Group, Azure automatically distributes runbook execution to an available, healthy worker node, ensuring operational continuity if an individual on-premises server is rebooting during maintenance.

2. The Retirement That Changes the Correct Answer

There were two worker platforms, and only one survives:

Platform Status Dependency Authentication

Agent-based (V1) Retired 31 August 2024 ; all jobs on agent-based workers stopped on 1 April 2025 Log Analytics agent reporting to a Log Analytics workspace Run As accounts (certificate-based service principals requiring annual renewal)

Extension-based (V2) The supported platform None — deployed as a VM extension through the Azure VM agent or the Azure Connected Machine agent System-assigned managed identity

For an on-premises server this means the sequence is always: onboard to Azure Arc first so the Connected Machine agent is present, then install the Hybrid Runbook Worker extension through that agent. Any design that starts by installing the Log Analytics agent is describing a retired product.

Extension-based workers also inherit automatic minor-version upgrades by default, and can be deployed through the portal, PowerShell, Azure CLI, ARM or Bicep templates, REST, or the Extensions blade of an individual machine.

3. Worker Groups, Scale and Job Dispatch Behaviour

A Hybrid Runbook Worker group is the unit you target when you start a runbook — you choose the group, never an individual worker. Adding a second worker to a group buys both high availability and load balancing.

  • Behaviour Value
  • Maximum user Hybrid Runbook Workers per Automation account 4,000
  • Maximum system Hybrid Runbook Workers per Automation account 4,000
  • Automation accounts a single machine may register with One
  • Job polling interval Every 30 seconds
  • Jobs a single worker generally accepts per poll About 4
  • Group considered inactive after 30 minutes with no ping from any member
  • Job outcome when the group is inactive Suspended after three retry attempts

Job restarts after a worker reboot Restarts from the beginning, or from the last checkpoint for PowerShell Workflow runbooks; suspended after three restarts

Two consequences follow directly. First, if you are pushing jobs faster than roughly four per 30 seconds into a single-worker group, jobs will queue and eventually error — the fix is more workers in the group, not a bigger worker. Second, Hybrid Runbook Workers are not supported on Virtual Machine Scale Sets , so the "scale out the workers automatically" design does not exist.

The other genuine advantage is the absence of sandbox limits: a Hybrid Runbook Worker job is bounded only by the host's own CPU, memory, disk and network, and is not subject to the Azure sandbox fair-share three-hour ceiling. Long-running migrations and bulk operations are the canonical reason to choose a worker over a cloud job.

System versus User Hybrid Workers

A system Hybrid Worker group is created and managed by Azure services such as Update Management and Change Tracking on your behalf and cannot be used to run your own runbooks. A user Hybrid Worker group is the one you create and target explicitly. Selecting a system group in a runbook schedule is a configuration error, not a shortcut.

4. Execution Context, Identity and Networking

On Windows, runbook jobs on a Hybrid Runbook Worker execute under the local SYSTEM account (on Linux, under nxautomation ). That is convenient — local file, service and registry operations need no stored credential — and it is also a limitation, because SYSTEM has no network identity of its own beyond the computer account. Anything that must authenticate off-box should use either the machine's system-assigned managed identity for Azure resources, or a credential retrieved from the Automation account's shared assets for on-premises resources: # Azure resources: use the machine's managed identity, no secrets stored anywhere

  • Connect-AzAccount -Identity
  • Get-AzVM -ResourceGroupName 'rg-branch-infra' | Select-Object Name, PowerState
  • # On-premises resources: pull a credential from the Automation account's shared assets
  • $SvcCred = Get-AutomationPSCredential -Name 'OnPremServiceAccountCred'
  • Invoke-Command -ComputerName 'FS-BRANCH-07' -Credential $SvcCred -ScriptBlock { Restart-Service Spooler }

For network controls, Azure Automation publishes the GuestAndHybridManagement service tag, which can be used in a network security group or Azure Firewall rule in place of hard-coded IP addresses. It covers webhook triggers from inside a virtual network and worker-to-service communication — but note that it does not cover runbook execution inside an Azure sandbox, only execution on a Hybrid Runbook Worker.

Shared assets are what keep runbooks portable: variables (optionally encrypted), credentials , certificates , connections and schedules are stored in the Automation account and retrieved at run time with Get-AutomationVariable , Get-AutomationPSCredential and Get-AutomationCertificate . Storing a password in the runbook body instead is the failure the exam expects you to reject.