Skip to content

Microsoft To Do: Simple Lists With Microsoft Sync

Microsoft To Do: Simple Lists With Microsoft Sync

Microsoft To Do Android review: no native calendar view, uncertain shared-list assignment across Microsoft accounts, and recurring-task history gaps.

App summary

App
Microsoft To Do
Developer
Microsoft Corporation
License
Proprietary
Version
unknown
Size
unknown
Price
Free

A Free, Proprietary Task List That Lives Inside a Microsoft Account

Microsoft To Do is published by Microsoft Corporation. It is proprietary software, it costs nothing, and it runs on Android. Those four facts frame everything else in this review, and they are worth stating plainly, because plenty of task apps are neither free nor bound to a single vendor’s account system.

What the app does, according to the supplied facts, is manage lists. Tasks live inside lists. Tasks carry reminders and due dates. There is a daily planning surface called My Day. Subtasks, attachments, and shared lists are part of the package. Sync runs through a Microsoft account, and the app connects to Microsoft 365 and Outlook. That is the documented surface, and it is narrower than the marketing around most productivity software would lead you to expect. Nothing in the fact data mentions boards, timelines, dependencies, time tracking, or reporting.

The proprietary license has practical consequences. You cannot inspect the code, you cannot self-host the backend, and you cannot extend the data model. What Microsoft ships is what you get. For a free app that is a reasonable trade for most individuals, but it does put a hard ceiling on customization, and that ceiling is low.

Because the app is free, the obvious question is what pays for it. The fact data does not answer that. It lists Microsoft 365 and Outlook integration as functions and names the Microsoft account as the sync mechanism, but it does not document which parts of the experience depend on a paid Microsoft 365 subscription and which do not. Treat that boundary as unknown until you verify it against your own account. The same caution applies to migration: the fact data documents no path for importing lists from any other service, so how you would move existing tasks in is not something this review can tell you.

Lists, Tasks, Reminders, and Due Dates: The Working Parts

The unit of work is a task inside a list. Reminders and due dates appear as separate named functions in the fact data, which suggests they are distinct concepts rather than two labels for the same field, though the data does not spell out how each one behaves in practice. A list, in this model, is a container. It is not a project, not a board, and not a workspace with its own permissions model beyond the sharing behavior covered below.

What is missing matters as much as what is present. The fact data does not list tags, labels, or custom task statuses among the app’s functions. If you are coming from a task manager that lets you slice work by context, energy level, or client, you will not find that vocabulary here. Lists are the only grouping mechanism the facts describe, and a task belongs to a list.

Due dates are metadata, not scheduling. A due date records when something is owed; it does not reserve time on a calendar, and it does not tell you whether you have room to do the work that day. That distinction sounds pedantic until you have a list of forty tasks all due Friday and no view that shows you the collision. This is the setup for the app’s biggest structural limitation, which the next section covers directly.

Microsoft To Do on Android Has No Native Calendar View: Due Dates, Reminders, and My Day Are Not a Schedule

The fact data confirms that Microsoft To Do handles lists, tasks, reminders, due dates, and My Day daily planning on Android. It does not list a calendar view among the app’s functions. That absence is the gap, and it is a meaningful one: a task with a due date is a record of an obligation, not a block of time on a grid. You can see what is due. You cannot see how the day is shaped.

My Day is the feature most often mistaken for a calendar, and it is not one. My Day is a daily focus list — a short, curated set of items you intend to work on today. A calendar view would show you the week, the overlaps, and the empty slots. A focus list shows you a commitment you made to yourself this morning. Those are different tools that solve different problems, and conflating them leads people to expect a schedule the app was never built to draw.

Google Calendar sync is not established by the fact data. It would be wrong to assume the app is Outlook-only, and equally wrong to assume it supports Google. The honest position is that the fact data is silent, so the answer is unknown and needs to be verified before you build a workflow around it. The related assumption — that every task with a due date automatically appears in the Outlook calendar — is also not supported by anything in the facts. Integration with Outlook is listed as a function; the specific mechanics of what crosses over and what does not are not documented.

Practically, this means the app is a poor fit if your working method depends on time-blocking. If you plan your week by looking at a grid and dragging work into open hours, Microsoft To Do will not give you that surface. It will tell you what you owe and when it is owed. Turning that into a schedule is a separate step you perform somewhere else.

My Day and the Practice of Daily Planning: A Focus List That Starts Fresh

My Day is the app’s answer to the problem of a list that has grown too long to act on. Instead of working from the full backlog, you assemble a smaller set of items for today and work from that. The fact data names this as a core function and describes it as daily planning, which is the right way to read it: a ritual, not a report.

One reader question the fact data cannot settle is whether My Day resets every morning and whether unfinished tasks stay there or fall back to their lists. The data does not document reset behavior or carry-over rules. If that detail matters to your routine — and for some people it matters a great deal — you will have to observe it on your own account rather than take a promise from this article.

What can be said with confidence is that a focus list only works if you curate it. A daily planning surface that you fill by dumping everything into it becomes a second backlog, and the value disappears. The feature’s usefulness depends on the discipline of the person using it, which is true of most planning tools but especially true of one with no calendar to fall back on.

Shared Lists in Microsoft To Do: Assignment Is Not Guaranteed Across Personal and Work Microsoft Accounts

Shared lists are part of the fact data’s core function set. That much is clear: lists can be shared, which makes the app usable for households, small groups, and lightweight coordination without anyone buying a project management license. Sharing is the feature that pulls Microsoft To Do out of the solo-productivity category.

What the fact data does not specify is whether task assignment behaves identically on personal Microsoft accounts and on work Microsoft accounts. That behavior must be marked unknown and tested on the specific account type you intend to use. It is entirely possible for a shared list to be visible to everyone and still not offer the same assignment controls across account boundaries, and nothing in the supplied facts rules that out.

This is where a common misconception does real damage. People assume that because a list is shared, every participant can be assigned tasks with the same fidelity. Sharing a container and assigning work inside it are two different capabilities, and the fact data only confirms the first. If your plan depends on handing specific items to specific people and seeing who owns what, verify it before you move a team onto the app.

The question of whether you can assign tasks in a shared list without a Microsoft 365 subscription is likewise unanswered by the fact data. It lists Microsoft 365 integration as a function but does not map features to subscription tiers. Assume nothing about the free tier’s sharing limits until you check.

Recurring Tasks in Microsoft To Do: Completed History and Missed Occurrences Are an Undocumented Gap

The fact data confirms due dates and reminders. It does not document recurring-task completion history, and it does not describe how missed occurrences are handled. It does not even establish, in explicit terms, how recurrence itself is configured. The reader question about completed recurring tasks disappearing is therefore one this review cannot answer from the supplied facts. The behavior is unknown.

That is an unsatisfying answer, but it is the accurate one. A recurring task is a small piece of state machinery: the app has to decide what happens when you check off one occurrence, whether the next one is generated immediately or on schedule, and what becomes of the occurrence you skipped. None of that is described. Anyone who tells you the app keeps a clean audit trail of every completed recurrence is going beyond what the documentation supports.

For most personal use this does not matter. You check the box, the next one appears, and you move on. It starts to matter when the task list doubles as a record — medication logs, maintenance schedules, compliance checklists, anything where you might later need to prove that something was done on a given date. If that is your use case, do not assume the app is storing history for you. Keep your own record, or verify the behavior carefully before you depend on it.

Subtasks and Attachments: Structure Without a Task Database

Subtasks and attachments are both listed functions. Subtasks let a task contain smaller tasks, which is enough structure to break a chore into steps without leaving the list. Attachments let a file travel with a task, which is useful when the thing you owe is a document rather than an action. The fact data does not specify how deep subtask nesting goes, what file types attachments accept, or what storage limits apply.

What the app is not, based on the facts, is a task database. There are no custom fields, no saved filters, and no automation described. Power users who build systems out of tags, queries, and rules will find the model too flat. Lists and subtasks are the only hierarchy the fact data describes, and there is no way to define your own attributes on top of it.

Encryption is another area where the fact data is silent. It says nothing about end-to-end encrypted notes or lists, which is not the same as saying the app lacks encryption — only that the supplied facts do not document it. If confidential task notes are a requirement, this is not the app to stake that requirement on without independent verification.

Sync and the Microsoft Account: What It Buys, and What Stays Unverified

Sync is a named function, and the fact data frames it around the Microsoft account. That framing tells you something important about the product’s center of gravity: the account is the identity, and the task data hangs off it. Sign in with a Microsoft account and your lists follow you; that is the model the facts describe.

Offline behavior on Android is not documented. The fact data does not say whether the app queues changes made without a connection and reconciles them later, or how conflicts are resolved when two devices edit the same task. For a task app used on a phone, offline handling is not a corner case — it is the normal condition on trains, planes, and bad hotel Wi-Fi. Test it before you rely on it in a place with no signal.

Recovery is another undocumented area. The reader question about recovering a deleted list or task after emptying the deleted items cannot be answered from the fact data, which describes no retention window and no restore mechanism. Treat deletion as final until you have evidence otherwise, and do not treat the app as a backup of anything you cannot afford to lose.

The fact data lists Android as the platform. It does not document other clients, so this review makes no claims about how the app behaves anywhere else. What matters for Android users is the account tie: your lists live in Microsoft’s service, not on the device, and the account is the thing you are really signing up for.

Microsoft 365 and Outlook: Integration Without a Calendar Guarantee

Integration with Microsoft 365 and Outlook is listed as a function. What that integration consists of, concretely, is not documented beyond the name. The fact data does not enumerate which Microsoft 365 surfaces the app touches, what data flows in which direction, or which parts require a subscription.

The frequently asked question about flagged Outlook emails becoming tasks is a good example of where the facts run out. The integration is real enough to be listed, but the specific mechanics — whether flagging an email creates a task automatically, whether it requires a desktop client, whether the task carries the message body — are not described. Do not build a workflow on an assumed version of that feature.

One misconception worth correcting directly: nothing in the fact data supports the idea that all Microsoft To Do tasks automatically appear in the Outlook calendar. Integration is listed; automatic calendar publication is not. If seeing your tasks on a calendar is a requirement, that is a gap to solve outside this app, not a feature to expect inside it.

The account boundary also deserves attention here. The fact data does not distinguish between personal Microsoft accounts and work accounts when describing Microsoft 365 and Outlook integration. Behavior that works on one may not work on the other, and the only responsible advice is to test with the account type you actually use.

Microsoft To Do Is Not Microsoft Planner: Skip It for Android Teams Needing Kanban, Dependencies, or Workload Planning

The fact data positions Microsoft To Do around lists, tasks, reminders, due dates, My Day, subtasks, attachments, shared lists, sync, and Microsoft 365 and Outlook integration. Read that list carefully. Every item is about individual work items and the containers that hold them. There is nothing about visualizing a workflow, sequencing work, or balancing load across people.

Specifically absent: Kanban boards, Gantt charts, task dependencies, time tracking, and workload planning. None of these appear in the fact data as functions of the app. A shared list is not a board. A subtask is not a dependency. Checking a box is not a status transition through a defined workflow. Teams that need those things are looking at the wrong product.

Microsoft Planner is a separate entity in this landscape, and the two should not be conflated. If your team needs to see work moving across columns, understand what blocks what, or see who is overloaded, Microsoft To Do will not answer those questions no matter how carefully you structure your lists. Managers who need workload balancing and detailed team reporting should look elsewhere from the start rather than discovering the limitation after a migration.

Verdict

Microsoft To Do is a free, proprietary Android task-list app from Microsoft Corporation, and it is good at a specific job: keeping lists of tasks with reminders and due dates, planning a daily focus set through My Day, breaking work into subtasks, attaching files, and sharing lists with other people who also live in the Microsoft account ecosystem. If you are an individual with a Microsoft account who wants a clean place to record what you owe and when, the app covers that ground without asking for money.

It is not for you if any of the following describe your needs. Teams that need Kanban boards, task dependencies, or Gantt-style planning should not treat this as a project tool. Anyone who wants native Google Tasks and Google Calendar synchronization is outside the documented scope, and the Google Calendar question is unanswered by the facts rather than answered favorably. People who require end-to-end encrypted notes and lists have no documented guarantee here. Freelancers who need built-in time tracking, billing, or client invoicing will not find those functions. Power users who need tags, saved filters, custom fields, and task automation will find the data model too flat. Managers who need workload balancing and detailed team reporting are in the wrong product entirely.

The honest summary is that the app’s limits are structural, not cosmetic. No calendar view means due dates never become a schedule. Undocumented assignment behavior across account types means shared lists are a coordination tool, not a delegation system. Undocumented recurrence history means the app is not a record of what was done. And the absence of boards, dependencies, and reporting means it is not a Planner replacement, whatever the shared Microsoft branding suggests.

If you want to try it, install it from Google Play, which is the official source for Android. Then test the things this review could not verify — offline sync, My Day’s reset behavior, shared-list assignment on your account type, and how recurrence handles completion — against your own workflow before you commit. The fact data leaves those questions open, and open questions are worth answering with evidence rather than assumption.

Pros

  • Free to use
  • Cross-device sync via a Microsoft account
  • Integrates with Outlook and Microsoft 365

Cons

  • Requires a Microsoft account
  • Proprietary and closed source
  • Some advanced features depend on the Microsoft ecosystem
Download from the official source

The link goes straight to Microsoft Corporation. We do not host app files.

Open official page →

Frequently asked questions

Is Microsoft To Do free?

The recorded pricing model is Free.

What license does it use?

It is listed under Proprietary.

Where can I download the official version?

The official link points to https://to-do.office.com/.

This article was drafted with AI assistance using official developer documentation, release notes, privacy policies, and public data, then reviewed by an editor. We do not claim lab testing. The full method is on our Review Method page.