Microsoft Azure ServerManagement
Browse all Azure APIs★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputeoauth225 EndpointsREST
For Agents
Register Windows nodes against a gateway, open management sessions, and run PowerShell commands on remote servers through the Azure control plane.
Use for: Register a Windows server as a managed node in Azure, Provision a Server Management gateway in a resource group, Open a session against a managed node to run commands, Run a PowerShell command on a remote Windows server through Azure
Not supported: Does not provision Azure VMs, manage Azure Arc-enabled servers, or run cross-platform commands — use for legacy Server Management Tools gateway and node operations only.
Jentic publishes the only available OpenAPI specification for ServerManagement, keeping it validated and agent-ready. The Azure Server Management API exposes the Microsoft.ServerManagement resource provider, which lets agents register on-premises Windows servers as managed nodes, pair them to a gateway, open remote sessions, and run PowerShell commands against them through the Azure control plane. It models gateways, nodes, sessions, and PowerShell sub-sessions, and is the underlying API for the Server Management Tools experience that Microsoft offered for hybrid and Server Core deployments.
Install Jentic One Beta
Connect the ServerManagement to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ServerManagement, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with ServerManagement API.
Register an on-premises Windows server as a managed node tied to a gateway
Provision and upgrade Server Management gateways inside a resource group
Regenerate a gateway profile when its credentials need to be rotated
Open a management session against a node and tear it down when done
Start a PowerShell sub-session on top of an active node session
Invoke PowerShell commands remotely and read their output
Cancel a long-running PowerShell command on a remote node
Use Cases
Patterns agents use ServerManagement API for, with concrete tasks.
★ Hybrid Windows Fleet Inventory
Operations teams managing hybrid estates need a single inventory of Windows servers under Azure control. The nodes endpoint at subscription and resource group scope returns every managed node along with the gateway it is attached to, so an agent can build a fleet view that pairs cloud resources with on-premises servers without scraping individual portal pages.
List nodes at subscription scope and return each node's gatewayId, fully qualified domain name, and provisioning state
Remote PowerShell Automation
Platform engineers run PowerShell remotely against managed Windows servers without exposing WinRM directly to the internet. The pssessions endpoint creates a PowerShell sub-session over an existing node session and the invokeCommand endpoint runs a command and returns its output, giving an agent a controlled remote execution channel that flows through the Azure control plane.
Open a session on the node, create a pssession, then call invokeCommand with the script Get-Service to read the service list back
Gateway Lifecycle Management
When a Server Management gateway needs upgrading or its credential profile rotated, an agent can drive the lifecycle through the gateways resource. The regenerateprofile endpoint produces a fresh provisioning profile and upgradetolatest moves the gateway to the latest gateway build, both without requiring an admin to log in to the gateway host.
Call regenerateprofile on the named gateway, then upgradetolatest to roll the gateway forward to the current build
AI Agent Hybrid Ops
An agent built on Jentic uses Server Management to run scoped Windows operations on remote nodes — reading event logs, restarting services, or pulling configuration — without an analyst RDPing into each box. The agent opens a session, runs the command, captures stdout, and closes the session in one tool sequence discovered through Jentic search.
Search Jentic for run powershell on azure managed node, load the schema, and invoke Restart-Service -Name spooler against the target node
Key Endpoints
25 endpoints — jentic publishes the only available openapi specification for servermanagement, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/subscriptions/{subscriptionId}/providers/Microsoft.ServerManagement/nodes
List all managed nodes in the subscription
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServerManagement/gateways/{gatewayName}
Create or update a Server Management gateway
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServerManagement/gateways/{gatewayName}/regenerateprofile
Regenerate the gateway profile credentials
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServerManagement/gateways/{gatewayName}/upgradetolatest
Upgrade a gateway to the latest build
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServerManagement/nodes/{nodeName}
Register a Windows node against a gateway
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServerManagement/nodes/{nodeName}/sessions/{session}/features/powerShellConsole/pssessions/{pssession}/invokeCommand
Run a PowerShell command on the remote node
GET
/subscriptions/{subscriptionId}/providers/Microsoft.ServerManagement/nodes
List all managed nodes in the subscription
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServerManagement/gateways/{gatewayName}
Create or update a Server Management gateway
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServerManagement/gateways/{gatewayName}/regenerateprofile
Regenerate the gateway profile credentials
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServerManagement/gateways/{gatewayName}/upgradetolatest
Upgrade a gateway to the latest build
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServerManagement/nodes/{nodeName}
Register a Windows node against a gateway
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServerManagement/nodes/{nodeName}/sessions/{session}/features/powerShellConsole/pssessions/{pssession}/invokeCommand
Run a PowerShell command on the remote node
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Azure AD service principal credentials sit in the Jentic vault. Agents get a short-lived bearer token scoped to user_impersonation — raw client secrets never enter the agent context, and PowerShell command output flows back through Jentic without secrets leaking into prompts.
Intent-based discovery
Agents search Jentic by intent such as run powershell on azure managed node or register windows node and Jentic returns the matching Microsoft.ServerManagement operation with its full input schema.
Time to first call
Direct integration: 1-2 days for AAD app registration, ARM token exchange, and async operation polling. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using ServerManagement API through Jentic.
Why is there no official OpenAPI spec for ServerManagement?
Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call ServerManagement via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the ServerManagement API use?
ServerManagement uses Azure AD OAuth 2.0 with the implicit flow against https://login.microsoftonline.com/common/oauth2/authorize and the user_impersonation scope. When called through Jentic, your AAD client credentials live in the Jentic vault and the agent receives a short-lived bearer token rather than the raw secret.
Can I run PowerShell on a remote server with this API?
Yes. Open a node session, then POST to /.../nodes/{nodeName}/sessions/{session}/features/powerShellConsole/pssessions/{pssession}/invokeCommand with the script. The cancel endpoint at the same path lets you abort a long-running command and the response stream returns stdout.
How do I register an on-premises Windows server as a managed node?
First PUT a gateway under /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServerManagement/gateways/{gatewayName}, install the gateway profile on a Windows host, then PUT a nodes/{nodeName} resource pointing at the FQDN of the target server with the gatewayId of the gateway you created.
What are the rate limits for the ServerManagement API?
Azure Resource Manager applies subscription-level throttling — typically 12,000 reads and 1,200 writes per hour per principal — and reports remaining quota in x-ms-ratelimit-remaining-subscription-reads and x-ms-ratelimit-remaining-subscription-writes. Jentic surfaces those headers so agents can pace themselves.
How do I rotate gateway credentials through Jentic?
Search Jentic for regenerate server management gateway profile, load the schema for POST /.../gateways/{gatewayName}/regenerateprofile, and execute it. The response contains the new profile that you install on the gateway host. The full search, load, and execute pattern is in the Jentic Python SDK after pip install jentic.
Is Server Management Tools still supported?
Microsoft retired the Server Management Tools portal experience in mid-2020, but the Microsoft.ServerManagement resource provider and this API remain reachable for environments that registered nodes before retirement. Treat new deployments as legacy and prefer Azure Arc for net-new hybrid Windows management.
GET STARTED