Study guide
5.3 Just Enough Administration (JEA) for Constrained PowerShell Endpoints
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.3 Just Enough Administration (JEA) for Constrained PowerShell Endpoints
Key Takeaways Explain This Topic AI
JEA requires two files: a role capability file (.psrc) listing permitted cmdlets, functions and parameter values, and a session configuration file (.pssc) mapping security groups to those roles.
RunAsVirtualAccount grants the session local administrative privilege for the duration of the connection, so the connecting user needs no standing administrative rights.
Role capability files must live in a RoleCapabilities folder inside a valid PowerShell module for the .pssc to resolve them by name.
Register-PSSessionConfiguration publishes the endpoint, and clients reach it with the -ConfigurationName parameter rather than the default Microsoft.PowerShell endpoint.
TranscriptDirectory writes a per-session transcript, which is the audit evidence that a delegated help-desk action actually took place.
Last updated: August 2026
Just Enough Administration (JEA) for Constrained PowerShell Endpoints
PowerShell Remoting as configured so far is all-or-nothing: a user who can enter a session on a server generally does so with the full rights of their account. That is unacceptable for help-desk delegation, where the requirement is "restart the print spooler on any file server" and nothing more. Just Enough Administration (JEA) solves it by constraining what a connected user may run, and by supplying the privilege from a temporary virtual account rather than from the user.
1. Just Enough Administration (JEA) Architecture & Configuration
Just Enough Administration (JEA) is a role-based security technology built into PowerShell that enforces the principle of least privilege. JEA locks down a remote PowerShell endpoint so that non-administrative users (such as Help Desk or junior operators) can perform specific administrative tasks without being members of the Local Administrators or Domain Admins security groups. +-----------------------------------------------------------------------------------------+
- | JEA ARCHITECTURE & PIPELINE |
- | |
- | [Connecting User: HelpDesk_User] (Has NO Admin Rights on Target) |
- | | |
- | | 1. Enter-PSSession -ComputerName Srv01 -ConfigurationName 'HelpDeskOps' |
- | v |
- | +-----------------------------------------------------------------------------------+ |
- | | JEA ENDPOINT ('HelpDeskOps') | |
- | | | |
- | | +-----------------------------------------------------------------------------+ | |
- | | | [Session Configuration File: (.pssc)] | | |
- | | | - SessionType = 'RestrictedRemoteServer' (No-Language Mode) | | |
- | | | - RunAsVirtualAccount = $true (Spawns temporary Local System Virtual Admin) | | |
- | | | - TranscriptDirectory = 'C:\ProgramData\JEA\Transcripts' (Auditing) | | |
- | | | - RoleDefinitions = @{ 'CORP\HelpDeskGroup' = @{ RoleCapabilities = 'DNS' }}| | |
- | | +-----------------------------------------------------------------------------+ | |
- | | | | |
- | | v Maps to Role Capability | |
- | | +-----------------------------------------------------------------------------+ | |
- | | | [Role Capability File: (.psrc)] | | |
- | | | - VisibleCmdlets = 'Restart-Service', @{ Name='Get-Service'; Parameters=..} | | |
- | | | - VisibleFunctions = 'Clear-DnsClientCache' | | |
- | | | - VisibleAliases = 'gsv' | | |
- | | +-----------------------------------------------------------------------------+ | |
- | +-----------------------------------------------------------------------------------+ |
- +-----------------------------------------------------------------------------------------+
The Two JEA Configuration Files:
Role Capability File ( .psrc ): Defines what an authorized user can do. It specifies allowed cmdlets, functions, external executables, and parameter restrictions (e.g., allowing Restart-Service only when -Name equals 'Spooler' ). Role capability files reside inside a RoleCapabilities folder within a PowerShell module path.
Session Configuration File ( .pssc ): Defines who can connect and how the session executes. It maps Active Directory security groups to specific Role Capabilities, enables virtual administrative accounts ( RunAsVirtualAccount = $true ), and configures over-the-shoulder transcript auditing ( TranscriptDirectory ).
- Step-by-Step JEA Authoring & Registration
- Step 1: Create the Role Capability File ( .psrc ) # Create directory inside module path
- $ModulePath = "C:\Program Files\WindowsPowerShell\Modules\JEARoles\RoleCapabilities"
- New-Item -ItemType Directory -Path $ModulePath -Force
- # Author Role Capability File
- New-PSRoleCapabilityFile -Path "$ModulePath\HelpDeskMaintenance.psrc" `
- VisibleCmdlets @(
- 'Get-Service',
- @{ Name = 'Restart-Service'; Parameters = @{ Name = 'Name'; ValidateSet = @('Spooler', 'W32Time') } }
- ) `
- VisibleFunctions @('Get-ProcessInfo') `
- FunctionDefinitions @(
@{ Name = 'Get-ProcessInfo'; ScriptBlock = { Get-Process | Sort-Object CPU -Descending | Select-Object -First 10 } }
- )
- Step 2: Create the Session Configuration File ( .pssc ) # Author Session Configuration File
- New-PSSessionConfigurationFile -Path "C:\JEA\HelpDeskEndpoint.pssc" `
- SessionType 'RestrictedRemoteServer' `
- RunAsVirtualAccount `
- TranscriptDirectory 'C:\JEA\Transcripts' `
- RoleDefinitions @{
- 'CORP\Tier1-HelpDesk' = @{ RoleCapabilities = 'HelpDeskMaintenance' }
- }
- Step 3: Register the JEA Configuration # Register the endpoint on the target server
- Register-PSSessionConfiguration -Name 'HelpDeskOps' -Path "C:\JEA\HelpDeskEndpoint.pssc" -Force
- # Test connection from non-admin client
- Enter-PSSession -ComputerName 'SRV-FILE-01' -ConfigurationName 'HelpDeskOps'
- 2. Virtual Accounts, Group-Managed Service Accounts and Session Types
The identity a JEA session runs under is the reason the model is secure, and it is chosen in the .pssc :
Setting Runs commands as Use when
RunAsVirtualAccount = $true A temporary machine-local administrator account created for the session The delegated tasks are local to the target server — the common case
GroupManagedServiceAccount = 'CORP\gMSA-JEA$' A gMSA with a domain identity The delegated tasks reach other machines, where a machine-local virtual account has no rights
Neither specified The connecting user Rarely useful — it defeats the purpose of JEA
RunAsVirtualAccountGroups narrows the virtual account further: instead of local Administrators, the account is placed only in the groups you list, such as Network Configuration Operators .
The SessionType value is equally consequential. RestrictedRemoteServer is the JEA session type: it starts with the language mode set to NoLanguage and exposes only Exit-PSSession , Get-Command , Get-FormatData , Get-Help , Measure-Object , Out-Default and Select-Object . Everything else a user is allowed to run must be added explicitly by a role capability. NoLanguage mode is what prevents a delegated operator from escaping the constraint through an expression such as Invoke-Expression or a script block.
Constraining Parameters, Not Just Cmdlets
Allowing Restart-Service outright still lets a help-desk operator restart NTDS on a domain controller. Role capabilities can pin parameter values: # Inside the .psrc — allow only these three services to be restarted
- VisibleCmdlets = @(
- @{ Name = 'Restart-Service'; Parameters = @{ Name = 'Name'; ValidateSet = 'Spooler','W3SVC','BITS' } },
- @{ Name = 'Get-Service' },
- 'Get-EventLog'
- )
- # Expose a purpose-built function instead of the underlying cmdlet
- VisibleFunctions = @(
- @{ Name = 'Repair-BranchPrintQueue'; ScriptBlock = { Restart-Service -Name Spooler -Force } }
- )
Important
A role capability file is only discovered if it sits in a RoleCapabilities folder inside a valid PowerShell module on the target server — for example C:\Program Files\WindowsPowerShell\Modules\JEAHelpDesk\RoleCapabilities\HelpDeskMaintenance.psrc . Placing the .psrc next to the .pssc and referencing it by name is the most common JEA registration failure.
3. Operating, Auditing and Removing a JEA Endpoint # What endpoints exist on this server, and what does this one expose to me?
- Get-PSSessionConfiguration | Format-Table Name,PSVersion,Permission
- Invoke-Command -ComputerName 'SRV-FILE-01' -ConfigurationName 'HelpDeskOps' -ScriptBlock { Get-Command }
- # Validate a configuration file before registering it
- Test-PSSessionConfigurationFile -Path 'C:\JEA\HelpDeskEndpoint.pssc'
- # Remove an endpoint (WinRM restart is required for the change to take effect)
- Unregister-PSSessionConfiguration -Name 'HelpDeskOps' -Force
- Restart-Service WinRM
Because TranscriptDirectory was set at registration, every session writes a transcript recording the connecting user, the virtual account used, and each command executed. Those transcripts, not the Security event log, are the primary audit artefact for delegated JEA administration — collect them centrally, because they are written on the target server and a local administrator can delete them.