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

More OCS challenges

on
Ok, So I have the basics up and running, but is it working? Aperantly, yes.
Front end and backend now run without errormessages, and I can chat, call and use livemeeting on all the clients.

I decided not spend to much time on running around, installing applications, so I am using AD Group policies to deploy the applications. Here is a quick rundown of what I did:

Livemeeting:
  • Download software from www.livemeeting.com (Remember to download both client and outlook plugin)
  • Convert exe files to .msi files by running "LMsetup.exe -out c:\temp" (presuming c:\temp exists)
  • Create a GPO for distribution (Assign or publish, Computer or User - It depends on your preference)
  • Create Groups for filtering of the GPO
  • Add objects to the groups
  • Remove "authenticated users" from the filtering, add the desired group.
Attendant:
The attendant setup file I downloaded was already a .msi file, so no conversion was needed. Other than that, just repeat the steps from above.

Office Communicator:
The attendant setup file I downloaded was already a .msi file, so no conversion was needed. Other than that, just repeat the steps from above.