Microsoft PPM in 2026: Every Portfolio Option in the Microsoft Stack

Quick answer: Microsoft PPM used to mean one thing — Project Server, then Project Online, with Project Professional on the desktop. That product line has been consolidated away, and in 2026 there is no single Microsoft PPM product to point at. There are four routes: use Microsoft Planner natively, build on the Power Platform, buy a Power Platform product that deploys into your own tenant, or add a hosted portfolio layer above Microsoft 365. Which one fits comes down to four questions about data residency, ownership, delivery tooling and time to value — not to a feature comparison.

If you last evaluated Microsoft PPM before 2024, everything you concluded is out of date. That is worth saying plainly before anything else.

The term changed underneath everyone

For most of two decades, Microsoft PPM had a precise meaning. Project Server, later Project Online, running on SharePoint, with Project Professional on the desktop and a reporting layer over the top. Enterprise resource pools, portfolio analyses, demand management, timesheets, custom fields and workflows. Organizations built PMOs around it and people spent careers becoming expert in it.

That answer has been dismantled in under two years, in stages, all of them announced.

Project for the web was retired in May 2025 and folded into Microsoft Planner as Planner Premium — a rename and a consolidation rather than a shutdown. In September 2025, Microsoft announced the retirement of Project Online effective 30 September 2026, citing its legacy architecture and its inability to support Copilot. 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.

Read together, the direction is coherent: fewer products, one work management surface, Copilot across it. Twelve months of notice on Project Online, with migration guidance published. 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.

So this article does not argue for an answer. It lays out the four routes that exist in 2026 and the questions that put you on one of them.

Route 1: Native Microsoft 365

Microsoft Planner is now the work management surface for the whole ecosystem, in two editions. Basic is included with Microsoft 365 and handles plans, buckets, tasks, assignments and a Charts view per plan. Premium adds real scheduling — dependencies, a timeline, goals, baselines and workload views — along with Portfolios, which roll several plans into one view.

Portfolios are the closest native answer to portfolio management and they are genuinely useful. Two limits shape where they fit: Microsoft documents that Portfolios do not cover Basic plans, and creating or editing one requires a Plan 3 or Plan 5 licence, so everyone who needs to work in the roll-up needs that licence.

The deeper limit is not licensing. A portfolio view of tasks is still a view of tasks. Neither edition holds resource capacity, project budgets, forecasts, benefits, or a risk and issue register — the things a steering committee asks about, which are not in the product to be reported on.

This route is right when your portfolio is modest, delivery is entirely inside Planner, and the questions you need to answer are about progress rather than investment.

Route 2: Build it yourself on the Power Platform

Microsoft publishes an open-source Project Accelerator — an MIT-licensed solution you deploy into your own Power Platform environment, built on Dataverse. It gives you a project and portfolio data model out of the box and you own everything from there.

It is a genuine option and a good starting point if you have the Dataverse environment, the administrative access and someone who will own it. Two things to weigh. Its terminology follows the legacy Project for the web model, which is now behind the product line. And an accelerator is a starting point by design — the deployment, every divergence you make from the template, and all subsequent maintenance are yours.

This route is right when your process is unusual enough that no product will fit, and you have the people to build and maintain the difference permanently rather than for the length of a project.

Route 3: Buy a Power Platform product

A substantial category of PPM products is built on Dataverse and deployed into your own Microsoft tenant. BrightWork 365, Sensei IQ, Projectum's Power PPM and xPM, Power Framework, pmo365, Altus, TPG's ProjectPowerPack and edison365 all sit here, alongside partner accelerators such as Wellingtone's Accelerator+.

The shared advantage is real and it is why the category exists: your portfolio data never leaves your tenant. You inherit Microsoft's security posture and identity model, and the compliance review that stalls a SaaS purchase for six weeks tends to take an afternoon. You also get extensibility — if your gate process has a step no product anticipated, someone can build it.

The shared consideration is ownership. These are solutions deployed into your environment, so the environment, the solution layers, the release testing and the response when something underneath changes all become internal responsibilities after go-live. Establishing early whether you are buying a versioned product or a configured solution matters more than any feature comparison, because it determines what happens at the next release.

This route is right when tenant data residency is a hard requirement, or when you already run the Power Platform at scale and have the capability to own another solution on it.

Route 4: Add a portfolio layer above Microsoft 365

The fourth route separates the portfolio layer from the tools the work sits in. Teams keep working in Planner. A hosted platform reads their plans and holds everything above them: portfolios and programs, resource capacity, budgets and benefits, risks and issues, prioritization and reporting.

Nothing is deployed into your tenant and nothing is installed in Planner. The people doing the work never open the portfolio tool — accounts are for the PMO, sponsors, finance and leadership. The trade-off is the mirror image of route 3: portfolio data is hosted by the vendor rather than sitting in your own environment. If tenant residency is non-negotiable, this route is not for you, and no feature comparison changes that.

The distinguishing advantage shows up in mixed estates. Most enterprises do not deliver everything in one tool — Planner in the business, Jira or Azure DevOps in engineering, Microsoft Project on a construction program, Smartsheet somewhere in operations. A portfolio layer that reads all of them produces one portfolio without asking any team to migrate.

Where AI actually reaches today

Every route now comes with an AI story, and they are not equivalent — not because some vendors have better models, but because AI can only answer questions about data it can see.

Copilot inside Planner works on a plan. It will summarize what is in front of it, draft tasks, and answer questions about that plan's contents. The Planner Agent extends this. It is useful and Microsoft is shipping against it steadily.

What it cannot do is answer a portfolio question, because the portfolio is not in the plan. Ask which initiatives are at risk this quarter, whether you have the capacity for the roadmap you just approved, or which program is consuming budget without delivering benefits, and the data required has never been in Planner in either edition.

This is a context boundary, not a model limitation, and no improvement in the model moves it.

Portfolio-level AI needs a portfolio-level data layer underneath it. That applies equally to every option on this page: an AI feature is worth exactly as much as the data it can reach.

Four questions that decide your route

Feature comparisons are the slowest way to make this decision. These four settle it faster.

1. Where must the data live? If portfolio data has to stay inside your own tenant, you are on route 2 or 3 and the rest is a shortlist exercise.
2. Who will own it in year two? Deployment ends; ownership does not. Without a named person with capacity to administer an environment permanently, routes 2 and 3 get harder over time rather than easier.
3. What else do you deliver work in? If the answer is only Planner, every route works. If it includes Jira, Azure DevOps, Microsoft Project or Smartsheet, that narrows things considerably.
4. How soon do you need the first portfolio view? Weeks and months are both legitimate answers, but they point in different directions.

Where PPM Express Enterprise fits

PPM Express is route 4, and we would rather be clear about that than pretend to be all four.

PPM Express Enterprise connects the Planner plans that represent real initiatives — Basic and Premium, including plans created in Teams — and holds the portfolio above them. Programs and portfolios, resource capacity and utilization, budgets, forecasts and benefits, risks and issues, prioritization and funding scenarios, and reporting executives open themselves. The Planner integration reads your plans and never writes back, so Planner stays the source of truth for the work and nothing changes for the teams doing it.

One flat annual subscription with unlimited users, so the people who only read a report are not a licensing decision. Jira, Azure DevOps, Microsoft Project, Smartsheet and monday.com connect into the same portfolio. And the AI works at portfolio level, where the questions actually are — status summaries generated from live delivery data when you ask or when a project syncs, and AI agents that monitor 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.

If tenant residency is a requirement you cannot move on, one of the Power Platform products on this page is your answer, and you should hear that from us rather than discover it in week six of an evaluation.

Frequently asked questions

What is Microsoft PPM in 2026? There is no longer a single Microsoft PPM product. The term historically meant Project Server and Project Online, both of which have been retired or are retiring. In 2026 it describes four approaches: native Microsoft Planner, a self-built Power Platform solution, a commercial Power Platform product deployed in your tenant, or a hosted portfolio layer reading your Microsoft data.

What replaced Microsoft Project Online? No single product replaced it. Microsoft Planner Premium inherited the scheduling capability that was Project for the web, but enterprise resource management, project financials, benefits tracking, portfolio analysis and risk registers did not carry across. Organizations close that gap with a Power Platform solution or a separate portfolio layer.

Can Microsoft Planner do portfolio management? Partly. Planner Premium includes Portfolios, which roll several Premium plans into one view. Microsoft documents that Portfolios exclude Basic plans and require a Plan 3 or Plan 5 licence to create or edit. More fundamentally, a Portfolio aggregates tasks, so it does not hold capacity, cost, benefits or risk data.

Does Copilot work for project portfolio management? Copilot works well within a single plan — summarizing it, drafting tasks, answering questions about its contents. It cannot answer portfolio-level questions because portfolio data has never been stored in Planner. That is a limit of what the data covers rather than of the model, so portfolio AI requires a portfolio data layer underneath it.

Which Microsoft PPM approach is right for us? Start with four questions rather than a feature list: where the data must live, who will own the solution in year two, what other tools your teams deliver work in, and how soon you need a first portfolio view. Data residency is usually the decisive one — a hard tenant-residency requirement rules out hosted options entirely.

The short version

Microsoft PPM is no longer a product, it is a decision between four routes. Native Planner handles the work and stops short of the portfolio. Building on the Power Platform gives you tenant residency and unlimited extensibility in exchange for permanent ownership. Buying a Power Platform product trades some of that ownership for a supported solution. And a hosted portfolio layer keeps Planner exactly as it is while holding everything above it, at the cost of your data being hosted elsewhere. Answer the four questions honestly and the shortlist writes itself.

The mixed-estate problem this piece describes — Planner in the business, Jira in engineering, Microsoft Project somewhere else — is the case a portfolio layer above Microsoft Planner handles better than anything deployed inside one tool. PPM Express reads all of them into one portfolio without asking any team to change how they work. Worth a look if your delivery is spread wider than your reporting.