Updated December 12, 2025: We have added additional content clarifying who is impacted by this feature. Thank you for your patience.
[Introduction]
Teams users in tenants with open collaboration policies have long been able to start a chat with anyone who has an email address. However, recipients without a Teams account were previously asked to sign up for one before being able to collaborate. We're introducing a new capability in Microsoft Teams for certain tenants (see ‘Who is affected’ below) that allows these recipients to join the chat as a guest— no account needed, and as long as it is allowed by the tenant’s existing policy configuration.
This feature will be available across Windows, Mac, Web, iOS, and Android platforms.
This message is associated with Microsoft 365 Roadmap ID 513271.
[When this will happen:]
- Targeted Release: Rollout for users with the aforementioned licenses begun in early November 2025 and was completed in mid-November 2025
- General Availability (Worldwide): February 2026
[How this affects your organization:]
Who is affected:
This capability is currently available only to small and medium business customers enrolled in public preview with a Teams Essentials, Business Basic, Business Standard, or Business Premium license. It also only affects organizations with guest chat enabled and that do not limit guest collaboration to specific domains. Organizations without users enrolled in public preview or without users with these licenses may still see this post even if they are not affected.
What will happen for those who are affected:
- After Teams users start a chat with someone who is not on Teams, the recipient will receive an email inviting them to join the chat as a guest. Only Teams users in your organization can start the chat, as users without Teams accounts cannot initiate chats.
- Chats will remain within your organization’s boundary.
- This feature is enabled by default but will be governed by your organization’s Entra B2B Guest policies and Teams Admin Center Guest Access policies. It will not override any existing policy configurations.
[What you can do to prepare:]
- Update internal documentation to reflect this new capability.
- Inform helpdesk and support teams about the change.
- Review the documentation here: Chat with anyone not using Teams - Microsoft Teams | Microsoft Learn
- To disable the feature, set the UseB2BInvitesToAddExternalUsers attribute of TeamsMessagingPolicy to false. Set-CsTeamsMessagingPolicy documentation here.
[Compliance considerations:]
No compliance considerations identified, review as appropriate for your organization.