powerbi-report-management

Manage Power BI report items and PBIR definitions in Microsoft Fabric via the REST API.

Updated Aug 19, 2026
One-click install
npx skills add https://github.com/paulasilvatech/Fabric-Agentic-SDLC --skill powerbi-report-management-paulasilvatech
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: powerbi-report-management
Source: https://github.com/paulasilvatech/Fabric-Agentic-SDLC/tree/main/.github/skills/powerbi-authoring/skills/powerbi-report-management
Command: npx skills add https://github.com/paulasilvatech/Fabric-Agentic-SDLC --skill powerbi-report-management-paulasilvatech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Publishing, downloading, updating, and deleting Power BI reports in Microsoft Fabric workspaces requires many low-level REST API calls with base64-encoded PBIR payloads, long-running operation polling, and strict format rules. This Skill provides tested az rest workflows for the full report CRUD lifecycle so you avoid auth failures, duplicate creates, and corrupted definitions. ## Core Features & Use Cases - Report CRUD via Fabric REST API: List, get, create, update, and delete report items in a workspace using az rest with the correct audience, scopes, and JMESPath filtering. - PBIR definition transport: Download report definitions with getDefinition?format=PBIR, decode base64 parts to local files, and re-encode full part sets for create or updateDefinition uploads. - Local .pbip publishing workflow: Guided flow to publish a local Power BI Project, including semantic model resolution, byPath to byConnection rebinding, binding verification against the target model's TMDL, and LRO polling. - Use Case: You have a local SalesDashboard.pbip project and want it live in a Fabric workspace. The Skill resolves the workspace, binds the report to the correct semantic model, uploads all PBIR parts, polls the operation to completion, and cleans up temp files. ## Quick Start Ask the AI to publish your local .pbip report to a named Fabric workspace, or to download an existing report's PBIR definition from a workspace for local editing.

Frequently Asked Questions about powerbi-report-management

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I publish a Power BI report to Microsoft Fabric with the REST API?▼

Create the report by POSTing to /v1/workspaces/{workspaceId}/reports with a definition containing all PBIR files base64-encoded as InlineBase64 parts. The definition.pbir must use a byConnection reference to a semantic model ID, and you must poll the long-running operation to completion.

How to download a Power BI report definition from a Fabric workspace?▼

Send a POST to the report's getDefinition endpoint with ?format=PBIR using az rest. The call often returns 202 Accepted, so capture the x-ms-operation-id header with --verbose and poll the operation, then base64-decode each returned part to local files.

Does the Fabric API support PBIR-Legacy report definitions?▼

This workflow only supports the modern PBIR format. Always pass ?format=PBIR on getDefinition, and if the response shows format PBIR-Legacy, the report cannot be downloaded or updated through this path.

Why do duplicate reports appear after creating a report in Fabric?▼

Duplicates happen when the create POST is retried after receiving a 202 Accepted response, since the operation is already processing server-side. Instead, capture the x-ms-operation-id from verbose output written to a file and poll that operation to completion.

Why are visuals empty after publishing a report to Fabric?▼

Empty visuals usually mean PBIR entity bindings do not match the target semantic model's table and column names, or definition.pbir points to a stale model ID. Download the model's TMDL, compare Entity and queryRef references, remap mismatches, and rebind byConnection to the resolved semanticModelId.

What permissions are needed to update a Power BI report definition in Fabric?▼

Updating a definition requires read and write permissions on the report, typically a Contributor workspace role, plus the Report.ReadWrite.All or Item.ReadWrite.All scope. The updateDefinition call replaces the entire definition, so all parts must be included.