Any word on exposing additional Planner triggers in Power Automate?
Right now, the ONLY triggers I can see are "when a new task is created", "when a task is completed", and "when a task is assigned to me". To make matters worse, even when using those I cannot read/write to custom fields using on Premium Planner boards. Its really frustrating as it feels like we're paying more and getting less when it comes to the "premium" plans.
Planner Agent does not work with Premium Plans
I have been toying around with Microsoft Planner Agent, and I am in love with the potential and the idea as to what it can help us do. It can help take meeting transcripts of weekly catch-up meetings and auto-populate/update different kanban cards and tasks and many other really cool and helpful features that will help DRASTICALLY reduce the time on menial admin work. However, these functionalities only work on basic plans, my team all have premium licenses and use a premium plan, and you would think planner agent would be able to work with premium plans, however, every time I try and leverage planner agent to create a task in our premium plan I keep getting the same response along the lines of: "this feature is not available for premium plans yet". You would think the opposite would be true, but I have chalked it up to the thought that since premium plans have more features, Microsoft haven't completely configured Microsoft Planner Agent to them yet. I would love to see if anyone else is dealing with this same problem, and if so, can share their experience to drive some visibility and SOU to this topic. I would also love to hear and see if anyone has any updates or timelines of when this feature would be available.Strategic Missing Capabilities in the new Microsoft Planner (Enterprise Perspective)
The Present State of Microsoft Planner’s Vision Enterprises want one coherent work-management layer in Microsoft 365 Microsoft’s ambition is to merge To Do, Planner, and Project for the Web into a single platform with Copilot, Goals, unified List/Board/Timeline views, and templates The direction is sound: reduce fragmentation and tool sprawl, standardize data, and give leaders a clean and solid portfolio picture while teams execute in familiar interfaces. In an environment where all employees have access to the same tool, are already included in the resource pool and integration options are basically unlimited, this is a step, that everyone was looking forward to. Nonetheless, the quip that “Microsoft abandoned MS Project 20 years ago” is a joke, but it reflects a real anxiety: if the new Planner displaces familiar scheduling experiences without enterprise-grade controls, PMOs will feel left alone again and disengage, in presence of abundant alternatives. Planner will not replace Microsoft Project, Primavera, or other detailled scheduling tools; those remain essential for deep dependencies, resource leveling, and baselining. Planner’s highest-value role is the management and aggregation layer above them: align goals, normalize metadata, and expose cross-program status. Simplicity matters, but simplicity cannot mean missing capability. If essential functions are absent, governance, traceability, and portfolio visibility suffer, and organizations turn to external tools. Following is a list of core functionality that is currently missing and was needed about a month ago. Current Structural Gaps Date logic too rigid for management use No independent target/due date field; planning often hinges on Start/Finish + Duration, which limits top-down milestone control Custom fields capped at 10 per plan Insufficient for enterprise metadata models and standardized portfolio reporting Maximum task duration of 1,250 days Constricts representation of multi-year initiatives and capital programs No enterprise-grade audit trail Lacks comprehensive, exportable change logs with retention controls for compliance Flat responsibility model Multiple assignees exist, but no roles such as Owner, Reviewer, Approver; no RACI support Insufficient hierarchy and dependencies for roll-ups Summary/sub-tasks exist, but cross-plan links and robust multi-plan aggregation are weak Group-based permissions only Sharing tied to M365 Groups/Teams; no fine-grained task- or field-level permissions; no simple view-only for externals Custom fields lack hyperlink behavior No URL field type; links in text fields are often not clickable for seamless navigation Inconsistent text capture and formatting Notes lack reliable rich-text structure; long entries are hard to read No page breaks or robust formatting for long descriptions Executive-level narratives and governance documentation become unwieldy Limited standardization across plans No global library for reusable custom fields, bucket structures, or templates at tenant/portfolio level Required Enhancements for Enterprise Readiness Flexible date logic Allow target/due dates independent of Start/Finish; add constraints, buffers, alerts, and escalation rules Expanded metadata framework Raise the custom-field limit; add field types (URL, Person, Multi-select), required fields, validation rules, and global field templates Enterprise auditability Provide full change history with export, retention policies, filters by field/user, and API access Role-aware assignments (RACI) Support roles (Owner, Doer, Reviewer, Approver), secondary ownership, and role-based views in people and reports Portfolio-grade structure Enable cross-plan dependencies, milestone roll-ups, program-level summaries, consolidated capacity and risk views Granular access control Introduce view-only sharing, external access without group membership, and task/field-level ACLs to protect sensitive data Hyperlink-enabled fields Add a URL type and clickable rendering in text fields, with previews and allow-lists for approved domains Robust editor for management communication Paragraphs, lists, headings, tables, code/quote blocks, and clean print/PDF output for formal documentation Reusable enterprise templates Tenant-wide libraries for custom fields, buckets, and workflows; versioning and approval flows for governed rollout Reliable data layer A standardized Power BI dataset, webhooks/events, incremental exports, and stable keys for multi-plan, multi-tenant analytics Scaling for long-horizon work Lift or mitigate the 1,250-day limit for leaf tasks and provide guidance or rules for multi-year programs Bottom line Planner can succeed as the enterprise management layer if it remains simple but gains the capabilities listed above. One does not work without the other. If Microsoft does not deliver these functions, enterprises will continue using Project, Primavera, or other scheduling tools — while adopting third-party platforms for governance and portfolio visibility. This would directly undermine Planner’s goal of becoming the unified standard within Microsoft 365. Please, do us a favor and spare organizations from having to implement yet another third-party tool. (And yes: I am aware of multiple enterprises that are in the process of testing and implementating different tools, presicely because of this missing capability)
