Power Automate’s Planner connector was built for classic (basic) Planner plans.
Adding attachments (including links) is not done with “Create task”
→ it’s done via Update task details → references
Planner Premium (a.k.a. Project for the web / Loop-backed tasks) is only partially compatible
If the Premium plan happens to be surfaced through the Planner UI, some connector calls may work
If it’s a true Premium-only plan, attachments via Power Automate are not supported unless you use Microsoft Graph
Why your flow does not work with Planner Premium
Works
- Basic Planner plans
- Tasks visible in classic Planner
- Updating task details → references
❌ Does NOT reliably work
- Planner Premium / Project for the web plans
- Premium-only task details schema
- Attachments via Planner connector
This is not a bug in your flow, it’s a feature gap.
Planner Premium uses:
- Dataverse-backed tasks
- A different task/attachment model
- APIs that Power Automate’s Planner connector does not fully expose
The key technical limitation
Power Automate’s Planner → Update task details action writes to:
plannerTaskDetails.references
That property:
- ✅ Exists for classic Planner
- ❌ Is ignored or blocked for Premium tasks
So the flow may:
- Run successfully
- Return no error
- But silently fail to attach the link
This is why it feels confusing.
What actually works today (your real options)
Option 1 - Use Microsoft Graph (only guaranteed method)
If you must add a link attachment to a Planner Premium task, this is the only reliable way.
High‑level steps:
- Register an Azure AD app
- Grant:
- Tasks.ReadWrite
- Group.ReadWrite.All (if group-based)
- Use Power Automate HTTP action
- Call the Planner task details endpoint
- PATCH the references object manually
Yes, it’s heavier, but it matches Microsoft’s current architecture.
✅ Works 100%
❌ Requires Graph + permissions
Option 2 - Store links in a task field instead of attachments (recommended workaround)
Many teams do this instead:
- Put the URL in:
- Description
- Checklist item
- Custom column (if using Project for the web UI)
Why this is often better:
- Fully supported
- Visible in UI
- No silent failures
- No Graph plumbing
If your goal is “users can click the link”, this is usually sufficient.
Why the confusion exists in the community
There are three overlapping realities that cause mixed answers:
- The Power Automate UI doesn’t distinguish clearly
- The same “Update task details” action appears selectable
- Some Premium plans appear inside the Planner app
- This makes people assume “it’s the same backend”
- But, it isn’t
- People test on basic Planner without realizing it
- Then report success
- Others try Premium and hit silent failure
So multiple “correct” answers exist, but for different plan types.