canonical: https://jentic.com/apis/azure.com/hanamanagementclient # Microsoft Azure HanaManagementClient 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. ## For AI agents Provision, restart, and tag SAP HANA Large Instance bare-metal hardware on Azure, and manage SAP monitor resources that observe the surrounding landscape. ## Scope 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. ## Capabilities - 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 ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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. Example prompt: 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 | 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 | ## Key resources - **HanaInstances** — Provision, list, get, update, delete, restart, start, and shut down SAP HANA Large Instances. - **SapMonitors** — Create, list, get, update, and delete SAP monitor resources that watch the SAP landscape. - **Operations** — Enumerate the operations supported by the Microsoft.HanaOnAzure provider. ## Why Jentic - **Setup:** Wiring SAP HANA on Azure by hand means setting up an Azure AD service principal, minting bearer tokens against management.azure.com, and polling the Azure-AsyncOperation header returned by long-running restart and provisioning calls. Through Jentic you install once, import SAP HANA Management from the API Directory, store the service principal credentials once, and your agent calls it. - **Permission scoping:** The HANA instance and SAP monitor names travel in the URL path (/hanaInstances/{hanaInstanceName}, /sapMonitors/{sapMonitorName}), so a rule can pin your agent to named instances. You choose the operations it may call, so destructive ones like shutting down or deleting a HANA instance are not included unless you add them. - **Credential handling:** Your Azure service principal credentials are stored once, encrypted, by your own Jentic One instance and exchanged for a scoped Azure AD bearer token at execution time. The client secret never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'restart an sap hana large instance' or 'create an sap monitor', and Jentic returns the matching HanaInstances or SapMonitors operation with its input schema so the agent calls the right ARM endpoint without browsing Microsoft Learn. ## Related APIs - **Azure Compute Management** — General-purpose Azure VM provisioning API. - **Azure Monitor** — Collect metrics and logs from HANA instances and SAP monitor resources. - **Azure Network** — Configures the VNets, subnets, and ExpressRoute connections HANA instances live in. ## FAQ ### 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 with Jentic One, the self-hosted execution layer. ### 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. ### Can I limit what my agent is allowed to do with the Azure SAP HANA Management API? Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use, so you choose whether it can only list and get HANA instances and SAP monitors or also call lifecycle operations like restart, start, provision, or delete. The instance and monitor names travel in the URL path, at /hanaInstances/{hanaInstanceName} and /sapMonitors/{sapMonitorName}, so a rule can pin the agent to specific named resources. Destructive operations such as shutting down or deleting a HANA instance are excluded unless you explicitly grant them.