Microsoft Planner has no native connector to Power BI — Microsoft’s own Q&A says so plainly, and no amount of searching Power BI Desktop’s data source list turns one up. What exists instead are two separate, Microsoft-sanctioned paths that each cover half the problem: a Power Automate pipeline you build and maintain for Basic plans, or a free Dataverse template that only sees Premium (Project for the web) plans. Neither gets you “all my plans in one Power BI report” without extra engineering. Here’s exactly what each path requires, why they don’t overlap, and what a dedicated cross-plan tool gets you instead — without pretending it’s a Power BI feature.

Does Microsoft Planner connect to Power BI at all?

No, and this isn’t a case of the feature being buried somewhere. A Microsoft Q&A dated 2025-07-15, asking exactly this, got an accepted answer that doesn’t hedge: “Currently, Microsoft Planner does not offer a direct connector to Power BI.” (Microsoft Q&A) Open Power BI Desktop’s “Get data” list and Planner isn’t on it, Basic or Premium. People have been asking for this since at least 2018 — a Microsoft Community Hub thread titled “How to automate Planner and integrate it with Power BI” ran from January 2018 to October 2023, 18 replies deep, with a Microsoft MVP confirming in the thread that Planner simply “does not provide” the kind of direct linking people keep asking for. Five-plus years on, the answer hasn’t changed.

What does the Power Automate route to Power BI actually require?

A flow you build and keep running, not a setting you flip. The pattern people land on, per that same Community Hub thread: a Power Automate flow calls Planner’s “List tasks” action on a schedule, writes the results to an Excel file or SharePoint list, and Power BI reads that file. It works, and it’s entirely native Microsoft tooling — but every piece of it is yours to build: the flow, the schedule, the destination table, and the fix whenever Planner changes a field underneath you. It also only sees Basic plan data; Premium plans live outside Planner’s Graph API entirely, so this pipeline never touches them.

What about the “Premium” route — the Dataverse template?

This is the other half, and it’s easy to mistake for a general Planner-to-Power-BI answer when it’s actually scoped tight. Planner Premium plans (the ones built on Project for the web) store their data in Dataverse, not Planner’s own store, and Microsoft publishes a free Power BI template that connects straight to that Dataverse instance — download it, open it in Power BI Desktop, enter your Dataverse and Project Web App URLs, sign in (Microsoft Support). Per a walkthrough of using it on current Planner Premium plans, it ships nine built-in reports across portfolio, resource, and task-level views (MPUG). The catch is right there in what it connects to: Dataverse only has Premium plans in it. A Basic plan is invisible to this template, full stop.

So: Power Automate sees Basic, misses Premium. The Dataverse template sees Premium, misses Basic. If your organization runs both tiers — and most do, since Premium is a per-plan upgrade, not an all-or-nothing switch — neither route alone gets you a complete picture, and nothing stitches the two together for you.

Why doesn’t either route scale to “all my plans”?

Because both were built around one plan (or a few), not a portfolio. The Power Automate route needs its own flow per plan or a loop that iterates over plans, and that falls over as the plan count grows. On the Microsoft Fabric Community, someone trying to consolidate 200+ Planner apps into a single Power BI dataset asked exactly this, and the answer they got wasn’t “here’s the setting” — it was to build a custom connector against the Microsoft Graph “List plans” endpoint and pull each plan’s tasks through it themselves (Microsoft Fabric Community). That’s a real, workable answer — and also confirmation that nothing off-the-shelf does this once you’re past a handful of plans.

Comparing the actual paths

PathWhat it requiresWhat it coversThe catch
Power Automate → Excel/SharePoint → Power BIA flow you build and schedule yourself, one per plan or looped over plansBasic (non-Premium) plansNo native way to merge many plans; breaks down past a handful
Custom Microsoft Graph API connectorAn app registration, calling List plans / List tasks yourself, your own Power Query or codeWhatever you build it to cover — Basic, and Premium if you add that path tooA real development project, not a toggle — you own paging, refresh, and schema drift
Power BI template for Planner Premium (Dataverse)A Planner and Project Plan 3+ license, a Dataverse connection in Power BI DesktopPremium (Project for the web) plans onlyFree Microsoft template, last substantively updated 2022, blind to Basic plans entirely

Is the Planner Power BI template still maintained?

It’s live, not pulled, but it hasn’t moved in a while. The GitHub repository behind the template Microsoft Support links to, OfficeDev/Project-Power-BI-Templates, is unarchived and still the one official documentation points at — but its commit history shows the last substantive work landing in late 2022. It was built for the old “Project for the web” branding and carried forward into Planner Premium reporting as-is, rather than rebuilt around the newer Planner surface. Treat it as a working legacy template, not an actively developed product.

Can I just build a custom Power BI connector myself?

Yes, and for a BI team with the time, it’s the only route that actually covers both plan tiers in one place — because you decide what it covers. The pattern (per the Fabric Community thread above) is a Microsoft Graph connector hitting List plans and List tasks, with your own code or Power Query resolving plan names, buckets, and assignees into something Power BI can model. Add a second path against Dataverse for Premium plans, and you’ve rebuilt both Microsoft’s own templates yourself, merged into one dataset. It’s a legitimate answer. It’s also a multi-week engineering project with ongoing maintenance, not a report you open this afternoon.

What if I just want cross-plan reporting, not a Power BI project?

This is the honest fork in the road: if what you actually need is a Power BI report specifically — because it feeds a larger BI estate, or other dashboards already live there — one of the three paths above is the real answer, and there’s no shortcut around the engineering. But if what you need is to see your Planner work broken down by status, priority, bucket, and who’s carrying what, across every plan, without building or maintaining a pipeline, that’s a narrower ask that doesn’t require Power BI at all.

Team Workload is built for that narrower case — and it’s worth being precise about what it is and isn’t. It does not export to Power BI, connect to it, or publish an OData feed; if a Power BI report is specifically what you need downstream, this isn’t that. What it does instead is give you the destination people usually reach for Power BI to get to: a Dashboard that charts status, priority, bucket, and assignee across every plan you can access — the same vocabulary as Planner’s own single-plan Charts page, just run across your whole portfolio — and a Trends view that charts open-tasks-over-time (burndown) and completions-per-week (velocity) from a daily snapshot history, with no flow to wire and no Dataverse connection to set up. It reads both Basic and Premium plans through one Microsoft sign-in.

One honest limit carries over from the Premium side either way: Premium (Project for the web) tasks don’t carry a completion timestamp the way Basic tasks do, so Premium work undercounts in the burndown and velocity charts even though it shows correctly as complete in the Dashboard’s live counts. If your plans are entirely or mostly Premium, that’s worth knowing before you lean on the trend lines specifically.

If the dashboard-style breakdown is the whole ask, see Planner dashboard across all plans for exactly what that view covers and where it stops. If it’s the historical/trend angle you’re after, Planner burndown chart and task history covers what’s reconstructible from Planner’s own data and what isn’t, Power BI or otherwise.