Windows remoting through connections — not a free PowerShell.
WinRM and PowerShell Remoting (PSRP) are one Windows connector family. You store the host and choose WinRM or PSRP, keep passwords and certificates in the vault, then test the path or run allowlisted Windows Ansible books. Same idea as SSH: a governed connection, not a shell in the prompt.
What Windows remoting is allowed to do
Catalog-gated `winrm` connector (`addon.winrm`). It appears only when deployed and the tenant is entitled.
WinRM and PSRP
One connection record, two plugins: WinRM and PowerShell Remoting. You pick the plugin when you create the connection.
Secrets in the vault
Passwords and client certificates stay in the tenant vault — never in the prompt or in workflow JSON.
Test the host
winrm.test checks connectivity with vault credentials before a workflow depends on the Windows host.
Windows Ansible books
Predefined books (for example ping and facts) and entitled Windows scenarios run over that connection — not an arbitrary remote script from the model.
Not a free shell
There is no open remote PowerShell. Calls go through the connection and allowlisted books, the same way SSH uses command profiles.
With Ansible workspaces
Windows playbooks in an Ansible workspace can be marked for WinRM and run against this connection.
Behind VPN when needed
If the Windows host is only reachable over VPN, bring the gateway up first — then WinRM or PSRP.
Explore more
Terraform
A Terraform connection points at modules you have allowlisted. Workflows can validate, plan, apply and show the result. Destroy stays off unless the connection allows it and a person has approved. Typical work: a Proxmox VM, deploying or upgrading a stack, preparing an environment. Provider credentials — including Proxmox API tokens — stay in the tenant vault. The run can be local or over an existing SSH connection.
Ansible
Ansible connections bind inventory and playbooks into governed workflow steps. A run uses an allowlisted playbook, secret-referenced credentials and tenant policy. Chat does not get a free ansible-playbook shell.
SSH
SSH connections store host, port, user and secret-referenced keys. Workflows run allowlisted command profiles. Free-form ssh.execute-command is disabled; use ssh.execute-profile.
VPN
VPN connections (IPsec, SSTP or WireGuard, client or server role) sit in the same governed catalog as SSH and Ansible. Typical path: gateway first, then SSH or playbooks on the far side.
Connectors
The platform composes tools, capabilities and connections: MCP, REST, SQL, GitHub, SSH, Ansible, Terraform, WinRM/PSRP and other deployed connectors. Calls go through tenant policy and secret references.
Ready to move beyond the chatbot?
Build AI that understands your business, follows your processes, finishes the work — and keeps token spend under your control.