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

Lost in the virtual time....

on
No, this isn't a sci-fi blog. It's about windows time in a virtual environment. Some applications depend on the computers having the same time. And this is no problem if all virtual machines are running on the same host. But in my case, I have a one server running virtual servers, and one or more computers running virtualPC images to access the VM's on the server.
Now, in a perfect scenario, all computers should have the same time scource (At least within the same campus). But as in my case, the lab is totally isolated. Time servers are not available to the hostserver or the vm's (who always, unless told otherwise sync with host-time).
I have recently discovered a way to stop the virtual pc from syncing the hostoperating system. There is no gui for this, and you have to turn your VM off first. Then edit the .vmc file:
Find the section of the .VMC file that looks like this:
<integration>
<microsoft>
<mouse>
<allow type="boolean">true</allow>
</mouse>
</microsoft>
</integration>
Change it to look like this:
<integration>
<microsoft>
<mouse>
<allow type="boolean">true</allow>
</mouse>
<components>
<host_time_sync>false
</enabled>
</host_time_sync>
</components>

Restart the virtual machine, and set any time you like. Very handy, also when testing betas that have expired ;)