Tracking, updating, and organizing tasks within Microsoft Teams or integrated apps
Planner task comments are stored and surfaced through Microsoft 365 Groups and Exchange Online. For Basic plans, comments behave as follows:
- Comments are written in Planner but actually stored as a conversation in the plan’s Microsoft 365 Group mailbox (Exchange Online).
- The desktop Outlook notification email is just a copy of that conversation; it does not control or guarantee Planner UI refresh.
- Comments are reliably visible and up to date in the web Planner experience; if the desktop client is not showing the latest state, use the web view as the source of truth.
There are also known limitations that can affect visibility of comments:
- If comments are pasted from email including “From:” and “Sent:” fields, anything from those fields onward may not appear when the task is reopened. Remove those fields before posting, or attach the email instead.
- If the organization is not using Exchange Online for the account, commenting may not work correctly.
- Comments cannot be added to tasks in plans created by Connected Yammer Groups.
- If a comment thread is “forked” (for example, someone replies directly to the group email instead of using the Planner task, or there are more than 100 comments), not all comments will load in Planner.
Given that comments are visible and correct on the web but not updating as expected in the desktop experience, the supported guidance is:
- Use the Planner web app as the authoritative view for task comments.
- Ensure comments are added directly in Planner (or via the group conversation) without including “From:”/“Sent:” blocks from emails.
- Confirm that the plan is a standard Basic plan backed by a Microsoft 365 Group using Exchange Online, not a Connected Yammer Group.
- If threads are very long (approaching or over 100 comments) or heavily email‑replied, expect possible partial loading and consider starting a new task for continued discussion.
If all of the above conditions are met and the issue persists for the whole team only in the desktop experience, escalation through the organization’s Microsoft 365 support channel is recommended, as the behavior is not configurable from the Planner side.
References: