Project Online retires September 30, 2026, and it’s taking its Power BI content pack and OData feed with it — Microsoft has no automated path that carries either one into Planner Premium. Planner Premium (Project for the web) stores its data in Microsoft Dataverse instead, with no built-in content pack, so the dashboard that used to come free now needs manual setup or a vendor’s report pack. Here’s what Microsoft’s own support staff say happens to that reporting pipeline, what actually works today, and where Team Workload fits — and the real limits on where it doesn’t.

What did Project Online’s reporting actually give you?

A ready answer, not a build project. Asked in November 2025 whether Planner Premium can connect to Power BI “the way Project Online did,” a Microsoft moderator’s answer spells out what Project Online offered that Planner Premium doesn’t: a “built-in Power BI content pack and OData feed for quick dashboard creation” (Microsoft Q&A). Point a Power BI content pack at Project Online and you got a working set of reports out of the box — no data model to design, no connector to configure.

Does Planner Premium support Power BI the same way?

Not the same way. The same Microsoft moderator is direct about the difference: Planner Premium “does support Power BI reporting, but it works differently compared to Project Online.” The reason is architectural — “Planner Premium stores its data in Microsoft Dataverse, so you can connect to Power BI using the Dataverse connector” — but “unlike Project Online, Planner Premium does not include a built-in content pack; you’ll need to configure the connection and apply Power BI templates manually” (Microsoft Q&A 5619017). Reporting is possible. It’s no longer something that ships finished.

Why can’t Power Automate or the standard Planner connector just read Premium data?

Because Premium plans sit outside Microsoft Graph entirely. A Community Hub thread from March 2026, asking how to retrieve Planner Premium fields in Power BI and Power Automate, got this answer: “Planner Premium data is not available via Graph API since it lives in Dataverse. This has been the case for past ~2 years and Microsoft hasn’t yet delivered any readymade Planner connector to overcome this issue” (Microsoft Community Hub).

It’s the same wall for automation. An August 2024 thread asking about Planner Premium and Power Automate ran to 14 replies before landing on a workaround from a Microsoft MVP: skip Planner’s own connector and call the Project Schedule APIs documented under Dynamics 365 Project Operations instead, “because ultimately Planner Premium uses the same scheduling engine as MS Project” (Microsoft Community Hub). That the same gap is still being asked about a year and a half later, in a different thread, with the same root cause, is the pattern worth noticing — this isn’t a bug that’s getting fixed, it’s a standing architecture decision.

What happens to the OData feed when Project Online retires?

Nothing carries it over. Project Online retires on September 30, 2026. Microsoft’s own retirement post lays out where to move — Planner Premium, Project Server Subscription Edition, Dynamics 365 Project Operations — without once mentioning what happens to an org’s existing OData feed or Power BI content pack (Microsoft Community Hub). A separate Q&A asking plainly “what is the replacement for Microsoft Project Online?” gets the same silence on this specific point — Microsoft’s moderator confirms there’s no “single one-to-one replacement that includes all Project Online features in the same way,” listing the same three destinations, and never addresses reporting continuity at all (Microsoft Q&A). Whatever dashboards, exports, or scheduled refreshes you built on that OData feed, you are rebuilding them from scratch on whichever destination you land on — not migrating them.

What are the realistic options for reporting today?

What you wantNative pathReal cost
A Power BI dashboard on Premium plansDataverse connector, manual templateYour own build time, or Microsoft’s free community template built for Project for the web on GitHub
Premium fields in a Power Automate flowNo standard Planner connector reaches themProject Schedule APIs under Dynamics 365 Project Operations
A finished dashboard without building oneNone from MicrosoftA paid third-party Power BI report pack
One person’s task list across Basic + Premium plans togetherNo native viewA tool that reads both tiers directly — see below

The first three rows are all variations on “rebuild the reporting pipeline yourself, with Dataverse instead of OData as the data source.” None of them is Project Online’s old plug-and-play content pack.

Does Team Workload replace Project Online’s reporting?

No, and it’s worth being exact about where the line sits. Team Workload reads Premium plans straight out of Dataverse — task title, start and due dates, percent complete, priority, bucket, and who’s assigned — and shows them next to your Basic plans in the same cross-plan task and people view. That’s genuinely useful if your question is “what is this person carrying across everything, Basic and Premium both,” which Planner itself can’t answer across plans.

It is not a Power BI replacement. There’s no path to Premium custom fields, dependencies, effort, baselines, or timesheets, and nothing here touches Project Online history or migration — those stay problems for Dataverse-direct Power BI or Project Server Subscription Edition to solve. If your reporting need is a BI dashboard with custom fields and baselines, this page’s table above is your actual answer. If it’s a day-to-day view of what one teammate is holding across plan types, that’s the specific gap this closes.

Getting Premium plans in is a one-time Connect step — sign in with a Microsoft work account, consent once, and Team Workload auto-discovers your Dataverse environment from there, no Power Automate flow to build or maintain. It isn’t a live sync, either: Premium data refreshes on load, on a schedule, or when you trigger it manually, the same as Basic plans.

A different question, answered elsewhere

This page is about the Project Online reporting pipeline specifically — the OData feed and content pack, and what replaces them. Two related questions get asked in the same breath and deserve their own answer:

Both of those stay unresolved even after you’ve sorted out reporting. This one — what replaces the OData feed and content pack you lost — is the one that hits first, the moment Project Online actually goes away.