Microsoft Teams: Threads will become the default layout for new channels created with Microsoft Graph
Rollout dates
- Standard release (GA):
Extracted from the announcement text; the Microsoft text is authoritative.
Microsoft announcement
[What and why]
We're updating the default message layout for new Microsoft Teams channels created through the Microsoft Graph v1.0 Create channel API (POST /v1.0/teams/{team-id}/channels). When a channel creation request doesn't specify the layoutType property, the new channel will use the Threads layout instead of the Posts layout.
This change applies only to newly created channels. Existing channels won't change.
[Rollout schedule]
- General Availability (Worldwide, GCC, GCC High, DoD): Beginning in late November 2026 and expected to complete by late November 2026
[Impact on your organization]
Who is affected
- Organizations with applications, scripts, or automated provisioning workflows that create Microsoft Teams channels through Microsoft Graph without specifying the
layoutTypeproperty
Platforms and services
- Microsoft Teams and Microsoft Graph v1.0 Create channel API
What will happen
- If
layoutTypeis omitted, new channels will use the Threads layout instead of the Posts layout. - If
"layoutType": "post"is specified, new channels will use the Posts layout. - If
"layoutType": "chat"is specified, new channels will use the Threads layout. - The API value for the Threads layout is
"chat", not"threads". - Existing channels won't change.
- Channel creation requests that explicitly specify a supported layout aren't affected.
[Action required and recommendations]
- Notify developers and owners of applications or automation that create Teams channels through Microsoft Graph.
- If your organization requires new channels to continue using the Posts layout, update channel creation requests to explicitly include
"layoutType": "post"before rollout begins. - For third-party solutions, contact the provider to confirm how the solution specifies the channel layout.
- If Threads is your desired layout, no request changes are required to adopt the new default.
- Review and test dependent workflows for compatibility with Threads.
Learn more
[Compliance considerations]
No compliance considerations identified. Review as appropriate for your organization.
Change history
- 2026-10-30 · Created · All