Microsoft Planner’s “Unassigned” filter is real, but it only works inside one plan at a time, and it solves a smaller problem than it looks like it solves. An overdue task still has an owner — Planner’s notification system is actively watching it and can nudge that person that it’s late. An unassigned task has no owner, which means nothing in Planner is watching it at all: no “Assigned to me” entry, no due-date reminder, no notification of any kind. That’s a quieter, more dangerous failure mode than lateness, and a flat “Unassigned” toggle inside one plan doesn’t answer “where across my whole team’s work is this happening?”
Does Planner have a native unassigned tasks filter?
Yes, inside a single plan. Board view lets you filter to “Unassigned,” and Planner lists every owner-less task under the To Do bucket — a Microsoft Q&A thread confirms exactly this behavior, from a tenant that had let 2,400+ unassigned tasks accumulate in one plan before someone went looking for them (Microsoft Q&A). Microsoft’s own accessibility documentation confirms the same filter-by-assignment mechanism, and is explicit that it operates on “the Board tab of the plan” you currently have open (Microsoft Support) — one plan, every time. There’s no tenant-wide or multi-plan version of that toggle. Ten plans means opening the filter ten times.
Why “unassigned” is a different failure mode than “overdue”
An overdue task is a visible problem. It has an owner, that owner’s “Assigned to me” list already contains it, and Planner’s notification settings are built to remind that person their task is late or due soon (Microsoft Support). It’s annoying, but the system is actively pointing at it.
An unassigned task is structurally invisible. Documentation of how Planner notifications actually fire describes two triggers: someone assigns you a task, or a task already assigned to you is coming due or overdue (SharePoint Maven). Both triggers require an assignee to exist. A task with an empty assignments object — the Graph API’s own term for “no one assigned,” per the plannerAssignments resource type, which is a set of properties keyed by user ID and simply has none when no one is assigned (Microsoft Graph) — sits outside both triggers. Nobody gets pinged. Nobody’s list contains it. It doesn’t become a “problem” the way an overdue task does; it just never becomes anyone’s job.
That’s the sharp distinction: overdue tasks are visible and late. Unassigned tasks are invisible and may stay that way indefinitely — not because anyone decided to ignore them, but because Planner’s entire notification model has no hook to hang an alert on when there’s no one to notify.
The compounding blind spot: unassigned tasks can have no due date either
It gets quieter still. In Planner’s data model, assignments and dueDateTime are two separate, optional properties on a plannerTask — neither implies the other (Microsoft Graph). A task can be created with both left blank: no owner, no deadline. That task will never show up on an overdue report, because there’s no due date for dueDateTime < utcNow() to compare against. It will never trigger an assignment notification, because there’s no assignee. It simply exists, parked in a bucket, until a human opens that specific plan, scrolls to that specific bucket, and notices. Scale that across a dozen plans and it’s easy for real work to sit there for months with zero signal anywhere that it’s stalled before it’s even started.
The DIY route: a Power Automate flow (or Graph script) for unassigned tasks
The mechanics are the same shape as building any other cross-plan Planner report — a scheduled flow that calls the Planner “List tasks” action per plan, then narrows the result with a “Filter array” step. The only thing that changes versus an overdue report is the condition: instead of filtering on dueDateTime < utcNow(), you filter on the task’s assignments object being empty.
That sounds like a one-line swap, but the surrounding friction is identical to — and in one way worse than — building an overdue flow:
- Still per-plan. “List tasks” runs against one plan; a dozen plans means a dozen branches or a loop you maintain, same as before.
- Pagination bites sooner. The List tasks action returns at most 100 records per call before you turn on parallelization (Manuel T. Gomes) — and because unassigned tasks tend to be older, stalled, half-created items that accumulate quietly rather than get cleaned up, a plan that’s been running for a year can have far more of them sitting around than it has genuinely overdue tasks at any given moment.
- No severity to band by. An overdue report can band tasks by how late they are (1–7 / 8–30 / 30+ days). An unassigned task has no “how long” dimension unless you also check
createdDateTimeyourself and compute an age — Planner tracks when a task was created, but nothing tracks “how long has this specific task gone without an owner.”
It works, and it’s worth building if the need is narrow and one-off. It’s also a second flow to own, separate from any overdue flow, because the filter conditions don’t compose into one query.
Related cross-plan views
“Who doesn’t own this yet?” is a different question from “what’s late?” and “who’s loaded?” — each needs its own view:
- Microsoft Planner Overdue Tasks Report Across Plans — the visible-lateness cut of the same underlying plans.
- See all Planner tasks across plans — the everything-in-one-list problem.
- Planner tasks by assignee across plans — who owns what, for the tasks that do have an owner.
- Microsoft Planner workload view — who’s overloaded, once ownership exists.
Overdue tasks tell you what’s slipping in plain sight. Unassigned tasks tell you what hasn’t even started being anyone’s responsibility — a different, earlier failure point in the same pipeline.
The shortcut: an Unassigned view across every plan
If building and maintaining a second flow isn’t worth it, that’s what the Unassigned count and filter in Team Workload are for. Its Dashboard and Overdue tabs each carry a running Unassigned count alongside Open, In progress, and No due date, and the person filter has a dedicated “Unassigned” preset — pick it, and every owner-less task across every plan you can access shows up in one list, no Graph query, no Filter array, no per-plan flow to babysit. It treats “nobody owns this yet” as its own tracked category instead of a side effect of a Power Automate condition — crosstowntech.com/planner.