A task’s comments and its Microsoft Teams thread are two ends of the same conversation. Comments you write in AB always post to the thread, and any reply in the thread comes back to the task — no @mention needed, once your team is on AB Projects 2.4.0 or later. A comment by itself still notifies no one: people are pinged only when you pick them in the mention picker.
Mentions are opt-in, per comment. Below the comment editor sits the Mention in Teams notification picker — a row of member chips. Only the members you select are @mentioned in the Teams channel post and get Teams’ native notification. No chips selected means no pings.
Write a comment and mention people
- Open the task and go to its Comments section.
- Write the comment in the rich-text editor — formatting and image upload are supported.
- Pick who to notify. In the Mention in Teams notification row, click a member’s chip to select them; click again to deselect. Only members with a Teams identity in this project appear (someone who can’t be @mentioned in Teams isn’t listed).
- Post. The comment is saved on the task and posted to the linked channel, with your selected members @mentioned in the Teams message.
How the sync works
- Every comment posts to the linked channel, not just the first one. The first comment on a task starts a thread with an Adaptive Card (an interactive message card in Teams) showing the task details; each later comment is a reply in that same thread. See Adaptive Cards and Task Previews.
- Every reply in the task’s thread syncs back. Reply under the task’s card the way you’d reply to anything in Teams, and the reply is added to the task as a comment. You don’t need to @mention anyone, and @mentioning colleagues in the reply doesn’t stop it syncing.
- In a task’s thread, a reply is always a comment. A reply that @mentions AB Projects is filed on the task too, with the mention removed, and the bot doesn’t answer it. To ask the bot a question or give it a command, start a new post in the channel and @mention AB Projects there.
- Unregistered repliers are still captured. If the replier isn’t an AB Projects user yet, the comment is saved with a “(Teams)” label on their name, and the bot invites them to register so future comments link to their profile.
- Viewer replies stay in the channel. Replies from members with the read-only Viewer role are not copied into the task’s comment history — they can chat in the channel, but the audited task record only takes comments from members who can edit. See Role-Based Access Control.
Replied in the thread but it’s not on the task? Your team is probably still on an AB Projects version older than 2.4.0. Version 2.4.0 added a permission (Microsoft calls it resource-specific consent: access granted to the app for this one team only) that lets AB Projects read replies in the team’s channels, and Microsoft Teams asks a team owner to accept it before it takes effect. Until then, Teams only passes the bot messages that @mention it, so a reply syncs only when it includes
@AB Projects. Ask a team owner to accept the AB Projects update for the team. Comments added on the task itself always reach both places either way.Comments not appearing in Teams at all? A project owner may have switched off New comments channel posts for the project — see the notification settings in Notifications and Reminders.
Quick reference
| Where you write | Where it ends up | Who gets notified |
|---|---|---|
| Task comment, chips selected | Task and the Teams thread | Selected members, via a real Teams @mention |
| Task comment, no chips | Task and the Teams thread | No one directly (the post is still visible in the channel) |
| Reply in the task’s thread (2.4.0 or later) | The thread and the task’s comments | Whoever Teams itself notifies for thread replies |
| Reply in the task’s thread, team on an older version | The thread and the task only if it @mentions AB Projects; otherwise the thread only | Whoever Teams itself notifies |
Best practices
- Mention only the people who need to act or weigh in — each chip is a real Teams notification.
- Keep the discussion in the task’s thread or on the task rather than in new channel posts, so nothing detaches from the work record. A new post in the channel isn’t a reply to a task, so it isn’t synced.
- Glance at your selected chips before posting; it’s the difference between a useful ping and noise.
Comment where it’s convenient — the task and its Teams thread stay one conversation, and only the people you choose get pinged.