Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Developer Tools / Azure / InfrastructureInsightsManagementClient
InfrastructureInsightsManagementClient logo

Microsoft Azure InfrastructureInsightsManagementClient

Browse all Azure APIs
39
AI ReadinessNon-Ready (F)39/100
See full scorecard
Agent-ready OpenAPI document · curated by JenticDeveloper ToolsMonitoring Observabilityoauth24 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

List Azure Stack region health alerts, inspect alert detail, and trigger automated repair against an Azure Stack Hub stamp.

Use for: List all open infrastructure alerts for my Azure Stack region, Get the details of a specific Azure Stack alert by name, Trigger a repair on a failing Azure Stack alert, Check whether an alert has cleared after a repair attempt

Not supported: Does not handle public Azure resource health, metric collection, or log analytics - use for Azure Stack Hub region alert listing and repair only.

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.

Jentic One on GithubView OpenAPI Document

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.

1

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Finfrastructureinsightsmanagementclient" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Finfrastructureinsightsmanagementclient" | 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

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

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

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

I

InfrastructureInsightsManagementClient

- Non-Ready (F)
39/100
74
Foundational Compliance
56
Developer Experience & Jentic Compatibility
18
AI-Readiness & Agent Experience
94
Agent Usability
35
Security
100
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
74

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4
95%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

0%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

56

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: CSignals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

25%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

18

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4
70%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

0%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

0%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

35

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1
35%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1
100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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

Alternatives and complements available in the Jentic catalogue.

Complementary

Azure HybridData Management

→

HybridData manages data movement between Stack and Azure that an Insights operator may need to triage when alerts fire.

Use HybridData when an alert relates to hybrid data movement jobs rather than platform region health.

Complementary

Azure Key Vault

→

Key Vault holds secrets and certificates that Stack operations depend on; alerts may surface vault availability issues.

Use Key Vault when remediation requires rotating or fetching secrets referenced by Stack workloads.

Alternative

Azure IoT Hub

→

IoT Hub exposes its own device-side health and routing surface separate from Stack region health.

Choose IoT Hub when the workload health you care about is device connectivity rather than Stack platform regions.

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

GET STARTED

Start building with InfrastructureInsightsManagementClient API

Explore with Jentic One
View OpenAPI Document