Building and customizing solutions using Microsoft 365 Copilot APIs and tools
Based on the documented Plan My Day template, the agent is described as using Microsoft 365 data from these sources:
- Outlook/email
- Teams messages
- SharePoint
- OneDrive
- Calendar
- Personal events from the personal calendar
The documented capabilities also explicitly mention evaluating items across:
- Outlook
- Teams
- SharePoint
- OneDrive
- Calendar
There is no statement that the Plan My Day agent directly accesses Microsoft Planner or Microsoft To Do.
What is supported in the documentation is:
- It can generate a briefing from Microsoft 365 signals such as calendar, emails, Teams messages, SharePoint and OneDrive activity, and personal events.
- It can surface priorities, pending decisions, meeting prep, deadlines, and delegation suggestions based on those listed sources.
- It can be extended by connecting additional resources through Microsoft 365 Copilot connectors or API plugins.
For task systems specifically, the only explicit extension example given is adding a project tracking tool through a Copilot connector, such as Azure DevOps or Jira, so open work items and sprint deadlines can appear in the priority ranking. Planner and To Do are not listed as built-in Plan My Day sources in the material provided.
So the clearest supported interpretation is:
- Direct built-in access is documented for Outlook, Teams, SharePoint, OneDrive, Calendar, and personal calendar events.
- Direct built-in access to Planner or To Do is not documented here.
- If Planner or To Do information appears in the briefing, that is not explicitly described in this material as native source access.
- Additional systems can be brought in through connectors or plugins, depending on the source system.
Related context from Planner shows that Planner itself has separate experiences such as My Tasks and My Day, where tasks can include private tasks, assigned tasks, and flagged emails, but that is separate from the documented Plan My Day agent source list.