Microsoft Azure Power BI Embedded Management Client
Browse all Azure APIs43
AI ReadinessFoundational (D-)43/100
Agent-ready OpenAPI document · curated by JenticCloud InfrastructureComputeoauth212 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Provision and manage Power BI Embedded workspace collections in Azure, rotate their access keys, and list the workspaces hosted inside each collection.
Use for: Provision a new Power BI Embedded workspace collection, Retrieve the access keys for an embedded Power BI workspace collection, Rotate the primary access key on a Power BI Embedded workspace collection, List all Power BI Embedded workspace collections in a subscription
Not supported: Does not author Power BI reports, mint embed tokens, or query datasets - use for the Microsoft.PowerBI workspace collection resource lifecycle and access-key management only.
Jentic publishes the only available OpenAPI specification for Power BI Embedded Management Client, keeping it validated and agent-ready. The API manages Microsoft.PowerBI workspace collections in Azure Resource Manager, covering provisioning, listing, updates, deletes, and access-key rotation for the dedicated capacity that hosts embedded Power BI dashboards. It also includes name availability checks and a workspace listing endpoint used to surface workspaces inside a collection.
Install Jentic One Beta
Connect the Power BI Embedded Management Client to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Power BI Embedded Management Client, 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.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Fpower-bi-embedded-management-client" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Fpower-bi-embedded-management-client" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 Power BI Embedded Management Client API.
Provision a Power BI Embedded workspace collection in a resource group
List workspace collections at subscription or resource-group scope
Rotate or retrieve the access keys used to embed Power BI content
Migrate workspace collections between resource groups
Check whether a workspace collection name is available before provisioning
List the workspaces hosted inside a given collection
Use Cases
Patterns agents use Power BI Embedded Management Client API for, with concrete tasks.
★ Embedded analytics provisioning
A SaaS team that embeds Power BI dashboards into its product needs a per-tenant workspace collection in Azure. The API provisions the collection in the chosen resource group, returns the access keys needed to mint embed tokens, and lists the workspaces inside the collection so the application can route reports to the right tenant.
Create a Power BI Embedded workspace collection named 'tenant-acme-prod' in resource group 'analytics-rg' in West Europe, then return its access keys
Access key rotation
Embedded Power BI tokens are signed with workspace collection access keys, so rotating those keys is a regular security task. The API regenerates a chosen key and exposes both keys so the rotation can be staged across the embedding application without downtime.
Regenerate the secondary access key for workspace collection 'tenant-acme-prod' and return the new key value
Tenant cleanup and migration
When a tenant is offboarded or moved between business units, the workspace collection needs to be migrated to a new resource group or deleted. The API lists collections by subscription, supports a moveResources call for migration, and deletes idle collections so capacity is not left running.
List all workspace collections in subscription X, identify any tagged 'lifecycle=eol', and delete each one
Agent-driven embed onboarding
An AI agent fronting an internal portal accepts a tenant onboarding request, checks the proposed workspace collection name, provisions the collection in the right region, fetches the access keys, and stores them in the tenant config. Jentic isolates the Azure AD client secret so the agent only ever sees scoped bearer tokens.
Onboard a new embedded analytics tenant: validate the desired collection name, provision in West Europe, return access keys for the application config
Key Endpoints
12 endpoints — jentic publishes the only available openapi specification for power bi embedded management client, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.PowerBI/workspaceCollections/{workspaceCollectionName}
Create or update a workspace collection
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.PowerBI/workspaceCollections/{workspaceCollectionName}
Get a specific workspace collection
DELETE
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.PowerBI/workspaceCollections/{workspaceCollectionName}
Delete a workspace collection
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.PowerBI/workspaceCollections/{workspaceCollectionName}/listKeys
List access keys for a workspace collection
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.PowerBI/workspaceCollections/{workspaceCollectionName}/regenerateKey
Regenerate an access key
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.PowerBI/workspaceCollections/{workspaceCollectionName}/workspaces
List workspaces inside a collection
POST
/subscriptions/{subscriptionId}/providers/Microsoft.PowerBI/locations/{location}/checkNameAvailability
Check workspace collection name availability
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.PowerBI/workspaceCollections/{workspaceCollectionName}
Create or update a workspace collection
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.PowerBI/workspaceCollections/{workspaceCollectionName}
Get a specific workspace collection
DELETE
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.PowerBI/workspaceCollections/{workspaceCollectionName}
Delete a workspace collection
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.PowerBI/workspaceCollections/{workspaceCollectionName}/listKeys
List access keys for a workspace collection
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.PowerBI/workspaceCollections/{workspaceCollectionName}/regenerateKey
Regenerate an access key
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.PowerBI/workspaceCollections/{workspaceCollectionName}/workspaces
List workspaces inside a collection
POST
/subscriptions/{subscriptionId}/providers/Microsoft.PowerBI/locations/{location}/checkNameAvailability
Check workspace collection name availability
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
P
Power BI Embedded Management Client
- Foundational (D-)43/100
90
Foundational Compliance63
Developer Experience & Jentic Compatibility17
AI-Readiness & Agent Experience94
Agent Usability100
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
90
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: ASignals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
60%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
17
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
58%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
8%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
0%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
100
Security
Trust, risk posture, and security compliance.
Grade: A+Signals: 1
100%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Power BI Embedded Management Client by hand means registering an Azure AD app for OAuth 2.0, minting bearer tokens against management.azure.com, and polling the asynchronous provisioning of workspace collections yourself. Through Jentic you install once, import the Power BI Embedded Management Client from the API Directory, store the Azure AD credential once, and your agent calls it.
Permission scoping
The subscription, resource group, and workspace collection name all travel in the URL path (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.PowerBI/workspaceCollections/{workspaceCollectionName}), so a rule can pin your agent to one collection and the operations it needs, such as listing keys and provisioning. You choose the operations it may call, so destructive ones like deleting a collection or regenerating an access key are not included unless you add them.
Credential isolation
Your Azure AD OAuth 2.0 credential is stored once, encrypted, by your own Jentic One instance and a scoped bearer token is injected at execution time. The client secret never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'provision a power bi embedded workspace collection' or 'rotate the access keys for an embedded collection', and Jentic returns the matching operation with its input schema so the agent supplies subscription, resource group, location, and SKU without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Power BI Embedded Management Client API through Jentic.
Why is there no official OpenAPI spec for Power BI Embedded Management Client?
Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Power BI Embedded Management Client 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 Power BI Embedded Management 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 rotate the access keys for an embedded workspace collection?
Yes. POST /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.PowerBI/workspaceCollections/{workspaceCollectionName}/regenerateKey regenerates the chosen primary or secondary key, and the listKeys POST endpoint returns the current pair so rotation can be staged across the embedding application.
What are the rate limits for the Power BI Embedded Management 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 is asynchronous and should be polled with backoff.
How do I provision an embedded workspace collection through Jentic?
Search Jentic for 'provision power bi embedded workspace collection', load the schema for PUT .../workspaceCollections/{workspaceCollectionName}, then execute with subscriptionId, resourceGroupName, location, and SKU. The pip install jentic Python SDK uses the async search, load, execute pattern.
Is the Power BI Embedded Management API free?
There is no per-call charge for the management API itself; you pay for the Power BI Embedded capacity SKU you select on the workspace collection resource. Reads against the management plane are not separately metered.
Can I limit what my agent is allowed to do with the Power BI Embedded Management API?
Yes. Because Jentic One is self-hosted, you write the rules that decide which operations and credentials the agent may use, and the subscription, resource group, and workspace collection name all travel in the URL path, so you can pin the agent to a single collection and only the calls it needs. You choose the exact operations it can invoke, such as provisioning a collection or listing access keys, while leaving destructive ones like deleting a collection or regenerating a key out unless you explicitly add them. The Azure AD credential is stored once by your own instance and a scoped bearer token is supplied at execution time, so the agent never handles the raw secret.
GET STARTED