canonical: https://jentic.com/apis/azure.com/blueprintclient

# Microsoft Azure BlueprintClient

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.

## For AI agents

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

## Scope

Does not handle blueprint definition authoring, policy evaluation, or ARM template execution - use for inspecting blueprint assignment operations only.

## Capabilities

- 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
- Audit when and how blueprint artifacts were applied to a target scope

## Use cases

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

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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

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

## Key resources

- **Assignment Operations** — List and retrieve long-running operations executed when a blueprint is assigned to a scope

## Why Jentic

- **Setup:** Wiring the BlueprintClient by hand means configuring Azure AD OAuth2 against management.azure.com and constructing the scoped Microsoft.Blueprint assignment operations paths, where the scope segment can be a subscription or management group, yourself. Through Jentic you install once, import the BlueprintClient from the API Directory, store the Azure AD credential once, and your agent calls it.
- **Permission scoping:** This API puts the scope, assignment name, and operation id in the URL path (/{scope}/providers/Microsoft.Blueprint/blueprintAssignments/{assignmentName}/assignmentOperations/{assignmentOperationName}), so a rule can pin your agent to one assignment's operation history. Both endpoints are read-only lookups of assignment operations, so no write or destructive action is reachable unless you add such operations.
- **Credential handling:** Your Azure AD credential 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.
- **Discovery method:** Agents search Jentic by intent such as 'check Azure Blueprint assignment status', and Jentic returns the matching assignment operations lookup with its input schema so the agent calls the right ARM path without browsing the Microsoft.Blueprint reference.

## Related APIs

- **ConsumptionManagementClient** — Read consumption and reservation data for the subscriptions a blueprint targets
- **CognitiveServicesManagementClient** — Manage Cognitive Services accounts that a landing-zone blueprint may provision
- **ComputeManagementConvenienceClient** — Deploy compute via ARM template deployments instead of governance blueprints

## FAQ

### 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 with Jentic One, the self-hosted execution layer.

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

### Can I limit what my agent is allowed to do with the Microsoft Azure Blueprint API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use. This API puts the scope, assignment name, and operation id directly in the URL path, so you can pin the agent to a single assignment's operation history rather than a whole subscription or management group. Both endpoints only list and read assignment operations, so no write or destructive action is reachable unless you explicitly add such operations.