Microsoft Planner Portfolios can put several plans on one Roadmap, with each plan on its own row and a status that someone sets by hand (Microsoft's Portfolios article). Editing a portfolio needs Planner with Project Plan 3 or Project Plan 5, and the listed sources do not confirm that Microsoft Project or Project for the web shows every client engagement on one screen. Ask your Microsoft admin to confirm that in writing before you choose a tool.
Can one Planner portfolio show every client engagement?
Yes, for supported plans. A Planner portfolio adds several plans to one Roadmap, with each plan on its own row (Microsoft's Portfolios article). Basic plans, Azure DevOps projects, and Project Online projects are not supported, so keep those engagements on a separate list and add only the supported plans.
Set up the portfolio in these steps:
- Name each plan with the client first, in the form "[Client name]: [engagement name]". The Roadmap shows each plan on its own row (Microsoft's Portfolios article), so the name is the first thing a sponsor reads.
- Check each plan's type before you add it. Move any basic, Azure DevOps, or Project Online engagement to the separate list, because Microsoft's article excludes those types (Microsoft's Portfolios article).
- Add each plan to the portfolio, then open the Roadmap. Confirm that each engagement appears once, with its client name in the title. If an engagement appears twice or not at all, fix the plan list before going on.
Which Microsoft licences does a portfolio need?
Editing a Microsoft portfolio needs Planner with Project Plan 3 or Project Plan 5, and creating one needs the same licences. People with Planner in Microsoft 365 or Planner Plan 1 can view shared portfolios in read-only mode, and basic Planner plans are not supported (Microsoft's Portfolios article).
Ask your Microsoft admin to confirm each person's licence against those names before anything is shared. Write the editors and viewers down first:
Editors (Planner with Project Plan 3 or Project Plan 5): [name], [name]
Viewers, read-only (Planner in Microsoft 365 or Planner Plan 1): [client contact], [name]
Plan for a client to be a viewer unless your admin has confirmed a licence for them.
Do I need a Planner Premium licence?
The listed Microsoft source does not define Planner Premium or map that edition to Project Plan 3 or Project Plan 5. Microsoft's Portfolios article names only those two licences for editing. Confirm with your admin which Planner edition each editor holds before you add their plans to a portfolio.
PPM Express says teams choose Planner Premium "when a plan needs real scheduling". That is a vendor description, not a Microsoft definition. Onplana says Portfolios "rolls up your premium plans", which is also the vendor's wording rather than Microsoft's.
Confirm the match with these steps:
- Ask your admin which Planner edition each editor holds, and whether that edition includes Project Plan 3 or Project Plan 5.
- Write the answer beside each name in the editor list above.
- Leave any plan whose edition is unconfirmed out of the portfolio until your admin confirms it in writing.
Can Microsoft Project or Project for the web show all client engagements on one screen?
The listed sources do not confirm it. Onplana says Microsoft Project computes variance against a baseline instead of asking, and that business-driver analysis is documented under Project Server. ONES describes Microsoft's portfolio setup. Neither says whether Project for the web shows every client engagement on one screen. Put the questions below to your admin in writing.
Both are vendor descriptions, not Microsoft documentation:
- ONES lists six setup steps for Microsoft's project portfolio management: framework, enterprise project structure, demand management, resource capacity and costs, portfolio analyses, and governance.
The listed sources leave two points open:
- Whether Project for the web has a portfolio view that lists more than one engagement.
- Whether Project Online or Project Server is still offered to your firm. ONES does not say, and Microsoft's Portfolios article excludes Project Online projects from Planner portfolios.
The questions for your admin:
- Which product does our firm license for portfolio reporting: Planner, Project for the web, Project Plan 3 or Project Plan 5, or Project Server?
- In that product, which view shows more than one client engagement, and what is it called?
- Can a client see only its own engagements in that view?
- Which licence does each editor need, and does a client viewer need one?
- Is Project Online or Project Server still offered to us?
What does a Microsoft portfolio roll up?
A Microsoft portfolio shows each plan on its own Roadmap row, with one status per plan: Not started, On track, At risk, Off track, or Closed (Microsoft's Portfolios article). Onplana describes the roll-up fields as each plan's owner, progress, and start and finish dates. Microsoft says the status is set manually.
Onplana describes a typed status as one that can stay "green until somebody decides otherwise". Agree what each value means before the first roll-up, and write the meanings where editors can see them:
On track: [condition the editors agreed]
At risk: [condition the editors agreed]
Off track: [condition the editors agreed]
Check each status against its plan before a sponsor meeting. The roll-up shows what an editor last set, not what the plan's dates now say.
This is an illustrative status note. Every name, date, and status in it is a placeholder, not a real engagement:
Portfolio status for [portfolio name], [date]
- [Client name], [engagement name]: [status value]. Meaning used: [condition from the list above].
- Decision needed from [decision owner] by [date]: [decision].
- Next step: [owner name], by [date].
Can I see cost and capacity in one place?
A Microsoft portfolio does not show cost, budget, expected benefit, or who is free. Onplana says the portfolio has no cost, budget, or expected benefit field, and PPM Express says Planner has "assignments but not availability". Keep cost and availability records in the tools the team already uses, and point to them in each status note.
PPM Express says the questions a steering committee asks are not in Planner, which has "no view of who is available next quarter". Onplana makes the same point about money: a question about what a portfolio costs is not one the portfolio can answer (Onplana).
In our reading, a sponsor who asks about cost or availability needs those records beside the status note, not buried in the portfolio. Keep each record in its usual tool, and add a one-line pointer to it in the status note.
Can I keep each client's data separate in one portfolio?
Not from the listed sources. Microsoft's Portfolios article covers sharing and access management in general terms, and none of the listed sources sets out client-level separation. Before any client is invited, check who can open the portfolio and each plan in it, then test what a client viewer can see.
- List everyone who will open the portfolio, by name, before you share it. Include each client contact.
- Check who has access to the portfolio and to each plan in it. Start with the sharing and access section of Microsoft's Portfolios article.
- Ask a client viewer with read-only access to open the portfolio and say what they can see. If they can see another client's plan, invite no other clients until the access is fixed.
In our reading, a full-firm portfolio is the easiest link to send, but it can show a client work that belongs to someone else. A separate portfolio for each client avoids that, but each one needs its own upkeep and a named maintainer. Write down who maintains each portfolio.
Which vendor claims should I check against Microsoft's article?
Check vendor claims about licences and plan types against Microsoft's Portfolios article first. ProjectManager says Planner "cannot display data from multiple plans at once", which Microsoft's article contradicts. Placker's no-upgrade claim describes its own grouping layer, and PPM Express does not explain how Premium-only fields roll up.
ProjectManager also says Premium "displays multiple plans in one dashboard", which conflicts with its own statement about Planner. Microsoft's article describes what the feature shows: each plan on its own Roadmap row, with a status set by hand (Microsoft's Portfolios article).
Placker says its approach needs no licence upgrade. That describes Placker's own grouping layer. Microsoft's article does not support a no-upgrade path for editing a Microsoft portfolio.
When a vendor page and Microsoft's article disagree, follow Microsoft's article for licences and feature limits. Ask the vendor to show the disputed point working in a test plan.
When should I add a reporting layer or a dedicated PPM tool?
Add a reporting layer when leadership needs cost, client separation, or sponsor decisions in the same view as the roll-up. The roll-up described above has no cost field, and the listed sources do not show client separation. Before you compare prices, ask each vendor in writing which Microsoft licences it needs and which data it reads.
PPM Express says it reads "plans, buckets, tasks, assignments, dates and progress", and that it has no access to Teams conversations, SharePoint files, or mailboxes. Set that list beside the data your client plans hold, and check whether any field a sponsor needs is missing.
Placker lists agency client projects as a use case, but its page does not explain how client data is kept apart. Ask any vendor to show that separation in a test before you compare prices.
Ask each vendor for these in writing:
- The Microsoft licences its layer needs.
- The data it reads from Planner and from other tools.
- How its permissions apply to each client.
How do I test a portfolio before I rely on it?
Run the portfolio on a few sample plans, then compare each Roadmap row with its plan. Fix any mismatch in the plan or the status before you decide the tool is at fault. Bring the licence list and your admin's written answers to the decision.
- Add a few sample plans to a test portfolio. Use plans that hold no live client work.
- Compare each Roadmap row with its plan's tasks and dates.
- Write down each mismatch, then fix the plan or the status. Check the row again.
- Set the statuses on a fixed day before each sponsor meeting, so the portfolio reflects the plans before anyone reads it.
Run the viewer check from the client data section on the test portfolio too, before any real engagement is added.