Microsoft Azure FabricAdminClient

Name: FabricAdminClient API
Brand: Azure Stack Fabric Admin Client
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputeoauth22 Endpoints

Install Jentic One Beta

Connect the FabricAdminClient to your agent

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

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

GET STARTED

Start building with FabricAdminClient API

Explore with Jentic

View OpenAPI Document

For Agents

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

Use for: List all fabric application operation results at location local, Get the status of fabric application operation op-12345 at location local, Check whether the latest fabric application operation succeeded in resource group System.local, Find any failed application operation results at the local fabric location

Not supported: 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.

Use Cases

Patterns agents use FabricAdminClient API for, with concrete tasks.

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

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.

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.

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.

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

2 endpoints — jentic publishes the only available openapi specification for the azure stack fabricadminclient, keeping it validated and agent-ready.

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

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

Why Jentic?

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

Credential isolation

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.

Intent-based discovery

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.

Time to first call

FAQs

Specific to using FabricAdminClient API through Jentic.

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.