We have identified what appears to be an inconsistency or internal error in the Microsoft ecosystem when using Planner Premium (Planner Plan 1) together with Power Automate.
Specifically, when using Planner-related triggers in Power Automate (for example, “When a task is completed”), Planner Premium plans do not appear in the Plan ID selector, even if they belong to the same Microsoft 365 Group. Moreover, attempting to manually insert the Premium Plan ID as a custom value results in an error and prevents the flow from being saved.
This means that:
- Power Automate flows work correctly with basic Planner plans, but
- The same flows do not work with Planner Premium plans, despite the user having an active paid license.
From our point of view, this should not be considered a feature request, but rather an incoherence or limitation introduced at platform level. Subscribing to a higher Planner plan (Planner Plan 1) should never result in reduced compatibility or functionality when working with Power Automate—quite the opposite.
If Premium plans are offered as part of Microsoft’s licensing model, Power Automate should fully support them by design, without requiring workarounds or excluding them from standard Planner connectors and triggers. This is something that should be taken into account internally when developing and maintaining Power Automate.
This limitation has a direct impact on real, production use cases, especially in professional and organizational environments where Planner Premium is used intentionally for its advanced features. At present, it is very difficult to justify paying for a Planner license that introduces disadvantages compared to the basic, free plan when automating processes.
We would greatly appreciate this issue being reviewed as a platform compatibility problem, and escalated internally so that Planner Premium plans are treated on equal terms with basic plans within Power Automate connectors and triggers.
Thank you for considering this feedback.
P.S. A support ticket has already been opened with Microsoft for this issue. The support team confirmed the limitation and explicitly recommended publishing this request in the Microsoft Ideas portal and the Microsoft Power Platform Community to raise visibility with the product teams.
