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

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...

New Microsoft Loop workspace policy coming: Require Existing Microsoft 365 Group for New Loop workspaces

Microsoft is improving the security of Loop workspaces by giving admins the capability to connect new workspaces into existing Microsoft 365 Groups. This change will allow end-users to choose existing groups for managing new workspaces, providing a structured environment for collaboration. While this integration supports governance, it may challenge scenarios like automatic aggregation of Teams meeting content into a Loop workspace or creating short-term project workspaces. I recommend reading the following post on how aggregating teams meeting into loop workspaces works.

If organizations have separate workflows for creating and govern Microsoft 365 groups, now would be the time to look into them and see if they need to be updated to include Loop Workspaces (or allowing to add workspaces)

This update is currently planned to be complete by the end of April 2025 but keep an eye on Microsoft 365 Roadmap ID 422725 for changes.