Forum Discussion

Yash8160's avatar
Yash8160
Icon for Advocate II rankAdvocate II
1 month ago
Solved

Claude Code Integrate with Power Bi

Hi everyone, I’m working on a POC for Power BI + Claude Integration, specifically the Report Authoring skill.We need to use Claude Code to create the required report pages and visuals. I’m currently...
data engineering
  • v-achippa's avatar
    v-achippa
    1 month ago

    Hi Yash8160​,

    Thank you for reaching out to Microsoft Fabric Community.

    For this POC, you can integrate Claude code with power bi using Microsoft’s Power BI Authoring skill for Fabric. This allows Claude code to work with power bi report and semantic model artifacts.

    There is no fixed number of Claude code credits or tokens per power bi report or page. The consumption depends on the Claude model used and the complexity of the authoring task. So, build one representative report page, record its token usage, and use it as a baseline to estimate the remaining POC, including some allowance for testing and rework

    For reference, follow the below documentation:
    Skills for Fabric

    Install Skills for Fabric

    Thanks and regards,
    Anjan Kumar Chippa

jubinsoni's avatar
jubinsoni
Icon for Memorable Member rankMemorable Member
1 month ago

Hi Yash8160​ ,

Agree with the others that measuring one real page is the way to go. Just wanted to add, if you're on API billing, running /cost in Claude Code at the end of a session shows the tokens and cost for that session, which makes the baseline easy to capture.

From doing similar work, a few things keep usage down a lot. The biggest token sink is Claude rereading large TMDL and PBIR files every session, so put a short CLAUDE.md in the project root with a summary of your key tables, measures and naming conventions. Then it can skip most of the exploring. Point it at the specific page folder you're working on rather than the whole project, and start a fresh session with /clear between pages so old context doesn't pile up.

Also worth using a mid-size model for the routine visual JSON work and only switching to a larger one for planning or tricky DAX. That alone can make a big difference on cost.