Microsoft Azure ServerManagement

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 your Jentic One instance 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.

Can I limit what my agent is allowed to do with the Server Management API?

Yes. Because you run Jentic One yourself, your own rules decide which Server Management operations and credentials the agent may use. Since the gateway and node names sit in the URL path, you can pin the agent to a single gateway or node and choose the exact operations it may call. For example, you can let it open a session and invoke a PowerShell command while withholding gateway profile regeneration until you explicitly allow it.