Microsoft To Do

Implementation, training & consulting · 40 guides

Get help with Microsoft To Do
Quick answer: Consultants in a Box helps teams implement, train on, and get more value from Microsoft To Do, and connect it with AI and the rest of their software stack. Book a free consultation.

About Microsoft To Do

Operational placement and workflow orchestration

Microsoft To Do is positioned as a lightweight task orchestration layer within a broader Microsoft 365 operating model. It acts as the frontline task catalog for individual contributors and small teams, enabling quick capture of action items, due dates, reminders, and checklists that feed into more formal planning tools when needed.

In day to day operations, Microsoft To Do sits alongside calendar and email workflows, surfacing tasks from email and planner integrations, while offering a personal view of workload across projects and priorities. This arrangement supports agile, iterative work by ensuring tasks are visible, attributable, and traceable without requiring heavy project setup.

The To Do experience aligns with common enterprise delivery rhythms by providing a consistent interface across devices and by enabling synchronization with Microsoft accounts and work accounts where available, ensuring continuity across information radiators.

The core delivery role of Microsoft To Do is to reduce cognitive load for individuals while preserving the ability to scale through team level organization when required. The design supports quick triage, status updates, and fast re-prioritization, which are essential for operational velocity and responsive capability in dynamic environments.

In this context Microsoft To Do becomes a practical entry point for work intake and daily planning, setting the stage for deeper governance and reporting in downstream systems if and when teams mature their use of the tool.

The product is well suited for scenario based usage in which the operational tempo requires rapid capture, quick edits, and reliable reminders, with minimal ceremony that could slow execution.

Delivery role and governance A practical governance pattern for Microsoft To Do involves clear ownership of personal task lists, shared lists for small teams, and a defined process for converting top priorities into actionable work items in broader systems. This structure supports accountability, as items can be tracked to individuals while maintaining flexibility for collaborative lists. In a scaled context, Microsoft To Do complements more formal project management tools by acting as a daily execution layer that feeds into larger planning artifacts. It also supports standardization of task naming, due date conventions, and reminder workflows, enabling predictable handoffs and reduced risk exposure across delivery stages. The integration dimension is central here: To Do can surface items from other platforms and reflect changes back into team workflows, providing a single source of truth for action items in the moment they are created or updated.

Team interactions and collaboration Within teams, Microsoft To Do supports lightweight collaboration by allowing shared task lists, assigned actions, and observable progress markers. The platform facilitates context sharing through comments and subtasks, enabling members to coordinate quickly without leaving the primary work surface. Teams can leverage To Do as a daily standup companion, a sprint planning micro-tool, or a personal task manager that respects boundary conditions between individual and team responsibility. For operational teams, To Do helps preserve visibility into urgent items, enabling quick alignment during morning rituals or shift changes. The ability to filter by priority, due date, or label supports flexible collaboration patterns, ensuring that the most time sensitive or high impact items are surfaced for discussion and action.

Integration patterns and scale As organizations grow, the integration of Microsoft To Do with the broader Microsoft 365 ecosystem becomes critical. Common patterns include feeding actionable tasks from email and calendar into To Do, synchronizing with planner assets for broader project visibility, and exporting completed items for reporting. To Do also serves as a bridge between personal task management and team level execution, enabling governance controls to scale through policy driven usage and data retention rules. In scalable configurations, organizations standardize on shared lists for cross functional work streams, complemented by personal lists that reflect individual commitments. This approach minimizes duplication and preserves a coherent view of work across the organization.

Operational resilience and data integrity The resilience of Microsoft To Do in operational environments lies in its offline capability and reliable sync, ensuring continued access to task data during network interruptions. Data integrity is maintained through consistent state management for task status, reminders, and subtasks, with audit trails accessible via export or integration points in the enterprise. Regular monitoring of integration health and user feedback cycles informs iterative improvements to the To Do experience, helping ensure that the tool remains a dependable surface for day to day delivery. Microsoft To Do remains a practical component of the productivity stack, especially in environments where rapid task capture and timely completion are essential. Category: Project Management. Microsoft To Do supports a straightforward, disciplined approach to personal and small team execution that aligns with operational delivery needs, while offering hooks into more comprehensive governance and reporting as teams mature.

Microsoft To Do and the tools around it

Tools we commonly connect with Microsoft To Do through its API, webhooks and automation platforms. What is possible depends on your plan and setup.

How we can help with Microsoft To Do

Features

5 guides

Integrations

14 guides

Automation

1 guide

Automation for operational excellence

Microsoft To Do has no automation engine of its own -- no rules, no triggers, no if-this-then-that logic inside the app. The real automation surface is Power Automate's Microsoft To Do (Preview) connector, which exposes actions like create a task, update a task, and complete a task, plus a trigger for when a task is created, completed, or modified in a given list.

Delivery model and structure

Because the connector is explicitly marked Preview, flows built on it should be treated as best-effort rather than mission-critical -- Microsoft doesn't guarantee the same SLA as its GA connectors. A typical flow uses the trigger on a specific list, say tasks created via a Forms submission or an email rule, to auto-create a corresponding To Do task, or moves completed-task data into a tracking spreadsheet or Teams channel, since To Do itself has no reporting surface to pull that from directly.

Who it’s for

  • Individuals who want a task auto-created in To Do whenever a specific email arrives or a form is submitted, via Power Automate.
  • Teams wanting completed-task data pushed into a tracking spreadsheet or Teams channel, since To Do has no built-in reporting.
  • Users comfortable with the To Do Power Automate connector being labeled Preview, with the reliability caveats that implies.

Scope and adaptability

Scope here is naturally small: To Do is a personal, per-account task list, not a team task board, so automation mostly means connecting one person's list to email, forms, or another Microsoft 365 app, not orchestrating work across a team, which is what Planner or Project exist for. List sharing, added to To Do a few years back, allows a shared list with real-time sync between collaborators, but every collaborator sees and can edit every task equally -- there's no owner or assignee automation logic built into sharing itself.

Expected outcomes

  • A small number of targeted Power Automate flows connecting To Do to email, forms, or another Microsoft 365 app, scoped to what the Preview connector actually supports.
  • Completed-task and due-date data exported on a schedule, since To Do has no native reporting to pull from.
  • A clear recommendation to move to Planner or Project instead, when the automation need is really team-level coordination rather than a personal list.

Because To Do's automation surface is a single Preview-labeled connector rather than a platform feature, the realistic scope of automation work here is a handful of well-chosen Power Automate flows, not an enterprise workflow engine.

Use cases

  1. Automate weekly status collection by creating tasks in Microsoft To Do from templated forms, with automatic assignment and due dates.
  2. Route incoming requests to appropriate teams using conditional task creation in Microsoft To Do and escalation rules.
  3. Trigger reminders and blockers when dependencies are delayed, visible in real time within Microsoft To Do.
  4. Synchronize issue triage between ticketing systems and Microsoft To Do task lists to preserve context.
  5. Enforce standard task templates in Microsoft To Do to ensure uniform data capture across projects.
  6. Auto-archive completed tasks to maintain a clean Microsoft To Do workspace while preserving history.
  7. Coordinate cross-functional handoffs by linking related tasks across different Microsoft To Do lists.
  8. Automate reminders for upcoming deliverables using calendar-aware logic within Microsoft To Do.
  9. Capture audit-ready task histories that demonstrate process adherence through Microsoft To Do records.
  10. Enable exception-handling workflows that reassign work within Microsoft To Do when owners are unavailable.

Microsoft To Do usage increases as automation matures, ensuring teams rely on a familiar interface for ongoing task execution.

Open the full guide: Automation →

AI capabilities

1 guide

AI-driven augmentation and decision support

Microsoft To Do has no dedicated AI assistant of its own -- there is no Copilot integration built into the To Do app itself, and no model that ranks or rewrites your tasks. The one piece of built-in intelligence is the Suggestions panel inside My Day, which surfaces a shortlist of tasks pulled from your existing lists -- recently completed items, due-soon tasks, and flagged Outlook emails -- using simple recency and due-date heuristics, not a trained recommendation model.

Delivery approach

Because To Do itself has no model-training surface, no custom fields, and no reporting API beyond raw task data, any real “AI for tasks” work has to happen outside the app: pulling tasks and due-date data through the Microsoft Graph /me/todo endpoints, which require a Tasks.Read or Tasks.ReadWrite delegated scope via an Azure AD app registration, and feeding that into an external prioritization model, then writing recommendations back as new tasks or notes rather than expecting To Do to generate them natively.

Who it’s for

  • Individuals and small teams who've outgrown My Day's built-in Suggestions and want prioritization logic tuned to their own workload patterns.
  • Power users who want cross-list workload visibility that To Do's per-list view doesn't natively provide.
  • Teams weighing whether a Graph-API-based custom layer is worth building versus simply using Planner or a dedicated PM tool with richer built-in prioritization.

Adaptation by maturity

For a single user, the honest answer is usually that My Day's native Suggestions and the Important and Planned smart lists cover prioritization needs well enough that a custom layer isn't worth building. Custom Graph-API-based prioritization becomes worth considering only once there's real cross-list or cross-person volume to reason about, and even then the output has to be written back as ordinary To Do tasks, since the app has no concept of an AI-generated insight distinct from a task.

Outcomes

  • A clear-eyed assessment of what My Day's native Suggestions already cover, so nothing is duplicated.
  • A Graph API integration pulling task and due-date data into whatever external prioritization logic is actually needed.
  • Recommendations delivered back as ordinary To Do tasks or notes, since that's the only way To Do surfaces anything to the end user.

Given how little native intelligence To Do actually has, most AI conversations about it end with a recommendation to either lean harder on My Day's existing Suggestions or move the workload to a tool -- Planner, Project, or a third-party PM app -- built for that level of automation in the first place.

Use cases

  1. Recommend next-best actions on a daily plan within Microsoft To Do based on historical completion rates.
  2. Suggest which tasks to defer or accelerate, with justification shown next to each item in Microsoft To Do.
  3. Surface risk indicators for upcoming deadlines inside Microsoft To Do and propose mitigation steps.
  4. Generate AI-assisted task summaries for standups using Microsoft To Do as the source of truth.
  5. Provide capacity and workload signals that inform team allocations directly in Microsoft To Do.
  6. Offer language-aware task descriptions to improve clarity when creating new items in Microsoft To Do.
  7. Assist in resource forecasting by analyzing trends across Microsoft To Do lists.
  8. Highlight dependencies and blockers with AI-enriched context in Microsoft To Do.
  9. Automate scenario planning for sprint planning within Microsoft To Do workflows.
  10. Deliver explainable AI recommendations that can be refined by users in Microsoft To Do.

Microsoft To Do is the natural surface for AI-assisted work planning and decision support.

Open the full guide: AI →

Comparisons

7 guides

Microsoft To Do FAQ

9 questions
Can Microsoft To Do integrate with other apps and automation workflows?

Microsoft To Do supports integration with Microsoft 365 services and can participate in broader automation scenarios through Microsoft Power Automate and other connectors where available.

Practical detail

Use standard connectors to synchronize tasks with calendar apps, email, and project workflows when appropriate. Microsoft To Do participates in automation to streamline task creation and updates.

Actionable considerations

  • Map task creation to triggers in your automation platform.
  • Coordinate updates across related tasks and lists.
  • Test integration scenarios in a controlled environment before broad rollout.
How do I get Microsoft To Do set up for my team?

Microsoft To Do offers a straightforward setup process that integrates with your Microsoft 365 environment. The tool provides a familiar task management interface suitable for individuals or teams.

Practical details

Plan user onboarding, define shared lists, and connect to your existing accounts. Microsoft To Do supports policy-based deployment through your organization’s admin center.

Actionable considerations

  1. Prepare user groups and access levels for Microsoft To Do.
  2. Configure default task lists and collaboration settings.
  3. Communicate onboarding timelines and support channels for Microsoft To Do.
How does Microsoft To Do scale for larger teams or organizations?

Microsoft To Do isn't really an "at scale" tool. It's a personal task list, and it doesn't have organization-wide governance controls, licensing tiers, or admin policies the way Planner, Teams, or SharePoint do. It's free and included with any Microsoft account, personal or work/school, so there's no licensing decision to plan around when someone starts using it.

Practical Details

Multiple people can each use their own To Do independently and share individual lists with each other, but there's no concept of rolling it out to a department with centralized settings or usage reporting. If an organization wants that kind of oversight, Planner or Microsoft Lists is the better fit; To Do stays a lightweight, individual tool even when many employees happen to be using it.

Actionable Considerations

  • Don't plan a formal rollout or licensing budget for To Do, since it's already included with every Microsoft account.
  • Use shared lists for small, informal collaboration rather than expecting department-wide visibility.
  • Move to Planner or Microsoft Lists if you actually need centralized governance or usage reporting.
What AI capabilities does Microsoft To Do offer to help manage tasks?

Microsoft To Do provides task management features that enhance organization, with smart suggestions and prioritization supported by the broader Microsoft 365 ecosystem where applicable.

Practical detail

AI-assisted capabilities focus on organization, reminders, and smart lists to help users stay on top of priorities. Microsoft To Do leverages the underlying platform capabilities to improve task visibility.

Actionable considerations

  1. Encourage users to leverage smart lists for routine tasks.
  2. Combine AI-driven insights with team workflows for better alignment.
  3. Monitor adoption and gather feedback to refine usage patterns.
What data portability options exist for Microsoft To Do data?

Microsoft To Do doesn't have a one-click "export everything" button in the app itself, and that trips people up when they want a backup or want to move to another tool. What you get depends on which kind of Microsoft account backs your lists: with a work or school (Microsoft 365) account, your tasks are actually stored in the same Exchange Tasks infrastructure as classic Outlook Tasks, so they're visible in Outlook's Tasks folder and reachable through the Microsoft Graph API. With a personal Microsoft account, tasks live in a separate consumer backend and aren't exposed through Outlook desktop the same way.

Practical Details

If you need your task data outside the app, the realistic paths are the Microsoft Graph API (the todo and tasks endpoints) for a scripted export, or Outlook's Tasks view if you're on a work/school account. There's no built-in "download my lists as CSV" option in the To Do app's settings, so plan around that rather than expecting it.

Actionable Considerations

  1. Check whether your lists are on a personal or work/school account, since that determines which export path is available.
  2. Use the Microsoft Graph API if you need a scripted or bulk export rather than looking for an in-app export button.
  3. For work accounts, check whether tasks also appear in Outlook's Tasks folder before assuming they're locked in the To Do app.
What engagement outcomes should we expect when adopting Microsoft To Do?

Because Microsoft To Do is a personal task manager rather than a team collaboration platform, "adoption" here mostly means getting someone into the habit of using My Day each morning and trusting the app enough to keep their task list there instead of on sticky notes or in their email inbox. There's no admin dashboard showing who's using it or how often, since it's built for individual use, not organizational rollout.

Practical Details

The features that actually drive habitual use are small: My Day resets every day and nudges you to pick a manageable set of tasks rather than staring at a growing backlog, and flagged Outlook emails and Outlook tasks show up automatically in To Do so people don't have to manually duplicate work between the two. Shared lists work for light coordination, like a two-person household list, but the app isn't built for assigning and tracking work across a team the way Planner is.

Actionable Considerations

  1. Start with My Day rather than the full list view, since a smaller daily view is easier to stick with than an unbounded backlog.
  2. Turn on the Outlook integration if flagged emails or Outlook tasks are already part of someone's workflow, so they don't have to re-enter the same items.
  3. Keep expectations realistic for shared lists, since they suit a handful of collaborators, not team-wide task tracking.
What permissions and access controls are available in Microsoft To Do?

Microsoft To Do's sharing model is much simpler than "role-based access" implies. You can share an individual list with other people by generating an invite link or adding them by email, and once someone joins a shared list, they can see and edit everything in it, since there's no view-only role or per-task permission level. Task lists you don't explicitly share stay private to your account, and there's no separate admin console that sets sharing defaults across an organization.

Practical Details

Sharing happens per list, not per task, so if you want to keep some items private while collaborating on others, you need to split them into separate lists. Anyone you invite to a shared list can add, edit, complete, or delete tasks in it, which is fine for a small group but isn't a substitute for the more granular permission controls in Planner or a dedicated project tool.

Actionable Considerations

  • Split tasks across separate lists if you need to keep some private while sharing others.
  • Remember that anyone on a shared list has full edit rights, not read-only access.
  • Use Planner instead if you need actual role-based permissions or task assignment tracking.
What security measures does Microsoft To Do employ to protect data?

Microsoft To Do provides enterprise-grade security features to help protect user data and workflows across devices, including data encryption in transit and at rest. Microsoft To Do is designed to meet common compliance requirements and integrates with your existing Microsoft 365 security controls.

Implementation considerations

Leverage conditional access and identity protection within Microsoft To Do to safeguard access. Ensure appropriate role-based access and policy enforcement across user groups when deploying Microsoft To Do at scale.

Actionable considerations

  • Assess data classification and retention policies for tasks and lists in Microsoft To Do.
  • Enable multi-factor authentication for all users.
  • Review sharing permissions to control collaboration in Microsoft To Do.
What support options are available if I encounter issues with Microsoft To Do?

Support for Microsoft To Do runs through the same channels as the rest of your Microsoft account, the Microsoft Support site, the Microsoft Tech Community forums, and in-app feedback, rather than a dedicated support line just for the app. There's no separate enterprise support tier specific to To Do; work/school account issues typically get folded into whatever Microsoft 365 support arrangement your organization already has.

Practical Details

Most real-world issues are sync related: tasks not appearing on another device, a flagged Outlook email not showing up in the linked list, or a Planner task assigned to you not surfacing in the "Assigned to you" list. Signing out and back in, or checking that the same Microsoft account is used across devices, resolves a good share of these before you need to dig further.

Actionable Considerations

  • Confirm you're signed into the same Microsoft account on every device before assuming something is broken.
  • Check the Outlook and Planner integration settings specifically if synced tasks aren't appearing.
  • Use the Microsoft Tech Community forums or Microsoft Support site for issues beyond basic sync troubleshooting.

Get more from Microsoft To Do

Whether you're rolling it out for the first time or fixing a setup that never quite worked, Consultants in a Box can help.

Book a free consultation

Tell us about your team and the software you need help with. We'll follow up to schedule a time to talk.

Open the form on its own page

Talk to a person

The fastest way is to pick a time. Prefer to write? Leave a message and we will email you back, usually the same business day.

Book a free call

By sending this you agree to our Terms and Privacy Policy.