A change made to an Office 365 retention policy for Teams personal chats in the KPMG tenant removed data for 145,000 users. That’s unfortunate, and it underlines the need for admins to understand how retention policies work. Maybe the people involve did and it was a simple slip that could happen to anyone, but perhaps it will cause tenant admins to reflect on how they make changes to organization configurations.
Teams channel conversations are composed of threads formed by base topics and replies. Unfortunately, the Teams client UI makes it easy for users to add topics when they should post replies. The good news is that the Teams development VP at Microsoft has admitted that something needs to be done. That, and a positive response to a User Voice request, makes us think that something will happen soon.
Office 365 Tenants need to stop people using Internet Explorer. On November 30, Teams stops support for IE11; nine months later, the rest of the Microsoft 365 apps cease support. According to Microsoft, the only browser in town is the new Edge (which has an IE mode), but most will keep on using Chrome, Firefox, Brave, or Safari as they do today.
Some recent small changes in Teams will make users happy because the product’s fit and finish is improving. Speaker attribution for live captions makes conversations easier to follow and faster updates from Exchange mean that out of office notifications and change in presence states are picked up faster. These aren’t earthshattering changes, but they do make Teams more pleasant to use.
In a surprise update, Microsoft announced that Teams meetings now use persistent background effects. Once you choose an effect, Teams will use it in meetings when video is enabled. It’s a small but nice change that will help users. We need more of this kind of update across Office 365.
Microsoft has updated the Teams meeting policy to restrict automatic meeting joining (aka lobby bypass) to organizers. This is likely to be most popular with schools, but enterprirse will see value in being able to force participants to pass through the meeting lobby before joining in some circumstances. And remember, a meeting organizer can always change the settings before the meeting begins.
Petri.com is running a free 1-day virtual conference on the topic of Microsoft Teams on August 12. All are welcome to attend. The jokes will be awful, the timing lousy, and the information insightful. That’s a pretty explosive mixture, delivered by experts (well, except me) packed full of knowledge. So much so that their heads swell on an ongoing basis…
The Electron-based Microsoft Teams has a reputation of being a memory hog. Does the moniker fit? Well, it all depends on how you view how the Chromium memory model works. Some won’t like the way memory is grabbed to cache data while others will think it quite reasonable to use available memory in this way.
The Windows desktop client for Teams monitors text as users type chat and channel messages to detect if they switch language. And if they do, Teams can change language for spell checking. The code runs on the client and no data is transmitted back to base. It’s all very intelligent, but you should warn users that it might happen.
Teams supports the ability to assign policies to up to 5,000 users with background jobs. This makes it much easier to assign new policies to large groups of users. Unless you like writing your own PowerShell scripts to handle Teams policy assignment, this is definitely something that all Teams administrators need to know about.