PowerBIDedicated

Name: PowerBIDedicated API
Brand: PowerBIDedicated
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputeoauth212 EndpointsREST

For Agents

Provision, scale, suspend, and resume Power BI Dedicated capacities in Azure, and list available SKUs and operations for the Microsoft.PowerBIDedicated resource provider.

Connect the PowerBIDedicated to your agent

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

Provision a Power BI Dedicated capacity in a resource group

Suspend or resume a Power BI Dedicated capacity to control billing

Update the SKU or tags on an existing capacity

List Power BI Dedicated capacities at subscription or resource-group scope

GET STARTED

Start building with PowerBIDedicated API

Explore with Jentic

View OpenAPI Document

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

Jentic publishes the only available OpenAPI specification for PowerBIDedicated, keeping it validated and agent-ready. The API manages Power BI Dedicated capacities under Microsoft.PowerBIDedicated in Azure Resource Manager — the per-tenant compute capacities (A SKUs) that back embedded Power BI workloads. It covers the full capacity lifecycle, including provisioning, scaling, suspend and resume, plus SKU listings and name availability checks.

Use Cases

Patterns agents use PowerBIDedicated API for, with concrete tasks.

★ Embedded analytics capacity provisioning

Teams that embed Power BI reports into customer-facing applications need a dedicated capacity sized to their tenant load. The API provisions a Microsoft.PowerBIDedicated capacity at the chosen SKU, returns the provisioning state, and exposes the listing endpoints needed to surface capacity status in an internal control plane.

Create a Power BI Dedicated capacity named 'analytics-prod-eu' at SKU A2 in resource group 'analytics-rg' in West Europe

Cost control via suspend and resume

Power BI Dedicated capacities are billed per hour, so suspending them outside business hours is a common cost-saver. The API exposes dedicated suspend and resume endpoints so a scheduler can pause capacities overnight and resume them before users return, without redeploying the resource.

Suspend the Power BI Dedicated capacity 'analytics-prod-eu' at 19:00 and resume it at 07:00 on weekdays

SKU scaling for usage spikes

Demand on embedded analytics often spikes around month-end reporting, so capacity SKUs need to scale up before the load hits and back down once it passes. The API supports updating the SKU on the capacity in place, and lists the SKUs available for a given capacity so the agent can pick a valid target tier.

Scale the Power BI Dedicated capacity 'analytics-prod-eu' from A2 to A4 ahead of the month-end window and back to A2 afterwards

Agent-driven capacity management

An AI agent fronting an analytics control plane accepts capacity sizing requests, validates the desired name, provisions or rescales the capacity, and posts the resulting state back to the requestor. Jentic isolates the Azure AD client secret so the agent only ever sees scoped bearer tokens.

Given a tenant request for capacity 'tenant-foo' at A1, validate the name and provision the capacity in West US 2, returning the provisioning state

Key Endpoints

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

METHOD

PATH

DESCRIPTION

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.PowerBIDedicated/capacities/{dedicatedCapacityName}

Create or update a dedicated capacity

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.PowerBIDedicated/capacities/{dedicatedCapacityName}

Get a specific dedicated capacity

PATCH

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.PowerBIDedicated/capacities/{dedicatedCapacityName}

Update SKU or tags on a capacity

DELETE

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.PowerBIDedicated/capacities/{dedicatedCapacityName}

Delete a dedicated capacity

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.PowerBIDedicated/capacities/{dedicatedCapacityName}/suspend

Suspend a capacity

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.PowerBIDedicated/capacities/{dedicatedCapacityName}/resume

Resume a suspended capacity

GET

/subscriptions/{subscriptionId}/providers/Microsoft.PowerBIDedicated/skus

List available capacity SKUs

POST

/subscriptions/{subscriptionId}/providers/Microsoft.PowerBIDedicated/locations/{location}/checkNameAvailability

Check capacity name availability

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.PowerBIDedicated/capacities/{dedicatedCapacityName}

Create or update a dedicated capacity

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.PowerBIDedicated/capacities/{dedicatedCapacityName}

Get a specific dedicated capacity

PATCH

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.PowerBIDedicated/capacities/{dedicatedCapacityName}

Update SKU or tags on a capacity

DELETE

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.PowerBIDedicated/capacities/{dedicatedCapacityName}

Delete a dedicated capacity

POST

Why though Jentic?

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

Credential isolation

Azure AD OAuth 2.0 client credentials are stored encrypted in the Jentic vault. Agents receive a scoped bearer token at execute time; client secrets and refresh tokens never reach the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'scale power bi dedicated capacity') and Jentic returns the matching update operation with the SKU parameters resolved from the spec.

Time to first call

Direct integration with the Microsoft.PowerBIDedicated ARM API, including AAD setup and async polling for suspend, resume, and scale operations, typically takes 1-2 days. Through Jentic: under 1 hour to first successful capacity action.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Power BI Embedded Management Client

The legacy Power BI Embedded workspace collections API that PowerBIDedicated replaced

Pick this only when an existing workload still uses the legacy workspace collection model rather than dedicated A-SKU capacities.

Complementary

App Service Plans API Client

Provisions the App Service plan that typically hosts the application embedding Power BI

Pick this when the agent also needs to size or scale the web application that renders the embedded Power BI reports.

Complementary

SQL Management Client

Manages Azure SQL databases that commonly back Power BI datasets

Pick this when the agent also needs to provision or scale the Azure SQL data source feeding the Power BI dataset.

FAQs

Specific to using PowerBIDedicated API through Jentic.

Why is there no official OpenAPI spec for PowerBIDedicated?

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

The API runs through Azure Resource Manager and uses OAuth 2.0 bearer tokens issued by Azure Active Directory under the azure_auth scheme with the user_impersonation scope. Through Jentic, the AAD client secret or refresh token is held in the encrypted vault and a short-lived access token is supplied at execute time so the secret never appears in the agent's context.

Can I suspend a Power BI Dedicated capacity to save money?

Yes. POST .../capacities/{dedicatedCapacityName}/suspend stops billing for capacity hours, and the matching /resume endpoint brings it back online. Both are long-running operations so the response should be polled until provisioningState reaches Succeeded.

What are the rate limits for the Power BI Dedicated API?

Azure Resource Manager applies subscription-level read and write throttles (around 12,000 reads per hour and 1,200 writes per hour per region per subscription) and returns 429 with a Retry-After header when exceeded. Provisioning, suspend, and resume are asynchronous and should be polled with backoff.

How do I scale a Power BI Dedicated capacity through Jentic?

Search Jentic for 'scale power bi dedicated capacity', load the schema for PATCH .../capacities/{dedicatedCapacityName}, then execute with the new sku.name in the request body. The pip install jentic Python SDK uses the async search, load, execute pattern.

Is the Power BI Dedicated API free?

There is no per-call charge for the management API itself; you pay for the Power BI Dedicated capacity hours of the SKU you select. Suspended capacities do not accrue capacity-hour charges, which is why suspend and resume are first-class operations on this API.