Microsoft is unlocking the "Full Potential" of Private Channels in Microsoft Teams: What You Need to Know

on
It has been a while since I posted something just about a Microsoft Teams update, as a lot have been Copilot in Teams to be honest. But here is a real Microsoft Teams update I think is worth knowing about, and it involves Security and Compliance as well. Microsoft is rolling out a "major" update to private channels in Teams, starting in late September 2025 and continuing through mid-December. This biggest change in this update is a shift in how private channel data is stored from individual user mailboxes to a dedicated channel mailbox. Not only will this simplifie compliance management, it will also and align private channels with shared channels, making governance and experience more consistent across Teams. This update promises to increase the support up to 1000 channels per team and 5000 members per channel, removing previous limitations. Teams will also allow meetings to be scheduled directly within private channels, enhancing collaboration.  For organizations using Micr...

Copilot in Teams will be available for multitenant organizations (B2B)

on
Microsoft has announced that Copilot will be accessible to Business-to-Business (B2B) members within Multi-Tenant Organizations (MTO). This update allows users with B2B (shadow) identities to utilize Copilot during Teams meetings, provided they have a license in their host tenant. This will help organizations boost collaboration and productivity when working with different organizations.

There will be a new policy setting in the Teams Admin Center (TAC) enabling IT administrators to manage and control Copilot access specifically for B2B members.

According to the Roadmap ID 423474, we can expect this feature to be rolling to the first customers at the end of this month. Keep an eye out on the messeage center, and in the Teams Admin Center for these changes. 

I know a lot of users and customers are asking for this feature, but organizations should make sure such access is aligned with their own security and access policies. And users should be informed that when the feature is released, some organizations might not turn it on.