A Microsoft Teams channel still holds the same messages. What changes is the layout: how those messages sit on screen. Microsoft calls that Posts (classic) and Threads (chat-like). It is not a new channel type and not a separate store. Same channel, different view — for everyone in that channel at once.
Posts layout
Classic channel behaviour. Someone starts a post (often with a subject). Replies hang underneath. A busy post pushes the rest of the channel down; you scroll through whole conversations. The tab at the top says Posts. Moderation (who may start a new conversation vs. reply only) is strongest here. Fits announcements, a notice board, “one topic = one post”.
Threads layout
Closer to a group chat, with the durability of a channel (files, tabs, ownership). The main stream stays readable: replies live in a thread and open in the right pane. The tab says Conversation. You follow threads that matter; unread stays small. Fits a project channel where back-and-forth is the work, not a weekly notice.
When to use which
- Posts — announcements, HR, “owners post only”, long pieces with a subject, a quality channel you must find again later.
- Threads — day-to-day work, a project, a support channel, teams that currently live in group chats because Posts felt messy.
New channels default to Threads (for new teams that has been the first-channel default since 2026). Existing channels stay Posts until an owner switches. Switching does not drop messages; guests or an old Teams client sometimes see Threads as Posts, and order can look wrong. Put that channel back to Posts until everyone is on a current client.
Change it in the app
Team or channel owner only. Three dots on the channel → Edit channel (or Manage channel → Edit) → Conversation layout → Threads or Posts → Save. The choice is for the whole channel, not per user. Chats do not have this switch.
Policy and bulk change: see the guide Change channel layout with PowerShell. MicrosoftTeams module: release notes.
Frequent errors and how to fix them
These are the messages people type into search when the module will not start. The exact wording is here so this page can be found.
The term 'Connect-MicrosoftTeams' is not recognized- MicrosoftTeams module missing. Install-Module MicrosoftTeams; new window; Import-Module MicrosoftTeams.
AADSTS / consent / MFA- Teams cmdlets need a Teams admin role, or app-only with the right Graph/Skype permissions.
Assembly / version conflict- Multiple MicrosoftTeams versions. Uninstall-Module MicrosoftTeams -AllVersions, then install one current version.
A parameter cannot be found that matches parameter name 'ThreadedChannelCreation'- MicrosoftTeams module too old. 7.1 or later in PowerShell 7. Cmdlet is Set-CsTeamsChannelsPolicy (Channels, plural).
layoutType / Invalid request- Graph scope ChannelSettings.ReadWrite.All missing, or the client does not expose layoutType yet. PATCH with Invoke-MgGraphRequest.
Questions about this, or need help setting it up? We are happy to think along.
Message on LinkedIn →