Automating Microsoft Planner: Tasks from Forms, Emails, and Approvals

Microsoft Planner can be automated with Power Automate by combining native triggers such as “When a new task is created,” “When a task is assigned to me,” and “When a task is completed” with actions to create, update, and assign tasks. This allows Planner cards to be generated automatically from Microsoft Forms submissions, incoming emails, or completed approval processes, without anyone having to create the card by hand. The Planner connector is part of the standard Power Automate environment in Microsoft 365 and was introduced by Microsoft, together with its triggers, on the official Power Platform blog. As of: August 2026.

Which triggers and actions does the Planner connector offer in Power Automate?

The Planner connector provides three central triggers that can start a flow.

• When a new task is created: Responds to every new card in a selected plan, for example to synchronize it with a SharePoint list or another system.
• When a task is assigned to me: Fires as soon as a task is assigned to a person, for example to generate a notification or a calendar entry.
• When a task is completed: Responds to the closing of a card and can mirror this status in other tools or send a completion notice.

In addition, actions are available for creating, updating, and assigning tasks, and for creating buckets, so a complete process from trigger to filing in Planner can be mapped. Microsoft published details on these triggers in the Power Platform blog on the Planner triggers.

How does a form or an email automatically turn into a Planner task?

The most common approach uses a trigger outside of Planner that starts the “Create task” action within the same flow. A Microsoft Forms form for complaints or internal requests can automatically generate a card in the appropriate plan and bucket for every submission, including title, description, and assignment to the responsible person. Likewise, an Outlook email that is flagged or moved to a specific folder can be used as a trigger to turn it into a task with a due date. A completed approval step from the Approvals connector can also serve as a starting point, for example to automatically create the implementation task in Planner after an approved order. Anyone who wants to set up such processes for several forms, mailboxes, or approval levels at the same time benefits from structured flow planning, such as that provided through a Power Automate consulting engagement.

Where does Planner automation reach its limits?

The classic Planner connector primarily covers basic plans and therefore does not automatically reflect every new interface Microsoft has introduced around Planner. There is also no dedicated trigger for every conceivable status change of a task, only for creation, assignment, and completion. Intermediate steps such as “in progress” or changes to checklists and comments can therefore only be mapped indirectly, for example through additional conditions in the flow or recurring queries of the task status. Anyone who needs more complex approval chains typically combines Planner in practice with the Approvals connector and, if necessary, with SharePoint or Teams, rather than solving everything through Planner triggers alone. These limits are important for process planning so that expectations match what automation can actually deliver.

What does the merger of Planner, To Do, and Project mean for automation?

Microsoft now positions Planner as a shared interface in which, according to its own product description, “to-do lists, tasks, plans, and projects” are brought together in one environment. This is reflected concretely in the tiering of the offerings: the Planner basic version included in Microsoft 365 remains free to use, “Planner Plan 1” adds, among other things, task dependencies, a timeline view, as well as backlogs and sprints, and “Planner and Project Plan 3” additionally adds advanced dependencies and access to Project Online. A footnote on the official product page shows that this consolidation is meant seriously, noting that Project Online will be discontinued on September 30, 2026. For automation, this means: the three classic Planner triggers and the associated actions remain the reliable foundation, while project-related premium features of the higher plans are currently not accessible in the same depth through the standard connector. Details on the scope of features and prices for the individual tiers can be found on the official Microsoft Planner product page.

Frequently asked questions about automating Microsoft Planner

Can I automatically create tasks in Planner with Power Automate when a form is filled out?

Yes, a Microsoft Forms trigger can be connected directly to the Planner action for creating a task. This means a card is automatically created in the appropriate plan and bucket every time the form is submitted, without any manual step.

Does Power Automate fire when only the status of a task changes, without it being completed?

No, the Planner connector does not offer a dedicated trigger for this; it only responds to the creation, assignment, and completion of a task. Intermediate statuses can only be replicated through additional logic in the flow or periodic queries.

Does Planner automation also work with the new premium features such as sprints or the timeline view?

These features belong to the paid Planner tiers and cannot be automated to the same extent through the classic Power Automate connector as simple tasks in basic plans. For such scenarios, it is worth specifically checking which steps the connector actually covers before building a flow around it.

Can I link approval processes directly to Planner tasks?

Yes, to do this you typically combine the Planner connector with the Approvals connector: after an approval is granted, the flow automatically creates or updates the corresponding task in Planner. The Planner connector itself does not have a dedicated “approval” trigger; the link is created in the flow design.