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

A few examples from get-userandpolicy

on
A couple of days ago I released the get-userandpolicy script, and I thought I give a few examples of how it can be used.

It's not a very complicated script, but it gave me an output I could not get in a simple way from the Lync server CSCP.

Example 1)
Q - How many policies do I have of a certain type?
A - Get-Cs........Policy will give you an answer, or use my script with a named switch to identify the number. No need to remember all the different policies, just TAB (auto complete) your way through the valid options.



Example 2) 
Q - How many policies do I have, and how many users are assigned to each policy
A - Not so easily identified through CSCP, possible with filters in powershell, or use the script in the following way.


Example 3)
Q - Now that I know how many policies I have, and what they are called, how do know which users have been assigned to these policies?
A - Simple, memorize the different powershell commands, or run the script with the -listuser switch. Then use the powerful filters of gridview to identify whatever user/policy combination you seek.