Skip to content
FidelicRoster →

Setup · Planner + Microsoft To Do

Wire Planner and Microsoft To Do to your Fidelic agent

How the agent files action items into Planner buckets and personal To Do lists after meetings, threads, and customer escalations.

← Back to Microsoft Teams

Prerequisites

  • · Microsoft Planner license (included with most Microsoft 365 Business and Enterprise plans)
  • · Tasks.ReadWrite Microsoft Graph scope grantable by a Global Administrator
  • · List of Planner buckets the agent should write into (one per team or function)

Permissions requested

  • · Tasks.ReadWrite — create and update tasks in Planner buckets and Microsoft To Do lists the agent is added to
  • · Group.Read.All — enumerate Planner-enabled groups during setup so the agent can find the right buckets
  • · User.Read — read display names for task assignment

Step-by-step

1. Identify Planner buckets

Pick the Planner buckets where action items should land. Common patterns: one bucket per recurring meeting (Weekly leadership, Monday revops); one per function (Engineering, Customer success). Make a list with the Planner Group name and bucket name.

2. Grant the Tasks scope

From Microsoft Entra admin center, add Tasks.ReadWrite to the Fidelic app registration and grant tenant-wide consent.

3. Add the agent to each Planner group

From the Microsoft Teams channel that owns the Planner board, open the Planner tab → Settings → Members and add the Fidelic service principal as a Member. The agent picks up the bucket and can create tasks within minutes.

4. Map use cases to buckets

In the Fidelic console, set the default Planner bucket per use case — meeting notes file action items into the meeting's bucket, support escalations file into the support bucket, and so on. The agent only writes to buckets you have authorized.

How to verify it worked

Trigger a meeting summary or test escalation. Within a minute the action items appear in the configured Planner bucket, assigned and dated, with a link back to the source thread.

Gotchas

Planner is group-scoped. The agent needs membership in the underlying Microsoft 365 Group that owns the Planner board, not just channel access. Adding the agent through the Planner tab handles this; manual group membership works too.

Microsoft To Do tasks are personal. If the agent should file a task on a specific user's To Do list (rather than a Planner bucket), the user must approve the agent through Microsoft To Do's app permissions. Plan for this if your use case calls for personal task assignment.

For the IT admin

Audit. Task creates and updates appear under Planner Activity in the Microsoft 365 audit log, attributed to the Fidelic app principal. Filter by Planner workload to see exactly which buckets and tasks the agent has touched.

Revocation. Removing the Fidelic principal from a Planner board cuts off access to that board. Removing the Tasks.ReadWrite scope cuts off Planner and To Do access tenant-wide.

Where to next