Microsoft Azure InfrastructureInsightsManagementClient

Name: InfrastructureInsightsManagementClient API
Brand: InfrastructureInsightsManagementClient
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsMonitoring Observabilityoauth24 EndpointsREST

For Agents

Install Jentic One Beta

Connect the InfrastructureInsightsManagementClient to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the InfrastructureInsightsManagementClient, 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.

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 | sh

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 instance

Jentic 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 InfrastructureInsightsManagementClient API.

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

GET STARTED

Start building with InfrastructureInsightsManagementClient API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use InfrastructureInsightsManagementClient API for, with concrete tasks.

★ 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.

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.

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.

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 MAXsystem injects a scoped bearer token into each admin-plane call.

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

4 endpoints — jentic publishes the only available openapi specification for infrastructureinsightsmanagementclient, keeping it validated and agent-ready.

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

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Azure AD OAuth 2.0 client secrets for the Azure Stack admin endpoint are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped bearer tokens for adminmanagement.local.azurestack.external — raw secrets never enter the agent's context.

Intent-based discovery

Agents search Jentic by intent (e.g. 'list azure stack alerts') and Jentic returns the matching InfrastructureInsights operation with its parameter schema, so the agent can call list, get, or repair without parsing Stack admin docs.

Time to first call

Direct InfrastructureInsights integration: 2-3 days to wire AAD against the Stack admin audience and handle ARM long-running operations. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using InfrastructureInsightsManagementClient API through Jentic.

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 at https://app.jentic.com/sign-up.

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 Jentic vault (MAXsystem) 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.