Quick answer: Microsoft Planner's People view shows who is assigned to what inside one plan. That is what it was built for, not for a view across plans. The moment a PM or resource manager is running more than a single plan, the per-plan Assignments and People screens stop answering the real question, which is workload, not assignment count. Planner Premium's Portfolios roll several plans' tasks into one screen, but a Portfolio still counts tasks, not hours or capacity, so it does not close the gap either. Doing real Microsoft Planner resource management across more than one plan needs three things Planner does not supply on its own: consistent owner identities across plans, an explicit capacity input per person, and one layer that reads workload across every connected plan at once.
This is the diagnostic piece: why the People view runs out of road, and what actually has to exist above it. For a worked numeric walkthrough of building a capacity view by hand, see the companion post, Capacity Planning for Microsoft Planner.
What Planner's People view actually shows
Inside a single plan, Planner's People view is genuinely useful. It groups every task by assignee, shows a progress ring per person, and lets you filter or re-assign directly from that screen. Even on a Basic (Plan 1) licence, that view sits alongside a real feature set: Timeline for scheduling, sprints for iterative teams, task dependencies, and custom fields for whatever metadata a team wants to track. Planner Plan 1 is more capable than some older comparisons give it credit for. This is not a "Basic is a toy" argument.
The limit is structural, not a missing feature. A plan lives inside one Microsoft 365 group or team, and the People view is scoped to that group. It has no concept of a second plan. If someone on your team is assigned tasks in five different plans across five different groups, you get five separate People views, each unaware the other four exist. There is no button inside Planner that merges them, because merging them was never the job the view was designed for.
Task count vs. real workload
This is the distinction the rest of this article hinges on, so it is worth stating plainly: the number next to someone's name in Planner's People view is a count of cards assigned to them. It is not a measure of hours, effort, or how full their week is.
A task with nine subtasks and a task that takes fifteen minutes look identical in a People view count.
Nothing in Planner, Basic or Premium, attaches an effort estimate to a task by default, and nothing converts an assignment count into a percentage of someone's available time. Premium's workload chart is a genuine improvement inside one plan: it shows task counts or, with some configuration, points, bucketed by assignee. But it is still counting objects inside a single plan, not hours across a person's real commitments. Someone showing "3 tasks" in Plan A and "12 tasks" in Plan B is not obviously more loaded in Plan B. A task in Plan A might be a two-week deliverable, and a task in Plan B might be a five-minute checklist item. Task count is a proxy people reach for because it is the number Planner shows them, not because it answers the question they're actually asking.
What Microsoft Planner resource management actually requires
Closing this gap does not require replacing Planner or migrating anyone's work. It requires three things layered on top of what Planner already tracks.
1. Consistent owners across plans. The same person needs to be recognized as the same person in every plan they touch. That sounds trivial until you have five plans where one uses full names, another uses a nickname, and assignment is inconsistent about whether it's tracking a UPN or a display name. Without a stable identity behind each assignee, "cross-plan workload" is just a spreadsheet of names that don't quite match.
2. Explicit capacity input. Somewhere, a number has to exist for how many hours or days a person actually has available in a given week or sprint. Planner has no field for this at any tier: it tracks what people are assigned, never what they have room for. Without a capacity number to compare assignments against, "workload" collapses back into a task count with a different label.
3. One visibility layer above the plans. Someone, whether a resource manager, a PMO lead, or a delivery manager, needs a single screen that reads every connected plan and shows assignments against capacity in one place, rather than switching between five People views and holding the comparison in their head. This is the layer Planner's Premium Portfolios come closest to and still don't provide, because a Portfolio rolls up tasks, not people or hours.
A dedicated resource management layer is built to do exactly this: hold one identity per person, take a capacity input, and read workload across whatever plans a team actually runs work in, Planner or otherwise.
Basic vs. Premium: what each edition gives you to start from
Which native starting point you have depends entirely on licence tier, and it's worth being precise about what each one actually includes.
Planner Basic (Plan 1) gives you Timeline, People view, sprints, dependencies and custom fields, all scoped to a single plan, with no roll-up above it. Planner Premium (Plan 3 or Plan 5) adds native Portfolios: a Premium plan can belong to a Portfolio, and other users with the right Premium licence get shared, read-only access to that Portfolio's rolled-up task view. That is a real feature, not vaporware, but it excludes Basic plans entirely, so a mixed environment of Basic and Premium plans can never be fully represented in one native Portfolio. And a Portfolio, again, aggregates tasks. It carries no capacity, budget, benefit or risk data, because Planner was never built to hold those.
One more distinction matters for a custom build: Microsoft's Graph Planner API only reaches Basic plans. Premium plans and Portfolios are surfaced through a separate Power Platform environment and permission model, and a Power BI report spanning both is, in practice, two integrations, not one.
It's also worth naming what AI does and doesn't change here. Planner Agent already generates automatic status reports for shared Basic and Premium plans, and ChatGPT can reach Planner data today through custom MCP connectors. Neither one adds capacity data or a cross-plan owner view. They summarize what's already in a plan, faster. AI-generated reporting is genuinely useful, but it isn't the thing missing from this picture.
Where PPM Express for Microsoft Planner fits
Not every organization needs the same amount of cross-plan visibility, and it's worth being clear about what this integration is built to handle.
A small team or a PMO just getting past ad hoc Planner sprawl usually needs three things: a consistent owner list, a light capacity input, and a workload view across a handful of plans, enough to answer "does anyone on this list have room this month" without building a data warehouse. PPM Express for Microsoft Planner is aimed at exactly that: it connects your active Planner plans in one tenant, maintains one cross-plan view, and includes manual capacity planning for your team, enough to compare real assignments against declared availability, not just count cards. Where the numbers come purely from rolled-up tasks rather than a declared capacity figure, they're shown as workload indicators, not utilization, so the distinction from the previous section stays honest in the product itself.
That scope has a ceiling: organization-wide capacity, longer planning horizons, multiple resource pools, or financial and governance data tied to the same workload picture. Past it is where PPM Express's broader project portfolio management capabilities take over. That's a deliberate line: this integration solves the specific problem this article describes, and the rest of the platform is for organizations that have outgrown it in scale, not in kind.
PPM Express: Resource Utilization / Availability and Capacity Views across multiple plans
If you want the fuller picture of how capacity planning works once you're past ad hoc spreadsheets, the resource capacity planning guide covers the broader method this article assumes.
Frequently asked questions
Not directly. The People view shows how many tasks are assigned to each person within one plan, which is a count of cards, not a measure of hours or capacity. Planner has no field, in any edition, for how much time a person actually has available.
Partially, on Premium. Planner Premium's Portfolios roll several Premium plans' tasks into one shared, read-only view. That's real cross-plan visibility for tasks, but it excludes Basic plans and carries no capacity, budget or risk data, so it doesn't answer a workload question on its own.
No. A Portfolio aggregates tasks across plans. Capacity planning requires comparing what people are assigned against how much time they actually have, and Planner, whether Basic or Premium, has no native field for a person's available capacity.
No, and this is the most common misreading of Planner data. A task can represent fifteen minutes or three weeks of work; Planner's assignment count treats them identically. Task count is a proxy for workload, not a measurement of it.
Yes, with a caveat worth planning around: the Graph Planner API only covers Basic plans. Premium plans and Portfolios are exposed through a separate Power Platform environment and permission model, so a report spanning both is effectively two integrations rather than one.
Not this specific one. Planner Agent already generates automatic status reports for shared Basic and Premium plans, and it does that well. But it summarizes what's inside a plan; it doesn't add a capacity input or merge owner identities across plans.
If your team's Planner footprint has grown past the point where one plan's People view answers "who has room this month," that's precisely the gap this article has been describing, and it's what PPM Express for Microsoft Planner is built to close: a consistent cross-plan owner list and a workload view across the plans you connect. Worth a look if you've hit that ceiling.
.svg){kind=small}
