A B51 downloadsDrag your Microsoft To Do tasks into notes from a sidebar, and see which ones a note already holds. Read-only.
A sidebar in Obsidian that lists your Microsoft To Do tasks. Drag a task into a note to insert it as a Markdown task line: it lands on a line of its own, not inside an existing line, indented like the line you dropped it on. Or use a task's + button to add it at the cursor: on the cursor's line if that is empty, otherwise on a new line below it, with the same indentation, and never inside the note's properties. Clicking a task the note already holds selects its line there. Links in a task's title open in your browser. Select Notes under a task to read its notes; links in them open in your browser.
Microsoft To Do itself does not let you drag tasks into other apps, so the drag starts in this panel instead.
title:, note: and list: match only that part, as in note:invoice.due-date: takes today, tomorrow, overdue, upcoming, none or a
date or the start of one (2026-11-20, 2026-11).is: takes open, completed or important.{{title}} stands for the active note's name, as in Obsidian's
templates, and follows you from note to note: list:{{title}} shows the
list named after the note, {{title}} alone any task that mentions it.
With no note open it matches nothing."quoted phrases" match as a whole, - excludes a term (-list:work),
and OR in capitals matches either side (milk OR bread); terms without
OR must all match.[x] ([<], [>] and
other marks do not count). Matching ignores case, indentation, whitespace,
the checkbox, and trailing emojis, dates and links. Each group's title
shows how many of its tasks the note holds, such as ○2 ✓1, open or
collapsed.- [x].The plugin only reads your tasks. It never creates, changes or completes anything in To Do.
This plugin is not made by or affiliated with Microsoft. Microsoft To Do is a trademark of Microsoft.
login.microsoftonline.com to sign in and graph.microsoft.com to read
your To Do lists and tasks. Nothing is sent anywhere else.data.json in your vault.The plugin signs in to Microsoft itself, with no other software needed. It needs an app registration in Microsoft Entra so that Microsoft knows which app is asking. There is no shared one: you register your own, once, which takes about five minutes and keeps your tasks between you and Microsoft.
consumers for personal accounts only;common for an app that accepts both work and personal accounts.Open the panel from the ribbon icon or with the command Microsoft To Do Panel: Open panel.
The sign-in (a refresh token) is stored in Obsidian's secret storage on this device, never in the vault or the plugin's settings file, so it is not synced or committed. Each vault keeps its own sign-in; sign in once per vault on each device. Changing the client ID or tenant, or selecting Sign out, ends it.
The dialog shows Microsoft's message, with a hint for the common setup mistakes:
| Message starts with | Fix |
|---|---|
AADSTS50059 |
Set Tenant to your directory (tenant) ID. |
AADSTS700016 |
Check the client ID and tenant. |
AADSTS7000218 |
Turn on Allow public client flows in the app registration. |
AADSTS65001 |
The permission is not granted yet; an administrator may need to approve it. |
Some organisations block device code sign-in altogether. If yours does, the plugin cannot sign in there.
Requires Obsidian 1.11.4 or newer, for secret storage.
Au2mater/obsidian-microsoft-todo-panel in the BRAT
plugin to get the latest release.main.js, manifest.json and styles.css from the
latest release
into <vault>/.obsidian/plugins/microsoft-todo-panel/, then enable the
plugin under Settings → Community plugins.| Setting | Default | Notes |
|---|---|---|
| The settings tab shows your Microsoft account and the task template. The rest | ||
| is under Advanced, collapsed. |
| Setting | Default | Notes |
|---|---|---|
| Client ID | empty | From your app registration. Shown up front until you sign in. |
| Tenant | common |
Tenant ID, common, organizations or consumers. Shown up front until you sign in. |
| Task template | - [ ] {{title}} {{due}} |
{{title}}, {{due}}, {{date}}, {{list}}, {{link}}, {{id}} |
| Due date format (advanced) | 📅 {{date}} |
What {{due}} becomes. {{date}} is YYYY-MM-DD. |
| Completed tasks to load (advanced) | 7 days |
How far back the show-completed toggle reaches; 0 hides it. |
| Daily note date format (advanced) | YYYY-MM-DD |
Moment.js format of daily note file names. |
| Permissions (advanced) | Tasks.Read |
Microsoft Graph permissions to ask for. |
{{due}} is empty for a task with no due date, and the spaces around it
collapse. {{link}} is https://to-do.office.com/tasks/id/<task id>/details.
Lists with no tasks to show are hidden.
Plain JavaScript with no dependencies. The source is src/plugin.js;
npm run build checks it and writes main.js, the file Obsidian loads. To
try a change, build it into a vault:
./install.sh "/path/to/vault/.obsidian" # builds, then copies
npm test
The tests load src/plugin.js against a small stand-in for the Obsidian API and
cover sign-in, token refresh, reading from Microsoft Graph and note matching.
To release, bump version in manifest.json and package.json, add it to
versions.json and commit. Push the tag first and the branch only once the
release exists, because the community directory reads manifest.json from the
default branch and expects a release for that version:
git tag 1.2.0 && git push origin 1.2.0 # the workflow builds and publishes
# wait for the release to appear, then:
git push origin main
The release workflow tests the plugin, attests the build provenance of the release files and publishes the GitHub release.