How Teams channels work inside projects

Once Teams is connected (see "Microsoft 365: SharePoint, Teams, and Calendar" for that setup), each project can mirror its conversation into a real Teams channel. This article is about how that mapping behaves day to day — what posts automatically, whether replies come back, and how attribution works for partners.

A project manager or admin opens the project and maps it from the Teams channel panel. Current lists the Teams you've joined and their channels — pick a team, then a channel, and save. This uses your own Microsoft connection, so if you haven't connected yet, the panel points you to Settings first.

1. 1
   Open the project

   The Teams channel panel appears on the project detail page for anyone who can manage projects.
2. 2
   Click Map to Teams

   Current calls Microsoft to list the Teams and channels your account belongs to.
3. 3
   Pick a team, then a channel

   The channel list depends on which team you selected.
4. 4
   Save the mapping

   New comments on this project now mirror to that channel. You can change the channel or unmap it later from the same panel.

Two kinds of messages reach a mapped channel. Comments you or your team write on the project post there, attributed with your name. Separately, project alerts — a task getting assigned, a task becoming unblocked, a health score dropping, and similar events — can also post to the channel if you've turned Teams on in your notification preferences.

Teams isn't a one-way broadcast. Current periodically checks each mapped channel for new messages and replies, and anything your team writes there — including replies buried in a thread — lands back in the project's comment history in Current. The first time a channel is mapped, Current only starts watching from that point forward, so you won't get flooded with the channel's older history.

Partners (external clients using the read-only portal) don't have a Microsoft connection of their own, so their co-managed comments can't post to Teams directly. When a partner adds a comment that's visible to your team, Current posts it to the mapped channel under a connected staff member's identity, with the message clearly labeled with the partner's name followed by "(partner)" so your team always knows the comment came from the client, not from a teammate.

Any mapped project can turn on a morning standup post — a short automatic summary posted to the channel on weekday mornings (8:30am ET) listing what was finished yesterday, what's due today, and what's overdue, along with the project's health indicator. It's off by default and is a per-project switch, right next to the channel mapping — there's no workspace-wide standup setting.

If Current can't list your Teams and channels automatically, the panel switches to manual entry: two plain text fields for Team ID and Channel ID. In Teams, open the channel, use "Get link to channel," and paste the IDs from that link.

• ＋An empty or failing picker is almost always a missing Channel.ReadBasic.All permission on the Microsoft 365 app registration — see "Microsoft 365: SharePoint, Teams, and Calendar" for the full permission list.
• ＋Reconnecting your Microsoft account in Settings can also resolve a stale or expired connection.
• ＋The manual Team ID / Channel ID fields work regardless of that permission, so mapping never has to be blocked entirely.