Productivity · Integration
Microsoft To Do
Add Microsoft To Do to your product for your customers, and give your AI agents governed access to it.
Microsoft To Do is reached through Microsoft Graph, so the integration inherits Graph's habits rather than inventing its own. A task list holds tasks, a task holds checklist items, which is how subtasks are expressed, and a linked resource is the pointer back to whatever created the task. That last one is the field an embedded integration should care about most: it is what lets your product find its own tasks again and send a user back to the thing the task is really about. Reminders, recurrence and due dates carry a timezone explicitly, and getting that wrong is how a task announces itself at four in the morning. Staying in step is a delta query rather than a re-read of everything, so a list with years of history is read once and then only for what has changed. Each person grants consent individually, which limits an integration to the lists that user owns or has been shared into.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each user consent for themselves, so anything your product files lands in the To Do list they already work from.
Attach a linked resource to every task you create, so your product can find its own tasks again and send a user back to the source.
Express subtasks as checklist items rather than inventing a convention To Do will not display.
Use a delta query to pick up changes, so a long-lived list is not re-read on every sync.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent lists what is due today across a user's task lists and proposes an order to work them in.
An agent creates a task with a reminder in the user's own timezone, and the list it wrote to is recorded.
An agent closes a task once the work it pointed at has been confirmed complete.
Example prompt
What is due today in my To Do lists, and which of those came from our system rather than from me?
Set up Microsoft To Do in 4 steps
- 01Enable the Microsoft To Do connector in your fastn dashboard.
- 02Have each user authorise their own account through Microsoft Graph, so your product sees only the lists they own or share.
- 03Decide which lists your product writes to, attach a linked resource to every task you create, and store a delta token per user.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Microsoft To Do integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Microsoft To Do integration without building it. Your customers connect their own Microsoft To Do account inside your product and work their work items, assignees and due dates there, with no per-customer code on your side.
- Handle the part that actually costs time: every team configures its own fields, statuses and workflow stages. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Microsoft To Do update is not your on-call problem.
- One integration serves your product and your agents. The same governed Microsoft To Do connection powers in-product features and gives AI agents scoped, audited access, so you keep work items in step with what happens in your product without wiring it twice.
Used by these teams
Compare with
Todoist
Google TasksWorks well with
Microsoft OutlookOften used alongside
Tools the same teams tend to run next to Microsoft To Do, across other categories.
Notion
Box
Docusign
AWS Simple Storage ServiceMicrosoft To Do integration FAQ
How do I add a Microsoft To Do integration to my product?
Enable the Microsoft To Do connector in your fastn dashboard, then let each customer authenticate their own Microsoft To Do account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Microsoft To Do client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Microsoft To Do account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Microsoft To Do account and only ever sees their own work items, assignees and due dates. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Microsoft To Do integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent lists what is due today across a user's task lists and proposes an order to work them in.
Who maintains the Microsoft To Do integration?
fastn does. When Microsoft To Do changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can my product create and update work in Microsoft To Do automatically?
Yes. Items can be created, updated, assigned and transitioned from your product, and changes made in Microsoft To Do can trigger your workflows in return.
Does it adapt to each team's own Microsoft To Do setup?
Yes. However a team has configured Microsoft To Do, whether that is custom fields, statuses and workflow stages or its own calendars and working hours, those are mapped per customer, so an unusual setup works without custom code from you.
What can I build with the Microsoft To Do integration?
A common starting point: let each user consent for themselves, so anything your product files lands in the To Do list they already work from. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Microsoft To Do integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Microsoft To Do does not change your per-connector cost. You can start free with 3 connected accounts.
Add Microsoft To Do to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.