canonical: https://jentic.com/apis/azure.com/fabric-admin-client

# Microsoft Azure FabricAdminClient

Jentic publishes the only available OpenAPI specification for the Azure Stack FabricAdminClient, keeping it validated and agent-ready. This narrow administrative API returns the status of fabric application operation results at a given Azure Stack location. Operators use it to check whether long-running fabric application operations have succeeded, failed, or are still in progress.

## For AI agents

Read the status of long-running fabric application operations at an Azure Stack location.

## Scope

Does not initiate fabric application operations, manage compute or storage resources, or change Azure Stack configuration - use only to read the status of fabric application operation results at a location.

## Capabilities

- List all fabric application operation results at a specified Azure Stack location
- Read the status of a specific fabric application operation by id
- Check whether a fabric application operation has succeeded or failed at a location
- Scope queries to a particular subscription, resource group, and Azure Stack fabric location

## Use cases

### Track Long-Running Fabric Operations

Azure Stack operators run fabric application operations that complete asynchronously. GET /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Fabric.Admin/fabricLocations/{location}/applicationOperationResults/{operation} returns the current state of a specific operation so an operator script can poll until the operation is complete before triggering follow-on work.

Example prompt: Get the status of operation op-12345 at fabric location local in resource group System.local and return whether it has reached a terminal state

### Audit Recent Fabric Operations at a Location

During a maintenance review, operators list every fabric application operation at a location to confirm no operation has stalled or failed. The list endpoint returns all operation result entries at the location so the audit can flag any that did not reach a successful terminal state.

Example prompt: List all application operation results at fabric location local in resource group System.local and return any whose status is not Succeeded

### Health Probe for Azure Stack Automation

Automation scripts use this API as a lightweight health probe before issuing further fabric admin calls. If the operation results list returns successfully, the calling automation knows the fabric admin endpoint is reachable and AAD authentication is valid for the current location and resource group.

Example prompt: Call ApplicationOperationResults_List at location local and return success or the HTTP error code

### Agent-Driven Azure Stack Operation Monitoring

An AI agent assisting an Azure Stack operator can poll fabric application operation results through Jentic until the operator-initiated change reports a terminal state. Intent search returns the operation results endpoints with their schemas; the AAD admin token is held in your Jentic One instance so the agent never sees the service principal secret used for fabric admin calls.

Example prompt: Search Jentic for 'get Azure Stack fabric operation result', execute ApplicationOperationResults_Get for op-12345 every 30 seconds until the response status is Succeeded or Failed

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Fabric.Admin/fabricLocations/{location}/applicationOperationResults | List all application operation results at a fabric location |
| GET | /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Fabric.Admin/fabricLocations/{location}/applicationOperationResults/{operation} | Get the status of a specific application operation |

## Key resources

- **ApplicationOperationResults** — List all application operation results at a fabric location and read the status of a specific operation

## Why Jentic

- **Setup:** Wiring the Azure Stack FabricAdminClient by hand means obtaining Azure AD OAuth 2.0 admin tokens for the stamp against the adminmanagement.local.azurestack.external endpoint rather than public management.azure.com, building the Microsoft.Fabric.Admin path, and polling operation results on a loop. Through Jentic you install once, import FabricAdminClient from the API Directory, store the Azure AD admin credentials once, and your agent calls it.
- **Permission scoping:** The API puts the subscription, resource group, fabric location, and operation id in the URL path (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Fabric.Admin/fabricLocations/{location}/applicationOperationResults/{operation}), so a rule can pin your agent to one fabric location. Both operations are read-only GETs, so limit the agent to ApplicationOperationResults_List and ApplicationOperationResults_Get, which is all this API exposes.
- **Credential handling:** Your Azure AD admin credentials for the Azure Stack tenant are stored once, encrypted, by your own Jentic One instance and injected at execution time as a scoped bearer token. The admin service principal secret never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get an Azure Stack fabric operation result' or 'list fabric application operations at a location', and Jentic returns ApplicationOperationResults_Get or ApplicationOperationResults_List with its input schema so the agent calls the right endpoint without memorising the Microsoft.Fabric.Admin path.

## Related APIs

- **Azure Stack Deployment Admin Client** — Manages Azure Stack deployment-level admin operations alongside fabric admin reads.
- **Azure Stack Infrastructure Insights** — Reports on Azure Stack alerts, regions, and infrastructure health that drive operator response.
- **Azure Stack Compute Admin Client** — Manages compute resource provider administration on Azure Stack.
- **Azure Stack Network Admin Client** — Sister Azure Stack admin API for network resource provider operations rather than fabric application operations.

## FAQ

### Why is there no official OpenAPI spec for FabricAdminClient?

Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call FabricAdminClient 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 FabricAdminClient use?

The API uses Azure Active Directory OAuth 2.0 bearer tokens (the azure_auth scheme) against the Azure Stack admin endpoint adminmanagement.local.azurestack.external. Through Jentic, the AAD admin service principal secret is stored encrypted in your Jentic One instance.

### Can I get the status of a fabric application operation with this API?

Yes. Call GET /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Fabric.Admin/fabricLocations/{location}/applicationOperationResults/{operation}. The response carries the current operation status, which an automation can poll until it reaches a terminal state.

### What location value should I pass on the path?

The {location} path parameter is the Azure Stack fabric location identifier (typically 'local' for an integrated system). The same location appears on the corresponding ARM resource ids you read or update through other Azure Stack admin APIs.

### What are the rate limits for this API?

Azure Stack admin endpoints apply per-stamp throttling. Polling at intervals of 15-30 seconds is safe for operation result tracking; on HTTP 429 back off using the Retry-After header. The API only supports GET, so there is no mutation budget to consider.

### How do I poll fabric operation results from an agent through Jentic?

Run pip install jentic, then search Jentic with 'get Azure Stack fabric operation result'. Load ApplicationOperationResults_Get, supply the subscription, resource group, location, and operation id, and execute on a polling loop. The AAD admin token is sourced from the vault on every call.

### Can I limit what my agent is allowed to do with the Azure Stack Fabric Admin Client API?

Yes. Jentic One is self-hosted, so you write the rules that decide which operations and credentials your agent may use, and this API only exposes two read-only GET operations, ApplicationOperationResults_List and ApplicationOperationResults_Get, which you can allow or withhold individually. Because the subscription, resource group, and fabric location live in the request path, your rules can pin the agent to a single location, resource group, and subscription so it can only read operation results for that scope. The Azure AD admin credentials stay in your own Jentic One instance and are injected only when a permitted call runs, so the agent never gains the ability to initiate fabric operations or change any Azure Stack configuration.