Study guide
5.4 OpenSSH on Windows Server & PowerShell Remoting over SSH
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
5.4 OpenSSH on Windows Server & PowerShell Remoting over SSH
Key Takeaways Explain This Topic AI
OpenSSH ships in-box from Windows Server 2019 and Windows 10 build 1809 and is installed as a Feature on Demand named OpenSSH.Server~~~~0.0.1.0.
sshd reads %programdata%\ssh\sshd_config and generates that file plus host keys on first service start; configuration changes require a service restart.
Windows OpenSSH supports only password and publickey authentication — Microsoft Entra account authentication is not supported.
Keys for any member of the Administrators group are read from %programdata%\ssh\administrators_authorized_keys , which must be ACLed to SYSTEM and BUILTIN\Administrators only.
GSSAPI (Kerberos) authentication is disabled by default and is available only on Windows Server 2022 and later.
Last updated: August 2026
OpenSSH on Windows Server & PowerShell Remoting over SSH
WinRM-based PowerShell remoting assumes a Windows-to-Windows relationship with Kerberos or an explicit TrustedHosts list behind it. In a hybrid estate that also runs Ubuntu and Red Hat Enterprise Linux — on-premises and as Azure IaaS virtual machines — that assumption breaks down. OpenSSH is Microsoft's answer: the same sshd daemon, key material and client tooling used across the Linux world, shipped in-box in Windows Server and usable as a PowerShell remoting transport.
1. OpenSSH as a Native Windows Server Role
Microsoft added OpenSSH to the operating system starting with Windows Server 2019 and Windows 10 build 1809 . It is not a third-party port and needs no download: both the client and the server are Features on Demand already staged in the image. +-----------------------------------------------------------------------------------------+
- | OPENSSH HYBRID MANAGEMENT ARCHITECTURE |
- | |
- | [Admin Workstation] |
- | - Runs: Enter-PSSession -HostName 10.0.1.5 -UserName azureadmin -KeyFilePath ~/.ssh/id_rsa
- | | |
- | | Standard SSH Protocol (TCP Port 22) - Asymmetric Key Authentication |
- | v |
- | +-----------------------------------------------------------------------------------+ |
- | | TARGET WINDOWS SERVER 2025 (OpenSSH) | |
- | | - sshd.exe Listening on TCP Port 22 | |
- | | - Authenticates via %ProgramData%\ssh\administrators_authorized_keys | |
- | | - Launches Subsystem: powershell.exe -sshs -NoLogo -NoProfile | |
- | +-----------------------------------------------------------------------------------+ |
- +-----------------------------------------------------------------------------------------+
- Installing and Configuring OpenSSH Server on Windows Server: # Install OpenSSH Server capability
- Add-WindowsCapability -Online -Name OpenSSH.Server~~~~0.0.1.0
- # Start sshd service and set startup type to Automatic
- Start-Service sshd
- Set-Service -Name sshd -StartupType 'Automatic'
- # Configure firewall rule for SSH (TCP Port 22)
- New-NetFirewallRule -Name 'OpenSSH-Server-In-TCP' -DisplayName 'OpenSSH Server (sshd)' `
- Enabled True -Direction Inbound -Protocol TCP -Action Allow -LocalPort 22
- PowerShell Remoting over SSH Syntax: # Interactive remoting over SSH to a Windows or Linux node
- Enter-PSSession -HostName '10.10.1.20' -UserName 'secadmin' -KeyFilePath 'C:\Users\admin\.ssh\id_ed25519'
# Parallel execution across Linux and Windows instances using SSH
$SSHOptions = @{ HostName = 'ubuntu-srv01.corp.contoso.com'; UserName = 'azureuser'; KeyFilePath = '~/.ssh/id_rsa' }
- $Session = New-PSSession @SSHOptions
- Invoke-Command -Session $Session -ScriptBlock { uname -a; Get-Date }
- 2. Services, Configuration Files and Key Locations
Two Windows services back the implementation. sshd is the server daemon, and ssh-agent caches decrypted private keys for the client. Neither starts automatically after the capability is added, which is why Set-Service -StartupType Automatic belongs in every deployment script.
Path or key Purpose
%programdata%\ssh\sshd_config Server configuration. Generated with defaults on first service start if missing.
%programdata%\ssh\ssh_config System-wide client configuration.
%userprofile%\.ssh\config Per-user client configuration; takes precedence over the system-wide file.
%userprofile%\.ssh\authorized_keys Public keys for a standard user (the AuthorizedKeysFile default is .ssh/authorized_keys ).
%programdata%\ssh\administrators_authorized_keys Public keys used instead for any member of the Administrators group .
%programdata%\ssh\ssh_host_*_key RSA, ECDSA and Ed25519 host keys, auto-generated on first start.
HKLM:\SOFTWARE\OpenSSH → DefaultShell String value naming the shell launched for an interactive session.
%systemdrive%\Windows\System32\OpenSSH Default binary location.
Warning
The administrators_authorized_keys file is the single most common cause of "key authentication works for a normal user but not for the administrator". sshd refuses to honour it unless its ACL is restricted to NT Authority\SYSTEM and BUILTIN\Administrators . Reset it explicitly: icacls.exe "C:\ProgramData\ssh\administrators_authorized_keys" /inheritance:r /grant "Administrators:F" /grant "SYSTEM:F" # Make PowerShell 7 the interactive shell for incoming SSH sessions
- New-ItemProperty -Path 'HKLM:\SOFTWARE\OpenSSH' -Name DefaultShell `
- Value 'C:\Program Files\PowerShell\7\pwsh.exe' -PropertyType String -Force
- # sshd reads its configuration only at service start
- Restart-Service sshd
- 3. Authentication and Access Control in sshd_config
Windows OpenSSH supports exactly two authentication methods: password and publickey . Microsoft Entra account authentication is not supported, and several directives familiar from Linux — X11Forwarding , HostbasedAuthentication , AuthorizedKeysCommand , PermitUserEnvironment — are not implemented at all. PermitRootLogin has no meaning on Windows; to block administrative sign-in you deny the group instead.
GSSAPIAuthentication (Kerberos) is available only from Windows Server 2022 onward and is disabled by default ; enabling it also requires the client to specify the host with ssh -K or an equivalent GSSAPIAuthentication yes entry in the client config.
Access rules are processed in a fixed order — DenyUsers , AllowUsers , DenyGroups , then AllowGroups — and every principal name must be written in lower case . Domain principals resolve to domain_short_name\user_name , and because @ already means "from this host" in SSH syntax, Windows uses ? in its place when matching a domain: # %programdata%\ssh\sshd_config
- PasswordAuthentication no
- PubkeyAuthentication yes
- DenyUsers contoso\legacysvc
- AllowGroups contoso\sshadmins contoso\serveroperators
- # Register PowerShell as an SSH subsystem so PowerShell remoting can use this host
- Subsystem powershell C:/Program Files/PowerShell/7/pwsh.exe -sshs -NoLogo -NoProfile
For file-based troubleshooting set SyslogFacility LOCAL0 , which writes to %programdata%\ssh\logs ; any other value, including the default AUTH , sends logging to Event Tracing for Windows instead.
4. Choosing Between WinRM and SSH as the Remoting Transport
- WinRM transport SSH transport
- PowerShell version Windows PowerShell 5.1 and PowerShell 7 PowerShell 7 (or 6) on both ends
- Cross-platform Windows only in practice Windows, Linux, macOS
- Authentication Kerberos, NTLM, CredSSP, certificate Password or public key
- Default port 5985 / 5986 22
- Double-hop Requires CredSSP or resource-based constrained delegation Handled by key forwarding or an agent
- JEA support Yes No — JEA endpoints are a WinRM concept
That last row is the exam-relevant boundary: a scenario that requires a constrained JEA endpoint rules out the SSH transport, while a scenario that requires managing Linux and Windows from one console rules out WinRM. They coexist happily on the same server, so the real design answer is usually "both, for different audiences".