Microsoft Azure HanaManagementClient
Browse all Azure APIs★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputeoauth215 EndpointsREST
For Agents
Provision, restart, and tag SAP HANA Large Instance bare-metal hardware on Azure, and manage SAP monitor resources that observe the surrounding landscape.
Use for: I need to provision a new SAP HANA Large Instance for production, Restart the HANA instance 'hana-prod-01' in resource group 'sap-rg', Shut down a HANA Large Instance ahead of a maintenance window, List all SAP HANA instances in subscription 'sub-sap'
Not supported: Does not run SAP transactions, configure HANA database parameters, or manage standard Azure VMs — use for HANA Large Instance and SAP monitor resource management only.
Jentic publishes the only available OpenAPI specification for HanaManagementClient, keeping it validated and agent-ready. The SAP HANA on Azure Management API manages dedicated HANA Large Instance bare-metal hardware and the SAP monitor companion service through Azure Resource Manager. Operators provision and patch HANA instances, restart or shut them down, and create SAP monitors that observe the broader SAP landscape. The API is authenticated via Azure AD OAuth2 against management.azure.com and exposes 15 operations split between hanaInstances and sapMonitors.
Install Jentic One Beta
Connect the HanaManagementClient to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the HanaManagementClient, 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 HanaManagementClient API.
Provision a new SAP HANA Large Instance and tag it with workload metadata
List HANA Large Instances across a subscription or filter by resource group
Restart, shut down, or start an SAP HANA Large Instance
Patch the tags on a HANA instance without recreating it
Create or update an SAP monitor resource that watches the SAP landscape
List or delete SAP monitors as part of landscape lifecycle management
Enumerate the operations supported by the Microsoft.HanaOnAzure provider
Use Cases
Patterns agents use HanaManagementClient API for, with concrete tasks.
★ Provision a HANA Large Instance for an SAP workload
Create a SAP HANA Large Instance via PUT on /subscriptions/.../hanaInstances/{hanaInstanceName} with sizing, OS, and network parameters drawn from the SAP sizing exercise. The bare-metal hardware is dedicated to the customer and registered into Azure Resource Manager so it can be managed alongside other Azure resources. Suitable for SAP S/4HANA migrations to Azure.
Create a HANA Large Instance named 'hana-prod-01' in resource group 'sap-rg' with the agreed SKU and tag costCentre=SAP-PROD.
Lifecycle operations on running HANA hardware
Restart, shut down, or start an instance via the dedicated POST endpoints on /hanaInstances/{name}/restart, /shutdown, and /start. These are long-running ARM operations and return 202 with an Azure-AsyncOperation header that the caller polls until completion. Useful for scheduled patching windows.
POST /subscriptions/{sub}/resourceGroups/sap-rg/providers/Microsoft.HanaOnAzure/hanaInstances/hana-prod-01/restart and poll the async operation until it reports Succeeded.
Manage SAP monitors for a landscape
Create and update SAP monitor resources that aggregate telemetry from the SAP landscape on Azure. The sapMonitors operations support create, update, delete, get, and list, mirroring the hanaInstances surface. Useful when standing up monitoring for a new SAP project.
Create an SAP monitor resource named 'sap-mon-prod' in resource group 'sap-rg' targeting the workload subnet in vnet 'sap-vnet'.
AI agent SAP operations through Jentic
An SAP basis agent uses Jentic to find HanaManagementClient operations, load their input schemas, and execute restarts, tag updates, or monitor changes without holding raw Azure credentials. Jentic resolves natural-language intents to the correct ARM operation and injects the bearer token at execution time.
Use Jentic to search for 'restart an sap hana large instance', load HanaInstances_Restart, and execute it for 'hana-prod-01' during the agreed maintenance window.
Key Endpoints
15 endpoints — jentic publishes the only available openapi specification for hanamanagementclient, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HanaOnAzure/hanaInstances/{hanaInstanceName}
Create a HANA Large Instance
GET
/subscriptions/{subscriptionId}/providers/Microsoft.HanaOnAzure/hanaInstances
List HANA instances in a subscription
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HanaOnAzure/hanaInstances/{hanaInstanceName}/restart
Restart a HANA instance
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HanaOnAzure/hanaInstances/{hanaInstanceName}/shutdown
Shut down a HANA instance
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HanaOnAzure/sapMonitors/{sapMonitorName}
Create or update an SAP monitor
DELETE
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HanaOnAzure/hanaInstances/{hanaInstanceName}
Delete a HANA instance
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HanaOnAzure/hanaInstances/{hanaInstanceName}
Create a HANA Large Instance
GET
/subscriptions/{subscriptionId}/providers/Microsoft.HanaOnAzure/hanaInstances
List HANA instances in a subscription
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HanaOnAzure/hanaInstances/{hanaInstanceName}/restart
Restart a HANA instance
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HanaOnAzure/hanaInstances/{hanaInstanceName}/shutdown
Shut down a HANA instance
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HanaOnAzure/sapMonitors/{sapMonitorName}
Create or update an SAP monitor
DELETE
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HanaOnAzure/hanaInstances/{hanaInstanceName}
Delete a HANA instance
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Azure service principal credentials are stored encrypted in the Jentic vault. Agents receive a scoped Azure AD bearer token at execution time and never see the raw client secret.
Intent-based discovery
Agents search Jentic with intents like 'restart sap hana large instance' and Jentic returns the matching HanaInstances operation with its input schema, so the agent can call the right ARM endpoint without browsing Microsoft Learn.
Time to first call
Direct ARM integration: 2-4 days for AAD setup, async operation polling, and HANA-specific input shapes. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using HanaManagementClient API through Jentic.
Why is there no official OpenAPI spec for HanaManagementClient?
Microsoft Azure does not publish a stand-alone OpenAPI specification for the SAP HANA on Azure Management API. Jentic generates and maintains this spec from the Microsoft.HanaOnAzure ARM surface so that AI agents and developers can call HanaManagementClient 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 this API use?
It uses Azure AD OAuth2 against management.azure.com, declared as the azure_auth security scheme. Through Jentic, your service principal credentials are stored encrypted in the vault and exchanged for a scoped bearer token at execution time.
Can I restart a HANA instance through this API?
Yes. POST on /subscriptions/.../hanaInstances/{hanaInstanceName}/restart triggers an async restart and returns 202 with an Azure-AsyncOperation header. There are matching /shutdown and /start endpoints for full power-state control.
What are the rate limits?
Standard ARM throttles apply at the subscription level — about 12,000 reads and 1,200 writes per hour per subscription. HANA lifecycle operations are long-running, so callers should poll the async operation rather than retry the original POST.
How do I provision a HANA instance through Jentic?
Run jentic.search('provision sap hana large instance on azure'), load the HanaInstances_Create schema, and execute it with the subscription, resource group, instance name, location, and SKU details. The PUT returns 202 and the async operation reports success once provisioning completes.
GET STARTED