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

Issue with enable-csuer when the user first name contain spaces

on
I have run into an issue with the set-csuser command in a few deployments. The error occurs when I try to use set-csuser with the "-sipaddresstype firstlastname" switch.


If I changed the -sipaddresstype from "firstlastname" to "emailaddress", I was able to use the script to enable the same user.

It turned out this user had two first names (with a space between) in the fname property in AD (fname="First Name"). If I removed one of them (fname="First"), or used a hyphen between them (fname="First-Name"), the script started working again.