Quick answer: Microsoft project portfolio management meant Project Server and then Project Online for the better part of two decades. Project Online retires on 30 September 2026. Planner Premium inherited the scheduling capability, but enterprise resource management, project financials, benefits tracking, portfolio analysis and risk registers did not carry across at all. Organizations are closing that gap three ways: rebuilding on the Power Platform inside their own tenant, adding a portfolio layer above Microsoft 365, or accepting manual consolidation while the portfolio stays small.
The question people are really asking when they search this phrase is not what it means. It is what happened to the thing they had.
What the term used to mean
Microsoft project portfolio management had a precise definition. Project Server, later Project Online, running on SharePoint, with Project Professional on the desktop and a reporting layer over the top. It was a complete PPM product: enterprise resource pools, portfolio analyses, demand management, timesheets, custom fields and workflows.
Organizations built PMOs around it. Governance processes were designed to fit its gate model. That history matters, because it sets the expectation people bring to whatever comes next.
What retired, and when
The consolidation ran over roughly two years and was announced in stages.
In May 2025, Project for the web was retired as a named product and folded into Microsoft Planner. What had been Project for the web became Planner Premium — a rename and a consolidation rather than a shutdown, with the capability continuing under a different name inside a different app.
In September 2025, Microsoft announced the retirement of Project Online, effective 30 September 2026, citing its legacy architecture and its inability to support Copilot. Twelve months of notice, with migration guidance published.
Alongside this, Viva Goals — which a number of PMOs had adopted for objectives — stopped receiving new features in December 2024 and was retired on 31 December 2025.
The direction is coherent and was communicated: fewer products, one work management surface in Planner, Copilot across it. Nobody was ambushed. But the practical effect for a PMO is that the product they ran portfolio management on no longer exists, and the thing it consolidated into is a different shape.
What Planner Premium covers
Planner Premium is the successor in the sense that it inherited Project for the web's capability, and it is a capable scheduling product. Dependencies, a timeline view, goals, baselines, sprints and workload views. It also adds Portfolios, which roll several Premium plans into one view.
For a team running a project, this is a genuine step up from Planner Basic and a reasonable landing place for a lot of the work that used to sit in Project Online.
Two boundaries are worth being precise about, because they determine whether it closes your gap. Microsoft documents that Portfolios do not cover Basic plans, and creating or editing a Portfolio requires a Plan 3 or Plan 5 licence. And a Portfolio is a roll-up of plans — which is to say, a roll-up of tasks.
What did not come across
This is the part that surprises people who assumed the successor would be a superset.
- Enterprise resource management. Project Online had a resource pool, resource engagements and capacity against availability. Planner has assignments and a workload view, which answers who is doing what, not who has time.
- Project financials. Cost, forecast, budget and benefit tracking were part of the old model. They are not in Planner in either edition.
- Portfolio analysis. Project Online could score, constrain and optimize a portfolio against a budget. Portfolios roll plans into a view; they do not model funding decisions.
- Risk and issue registers. Standard in the old product, absent in the new one.
- Demand management and gated intake. Workflow-driven intake was a core Project Online capability with no direct successor.
None of this is a criticism of Planner, which was not built to do these things and does not claim to. It is simply the shape of the gap: the new product is stronger at running the work and does not attempt the layer above it.
How organizations are closing the gap in 2026
Three patterns, and the right one depends on constraints rather than preference.
Rebuild it on the Power Platform
Microsoft publishes an open-source Project Accelerator built on Dataverse, and a category of partner products sits on the same foundation. Everything runs inside your own tenant, which satisfies data residency requirements absolutely and gives unlimited extensibility.
What you take on is ownership: the environment, the solution layers, the release testing, and the response when something underneath changes. That is a permanent internal responsibility rather than a project with an end date. For organizations with an established Power Platform practice this is a natural fit; for those without one it is a larger commitment than it first appears. Our guide to the Power Platform PPM landscape covers who builds in this category.
Add a Portfolio Management layer above Microsoft 365
Keep Planner as the place work happens and put the portfolio layer somewhere else. The plans stay where they are; portfolios, programs, capacity, financials, benefits, risk and reporting sit above them and read from them.
This is the closest structural match to what Project Online actually did, because Project Online was also a layer above the work rather than the work itself. The difference is that the layer is now separate from the tool, which turns out to matter in mixed estates — and most enterprises have mixed estates.
Do nothing above the plans
A legitimate answer for some organizations. If your portfolio is small enough that the roll-up fits in a spreadsheet and the questions you get asked are about progress rather than investment, native Planner plus a manual monthly consolidation may genuinely be sufficient. It stops being sufficient at the point where somebody starts asking about capacity or benefits.
The question the old product answered
It is worth being clear about what portfolio management is for, because the tooling conversation obscures it.
Project portfolio management exists to answer four questions that no individual project can answer. Are we doing the right things? Can we actually deliver what we have committed to, with the people we have? Is the money producing the value it was approved for? And what is going to stop us?
Task tools — including excellent ones — answer none of these, because the data required is not task data. It is capacity against availability, cost against forecast, benefit against baseline, and risk against mitigation.
Whatever route you take out of Project Online, the test is whether the destination holds that data. If it does not, you have replaced the scheduling and lost the portfolio.
Where AI changes the calculation
There is a reason to resolve this sooner rather than later, and it is not the retirement date.
AI in project management is genuinely useful now, and it is useful in proportion to the data it can reach. Copilot inside a plan will summarize that plan well. Ask it which initiatives are at risk this quarter, or whether the roadmap fits the capacity, and it cannot answer — not because the model is weak but because the data has never been in Planner.
Every month a portfolio runs on spreadsheets and manual consolidation is a month of decisions, changes and outcomes that never becomes queryable. Organizations that get their portfolio data into a structured layer are accumulating something the ones on spreadsheets are not.
What PPM Express Enterprise does here
PPM Express Enterprise is the portfolio layer for organizations that want to keep working in Microsoft 365.
It connects Planner plans — Basic and Premium, including plans created inside Teams — and holds everything above them: portfolios and programs, resource capacity and utilization, budgets, forecasts and benefits, risks and issues, prioritization and funding scenarios, and reporting your executives open themselves. The integration reads your plans and never writes back, so Planner remains the source of truth for the work.
For organizations coming off Project Online, two things usually matter most. The capability that did not survive the consolidation — capacity, financials, benefits, risk, portfolio analysis — is present. And Planner is not the only thing that connects: Jira, Azure DevOps, Microsoft Project, Smartsheet and monday.com feed the same portfolio, which matters because delivery is rarely all in one tool. An automated Project Online migration path is included for teams still moving.
AI works at portfolio level, where the questions are. Status summaries are generated from live delivery data when you ask for them or when a project syncs. AI agents monitor the portfolio and propose rather than execute. Copilot integration for PPM Express Enterprise is in development, so portfolio questions can be asked from where your organization already works.
Frequently asked questions
When does Microsoft Project Online retire? 30 September 2026. Microsoft announced the retirement in September 2025, citing the product's legacy architecture and its inability to support Copilot, and published migration guidance alongside the announcement.
What replaced Project Online for portfolio management? Nothing replaced it as a single product. Planner Premium inherited the scheduling capability that had been Project for the web, but enterprise resource management, project financials, benefits tracking, portfolio analysis and risk registers have no direct successor in the native Microsoft stack.
Is Microsoft Planner Premium a replacement for Project Online? For scheduling and task management, largely yes. For portfolio management, no — Planner Premium holds no capacity against availability, no project financials, no benefits data and no risk register, and its Portfolios feature aggregates tasks rather than modelling funding decisions.
What does Microsoft project portfolio management mean in 2026? It describes an approach rather than a product. Organizations either run native Planner and accept its ceiling, build a portfolio solution on the Power Platform inside their own tenant, or add a hosted portfolio layer that reads their Microsoft data.
Do we have to migrate off Project Online before September 2026? The service retires on that date, so any organization still running portfolio management on it needs a destination. What matters more than speed is whether the destination holds the capacity, financial, benefits and risk data the old product held — replacing only the scheduling leaves the portfolio behind.
The short version
Project Online was a layer above the work, and Planner Premium is the work. That is the whole difference, and it explains why the migration feels harder than a rename. Scheduling carried across. Capacity, cost, benefits, risk and portfolio analysis did not. Whichever route you take — Power Platform build, hosted portfolio layer, or manual consolidation while the portfolio stays small — judge it on whether it holds the four things Planner does not, rather than on how closely the interface resembles what you had.
If you are working out where a Project Online portfolio should land, the part worth checking first is whether the destination holds capacity, financials, benefits and risk — not whether the schedules import cleanly. PPM Express was built as that layer, and reads Planner alongside Jira, Azure DevOps and Microsoft Project into one portfolio. Happy to walk through what that looks like against your current setup.
.svg){kind=small}
