BlueprintClient

Name: BlueprintClient API
Brand: BlueprintClient
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputeoauth22 EndpointsREST

For Agents

List and inspect Azure Blueprint assignment operations to monitor governance rollouts across subscriptions and management groups.

Connect the BlueprintClient to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the BlueprintClient, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

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

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

List blueprint assignment operations for a given assignment to track rollout progress

Retrieve a specific assignment operation by name to read its provisioning state and artifact-level results

Monitor long-running blueprint deployments scoped to a subscription or management group

Diagnose failed governance artifact applications by reading per-operation error details

GET STARTED

Start building with BlueprintClient API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for BlueprintClient, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for BlueprintClient, keeping it validated and agent-ready. BlueprintClient is the Azure Blueprints management surface for inspecting blueprint assignment operations as they apply governance artifacts (policies, role assignments, resource groups, ARM templates) to subscriptions or management groups. The 2018-11-01-preview API exposes long-running assignment operation tracking so that automation can poll the progress of a blueprint rollout and react to per-artifact failures. It targets Azure Resource Manager and authenticates through Azure Active Directory OAuth2.

Use Cases

Patterns agents use BlueprintClient API for, with concrete tasks.

★ Track blueprint rollout progress

When a platform team assigns an Azure Blueprint to a subscription, the assignment runs as a long-running operation that applies multiple artifacts in sequence. BlueprintClient lets automation list assignmentOperations under an assignment and poll each operation for its provisioningState. This is how a governance pipeline knows when a rollout is complete and whether every artifact succeeded, without scraping the Azure Portal.

List all assignmentOperations under blueprintAssignments/{assignmentName} for a target subscription scope and report the provisioningState of the most recent operation.

Diagnose failed governance artifacts

Blueprint assignments often fail on a single artifact (a policy, role assignment, or ARM template) while the rest succeed. BlueprintClient exposes per-operation detail so an agent can pinpoint which artifact failed and surface the underlying error message. This shortens incident response when a landing-zone rollout breaks and avoids manual log spelunking.

Get the assignmentOperation named {assignmentOperationName} under a failing blueprint assignment and extract the artifact-level error fields from the response.

Governance audit trail extraction

Compliance teams need a machine-readable history of when blueprints were applied and what they did. By iterating assignmentOperations across scopes, BlueprintClient produces a structured audit trail of governance changes that can be loaded into a SIEM or change-management system. This avoids relying on Activity Log scraping for blueprint-specific lineage.

Iterate every blueprintAssignment under a management-group scope, list its assignmentOperations, and emit a CSV row per operation with timestamp, scope, and provisioningState.

AI agent governance assistant

An agent connected via Jentic can answer operator questions like 'did last night's blueprint rollout finish cleanly on subscription X?' by calling BlueprintClient through Jentic's MCP tooling. Jentic handles the Azure AD OAuth2 flow and returns the operation list and detail in a structured form the agent can summarise, so the operator never opens the portal.

Use Jentic to search 'check Azure Blueprint assignment status', load the listAssignmentOperations operation, and return a natural-language summary of the latest assignment outcome for the requested scope.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/{scope}/providers/Microsoft.Blueprint/blueprintAssignments/{assignmentName}/assignmentOperations

List assignment operations for a blueprint assignment

GET

/{scope}/providers/Microsoft.Blueprint/blueprintAssignments/{assignmentName}/assignmentOperations/{assignmentOperationName}

Get a specific blueprint assignment operation

GET

/{scope}/providers/Microsoft.Blueprint/blueprintAssignments/{assignmentName}/assignmentOperations

List assignment operations for a blueprint assignment

GET

/{scope}/providers/Microsoft.Blueprint/blueprintAssignments/{assignmentName}/assignmentOperations/{assignmentOperationName}

Get a specific blueprint assignment operation

Why though Jentic?

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

Credential isolation

Azure AD tokens for BlueprintClient are stored encrypted in the Jentic vault (MAXsystem). Agents receive a scoped execution handle — raw bearer tokens never enter the agent's context, so blueprint operations cannot be replayed outside Jentic's audit boundary.

Intent-based discovery

Agents search Jentic by intent (e.g. 'check Azure Blueprint assignment status') and Jentic returns the matching BlueprintClient operation with its input schema, so the agent calls the right ARM path without browsing the Microsoft.Blueprint reference.

Time to first call

Direct integration with BlueprintClient: 1-2 days for AAD app registration, token acquisition, and ARM polling. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

ConsumptionManagementClient

Read consumption and reservation data for the subscriptions a blueprint targets

Pair with BlueprintClient when an agent needs to correlate a governance rollout with the spend it produced on the same subscription.

Complementary

CognitiveServicesManagementClient

Manage Cognitive Services accounts that a landing-zone blueprint may provision

Use after a blueprint rollout when the agent must verify Cognitive Services accounts created by the assignment exist and are configured correctly.

Alternative

ComputeManagementConvenienceClient

Deploy compute via ARM template deployments instead of governance blueprints

Choose this when the goal is a one-off compute deployment rather than a repeatable governance package with policies and role assignments.

FAQs

Specific to using BlueprintClient API through Jentic.

Why is there no official OpenAPI spec for BlueprintClient?

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

BlueprintClient uses Azure Active Directory OAuth2 with the implicit flow against https://login.microsoftonline.com/common/oauth2/authorize and the user_impersonation scope. Through Jentic, the AAD token is held in the encrypted vault and never enters the agent's context — the agent receives a scoped execution handle instead of the raw bearer.

Can I list assignment operations for a blueprint with this API?

Yes. Issue GET /{scope}/providers/Microsoft.Blueprint/blueprintAssignments/{assignmentName}/assignmentOperations where scope is a subscription or management-group path. The response is a paged list of operations with provisioningState fields you can poll until terminal.

What are the rate limits for the BlueprintClient?

The spec does not declare explicit rate limits. In practice, Azure Resource Manager applies tenant-wide ARM throttling (commonly 12,000 reads per hour per subscription). Honour the Retry-After header on 429 responses; Jentic surfaces these headers directly in the execution result.

How do I poll a blueprint assignment operation through Jentic?

Run pip install jentic, then search for 'check Azure Blueprint assignment status', load the getAssignmentOperation operation, and execute with scope, assignmentName, and assignmentOperationName. Jentic returns the structured response including provisioningState so the agent can loop until Succeeded or Failed.

Is the BlueprintClient free?

Azure Blueprints itself has no per-call charge — you pay only for the resources blueprints provision. ARM API calls are subject to subscription-level throttling rather than billing.