canonical: https://jentic.com/apis/azure.com/infrastructureinsightsmanagementclient # Microsoft Azure InfrastructureInsightsManagementClient Jentic publishes the only available OpenAPI specification for InfrastructureInsightsManagementClient, keeping it validated and agent-ready. The Azure Stack Infrastructure Insights admin API surfaces region health alerts for an Azure Stack Hub stamp so operators can list, inspect, and repair alerts raised by the platform. It exposes 4 ARM admin endpoints under Microsoft.InfrastructureInsights.Admin/regionHealths to enumerate alerts in a location and trigger a repair workflow on an individual alert. ## For AI agents List Azure Stack region health alerts, inspect alert detail, and trigger automated repair against an Azure Stack Hub stamp. ## Scope Does not handle public Azure resource health, metric collection, or log analytics - use for Azure Stack Hub region alert listing and repair only. ## Capabilities - List active region health alerts for an Azure Stack Hub location - Retrieve detail for a specific alert by alertName under a region health resource - Trigger an automated repair workflow on a named alert - Scope all calls to a subscription, resource group, and location for tenant isolation - Authenticate with Azure AD against the Azure Stack admin endpoint ## Use cases ### Azure Stack Hub Health Monitoring Operators of an Azure Stack Hub stamp poll the regionHealths/{location}/alerts list to surface active platform alerts in a custom dashboard or Slack channel. Because the admin API exposes alerts by location, a single subscription-scoped script can cover every Azure Stack region the operator manages. Setup against an existing Stack stamp is a half-day exercise. Example prompt: List all alerts under regionHealth 'redmond' for the Stack admin subscription and print any with severity 'Critical'. ### Automated Alert Repair Workflow Wire alert detection to an automatic remediation flow by polling the alerts list, then POSTing to /alerts/{alertName}/repair for any alert that has a known remediation. Repairs are run by the platform itself, so the workflow only has to identify and dispatch them. This pattern reduces mean-time-to-repair for routine Azure Stack faults. Example prompt: For every alert in regionHealth 'eastus' with state 'Active', call repair on its alertName. ### Alert Audit and Reporting Build a periodic audit by walking every resource group's regionHealths and capturing alert counts by severity and status. The output supports SLA reporting for Azure Stack tenants and feeds into capacity planning. Because alerts are scoped under regionHealths/{location}, the audit is naturally partitioned by Stack stamp. Example prompt: Produce a CSV of all alerts across regionHealths in the subscription with columns alertName, severity, state, location. ### Agent-Driven Stack Operations via Jentic An AI ops agent can list Azure Stack alerts and trigger repairs through Jentic without holding raw AAD credentials. The agent searches Jentic for 'list azure stack alerts', loads the operation schema, and executes with the subscription, resource group, and location. Jentic's your Jentic One instance injects a scoped bearer token into each admin-plane call. Example prompt: Use the Jentic MCP tool azure_infrastructureinsights_list_alerts to get all alerts in regionHealth 'redmond' and call repair on the first Critical one. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.InfrastructureInsights.Admin/regionHealths/{location}/alerts | List alerts under a region health | | GET | /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.InfrastructureInsights.Admin/regionHealths/{location}/alerts/{alertName} | Get a single alert by name | | POST | /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.InfrastructureInsights.Admin/regionHealths/{location}/alerts/{alertName}/repair | Trigger a repair workflow on the named alert | ## Key resources - **Alerts** — Region health alerts raised by the Azure Stack platform; supports list, get, and repair - **RegionHealths** — Per-location container under which alerts are scoped ## Why Jentic - **Setup:** Wiring the Azure Stack Hub InfrastructureInsights admin API by hand means registering an Azure AD app against your Azure Stack admin endpoint, negotiating OAuth 2.0 tokens, and pointing calls at the adminmanagement.local.azurestack.external host rather than public Azure. Through Jentic you install once, import InfrastructureInsightsManagementClient from the API Directory, store the Azure AD credential once, and your agent calls it. - **Permission scoping:** This API puts the region and alert in the URL path (/regionHealths/{location}/alerts/{alertName}), so a rule can pin your agent to one region's alerts: it can list and read alerts for that location. You choose the operations it may call, so triggering an alert repair is not included unless you add it. - **Credential handling:** Your Azure AD credential for the Azure Stack admin surface is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'list Azure Stack region health alerts' or 'repair a region alert', and Jentic returns the matching InfrastructureInsights operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Azure HybridData Management** — HybridData manages data movement between Stack and Azure that an Insights operator may need to triage when alerts fire. - **Azure Key Vault** — Key Vault holds secrets and certificates that Stack operations depend on; alerts may surface vault availability issues. - **Azure IoT Hub** — IoT Hub exposes its own device-side health and routing surface separate from Stack region health. ## FAQ ### Why is there no official OpenAPI spec for InfrastructureInsightsManagementClient? Microsoft does not publish a maintained OpenAPI 3 specification for the Azure Stack InfrastructureInsights admin surface. Jentic generates and maintains this spec so that AI agents and developers can call InfrastructureInsightsManagementClient 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 the InfrastructureInsightsManagementClient use? It uses Azure Active Directory OAuth 2.0 against the Azure Stack admin endpoint (adminmanagement.local.azurestack.external). Through Jentic the AAD client secret is held in the your Jentic One instance and a scoped bearer token is injected per call so the agent never holds raw secrets. ### Can I auto-repair an alert with this API? Yes. POST to /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.InfrastructureInsights.Admin/regionHealths/{location}/alerts/{alertName}/repair to invoke the platform's built-in repair workflow for that alert. Subsequent GET on the alert reflects the post-repair state. ### What are the rate limits for InfrastructureInsightsManagementClient? It runs on the Azure Stack admin ARM plane, which inherits standard Azure Resource Manager throttling - typically 12,000 reads and 1,200 writes per hour per subscription, surfaced via x-ms-ratelimit-remaining-subscription-* headers. The provider does not document tighter per-resource limits. ### How do I list region alerts through Jentic? Run pip install jentic, then search Jentic with 'list azure stack alerts', load the list-alerts operation, and execute with subscriptionId, resourceGroupName, and location. Jentic returns the JSON array of alert resources for that regionHealth. ### Does this API work against public Azure or only Azure Stack? Only against Azure Stack Hub admin endpoints - the base URL is the local admin management host (adminmanagement.local.azurestack.external). For public Azure platform health, use the Azure Resource Health and Azure Service Health APIs instead. ### Can I limit what my agent is allowed to do with the Azure Stack InfrastructureInsights API? Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use. This API carries the region and alert in the URL path (/regionHealths/{location}/alerts/{alertName}), so a rule can pin the agent to a single location and let it only list and read alerts there. Since you choose the operations it may call, triggering an alert repair stays off unless you explicitly allow that operation.