Qualify PowerShell Direct as a host-to-guest administration path

Source facts

PowerShell Direct runs PowerShell in a Windows guest from its Hyper-V host without depending on guest networking or remote-management configuration. Microsoft requires the virtual machine to be local, running, and to have a configured user profile. The operator must be a Hyper-V administrator on the host and provide valid credentials for the guest. Microsoft Learn.

Applicability

Check the host and guest versions against the current source, then confirm the virtual machine identifier and its actual host. Keep host privileges and guest authentication as two separate prerequisites. An unavailable guest network is only one part of the access decision.

DSE recommendation

Define one bounded administrative action and the expected guest before opening a session. Use the authorized guest account and protect its credentials through the approved handling process. Have the operator record the guest identity from inside the session before running the intended command. For repeatable work, decide when the session will be closed and who owns cleanup.

Verification

Use a harmless inventory command on a representative guest and compare its output with the known guest identity. Confirm the command executed inside that guest rather than on the host. Record failures by prerequisite: host authorization, VM location and state, guest credentials, or supported version. Close the session and retain a sanitized result.

Official references

Microsoft Learn: Manage Windows Virtual Machines with PowerShell Direct. Source reviewed September 8, 2026.