Planner comments referenced in notifications not visible in the associated task

Andreu Carro 0 Reputation points
2026-09-04T10:27:36.25+00:00

Users receive an email notification indicating that they have been mentioned in a Planner task comment. However, after opening the notification and navigating to the corresponding Planner task, the most recent comment referenced in the notification is often not visible in the task's comments/conversation section.

Expected behavior:

  • Users receive a mention notification.
  • Opening the Planner task displays the latest comment that triggered the notification.

Actual behavior:

  • The notification email is received correctly.
  • When the task is opened, the latest comment is missing from the comments thread.
  • Users cannot locate the comment that generated the notification, even after reviewing the task conversation history.
  • The issue occurs intermittently but affects most colleagues sooner or later.

Business impact: This issue has a significant operational impact. Our team consists of approximately 40 colleagues who actively collaborate through Microsoft Planner, which is a critical tool used to manage internal workflows, coordinate activities, track deliverables, and monitor progress across multiple internal subprocesses.

Reliable visibility of task comments and mentions is essential for day-to-day coordination. When users receive notifications for comments that are not visible within the task, important information, decisions, requests, and action items may be missed. This creates confusion, increases the need for manual follow-up, and reduces confidence in Planner as the source of truth for task-related discussions.

Based on the reports received and my own experience, this does not appear to be an isolated user issue. It affects multiple users across the team and occurs with varying frequency. We would appreciate an investigation into the root cause and any available mitigation or resolution.

Microsoft Teams | Microsoft Teams for business | Tasks | Manage tasks
0 comments No comments

1 answer

Sort by: Oldest
  1. Ana Le 2,345 Reputation points Independent Advisor
    2026-09-04T10:50:49.71+00:00

    Hello,

    Please confirm whether the affected plan is a Basic or Premium plan and whether users open the task in Planner for the web, Teams desktop/web, or a mobile app. Microsoft documents different conversation experiences depending on the plan type.

    For Basic plans using Task chat, Microsoft states that:

    • Users explicitly mentioned in a message receive an email and a Teams notification.
    • Anyone who can open the task can view its chat.
    • The message author can edit or delete the message.
    • Task chat does not move with a task if the task is moved to another plan.

    Please test one affected example:

    1. Open the exact task directly in Planner for the web⁠.
    2. Compare the same task in Planner within Teams desktop or Teams web.
    3. Ask both the message author and the mentioned user to check the task.
    4. Confirm whether the message was edited or deleted after the notification was sent.
    5. Confirm whether the task was moved to another plan.
    6. Note whether the issue occurs only in a particular application or device type.

    Microsoft documents the current behavior here: Comment on tasks in Microsoft Planner⁠.

    If the message remains missing for both users in Planner for the web and Teams desktop/web, please have a Microsoft 365 administrator open a support request under Support > New service request so Microsoft can investigate the affected tenant.

    Include the plan and task link, exact UTC time, notification email, affected applications, and screenshots showing that the notification was received but the associated message is not visible. Please do not post users’ email addresses or other account information publicly.

    Get support for Microsoft 365 business

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.