Teams supports the ability to allow selected users to enable Public Preview features in the desktop and browser clients for an early view of functionality. You’ll need to create a new update policy in the Teams admin center and assign it to the people you want to access public preview. It’s all very easy and very useful, which is nice.
Browsing a Teams configuration file uncovered a reference to a blueberry. There’s no obvious link between Teams and a small fruit, so it’s some form of in-joke among the product designers or developers. A point of trivia for a holiday Friday!
Participants in Teams meetings can use the meeting chat to discuss topics, post pointers, and so on. The access rules are changing for some added to a meeting to make sure that people don’t get too much access to meeting resources (like chat) once the meeting finishes. It’s a small but important point for Teams administrators to understand.
Outlook for Windows has a Groups menu bar which is displayed when conversations in a Microsoft 365 group are accessed. A new Teams button is available to bring users to the General channel of team-enabled groups. It’s an interesting decision by Microsoft to add the button because I am not quite sure if any need exists for such a facility.
An update to the Teams Windows client introduces automatic noise suppression for Teams meetings. You can tune suppression up or down to reflect your environment. The feature works by analyzing the audio feed from the microphone used in a meeting and removing unwanted noise. The more suppression is done, the more resources are used, so this is something to keep an eye on.
Together Mode is a more immersive way to present participants in a Teams meeting. The original theater scene is being augmented with new scenes including boardrooms (suitable for small meetings) and amphitheaters (for large meetings). At the same time, the view used for Teams meeting recordings is changing from 2×2 to 3×3.
The Teams Windows and MacOS desktop clients will soon allow users to add a personal account to the set of Office 365 tenants they connect to. A great deal of excitement ensued after people saw Microsoft 365 roadmap item 68845 and assumed this meant that Teams would support connections with multiple work accounts. The ability to add more than one work account to your Teams profile isn’t available now as the update is to support connectivity to Teams at home (personal), but support for multiple work accounts is coming in the future.
Two recent updates released for Microsoft Teams gives users the ability to set a duration for their presence status and five-minute end of meeting notifications. The notifications are just a nagging prompt that the meeting will end soon. It doesn’t mean that everyone will be forced out of the meeting when the five minutes expire, even if you’d like this to be the case.
The Teams Meeting add-in for Outlook schedules online private Teams meetings. A recent update for Outlook for Windows allows meeting settings to be changed. It’s a logical and useful update to allow people who prefer to work in Outlook to maintain their meetings without needing to go to the Teams calendar app.
Microsoft’s FY21 Q3 results told us that Teams now has 115 million users, a 53% uptick since April. Office 365 keeps on growing in numbers, revenue, and profit. While growth might be slowing, there’s still a ton of accounts to be moved to the cloud, where they’ll probably end up as Teams users.
Teams notifications can now be handled by Windows and macOS, and you can get better privacy by disabling message preview in the notifications, including on Teams mobile clients. The privacy updates are available now and support for the native OS notifications in both Windows and macOS should be available in mid-November.
Teams depends on Microsoft 365 groups. You can add groups as meeting attendees and expect that members of those groups will receive meeting invitations. But they won’t unless you update group settings to force Office 365 to send invitations to all members. The job is easily done with PowerShell, and we show how in this post.
Teams gives Office 365 tenants the option to store meeting recordings in Stream or OneDrive for Business (including SharePoint Online). Now configurable through Teams meeting policies, new meeting recordings are dealt with like any other file, meaning that you can share recordings, apply labels, update metadata, and so on.
In an update posted to Teams User Voice, Microsoft said that they had enabled offline capabilities for messaging with access to recent chats and channel conversations. This is good, but the problem is that Teams is much more than chats and offline access remains problematic for many of the components people access through Teams. Until all apps support offline access, functionality will remain limited.
Users of ARM64 devices like the Surface Pro X can now download a native ARM64 Teams desktop client. According to users, the native client is faster and more stable than running the Teams 32-bit client under emulation. It’s good news for people who like the battery life and mobile connectivity of ARM devices while also giving developers who might have ignored ARM on Windows up to now something to think about.
Without saying anything, Microsoft changed where Microsoft 365 stores Teams compliance records in user and group mailboxes. The logic behind the change is impeccable even if it will cause PowerShell scripts to break. In addition, any ISV claiming to backup Teams by copying compliance records has some work to do.
The latest build of the Microsoft Teams desktop and browser clients include the ability for users to see the essential details of calendar events through a “peek.” Single clicking on an event exposes the most commonly used information and some command buttons. It’s a quick and easy way to find out what you need to know about an event. Also, Teams has finally shipped two features announced in June and July, examples of how things sometimes get delayed for different reasons.
The latest update for the Teams admin center includes the ability to manage the permissions used by third-party apps to access data via the Microsoft Graph. The updates also include the ability to manage resource specific consent (RSC) for Teams apps. While third-party apps ate the obvious target, LOB apps created by tenants are managed in the same way.
Teams is introducing a new Offline presence status this month to allow users to continue working while appearing unavailable and uncontactable to coworkers. The new status behaves differently to the Do Not Disturb presence, which gives coworkers some hope that you’ll soon be online and available.
Microsoft Teams allows meeting organizers to control if attendees can unmute themselves during meetings with a new control introduced in October 2020. The new control is likely to be more popular in education settings than in the corporate world, but sometimes it’s nice to be able to take control and stop someone speaking.
The ability to create new Teams using customizable templates is now rolling out to Office 365 tenants. Microsoft provides 13 out-of-the-box templates and tenants can add their own to meet their needs. Microsoft thinks that templates will help standardize the design of Teams and drive best practice. Time will tell.
Microsoft announced that Teams meetings will support breakout rooms in Q4 2020 for commercial, education, and GCC Office 365 tenants. The new feature allows up to 50 sub-meetings (breakout rooms) to be created from a meeting. The meeting organizer can then assign people to rooms, which then host discussions. The rooms can be started and closed as needed, and participants in each room can share information with each other just like a regular Teams meeting.
Microsoft has launched version 1.1.6 of the PowerShell module for Teams (MicrosoftTeams). The new module makes the Skype for Business Online connector unnecessary because it contains the New-CsOnlineSession cmdlet needed to create a new session to use the cmdlets used to manage Teams policies.
We bet you never knew about the importance of app pill counts. Well, the badge counts shown by apps like Teams are guides for users to know when new information is available. It’s important enough for Teams to invest in a new Teams Badge Count service to improve the accuracy of the new item counts shown to users. Here’s what’s happening.
You can easily add people from outside your Office 365 tenant to the membership of Teams, but some oversight of who those people are and what teams they join is probably needed. This PowerShell script shows how to find records in the Office 365 audit log and figure out if they relate to the creation of new guest accounts before sending email asking to justify the addition of the new account.
A preview of a new migration API for Teams is with ISVs. The API is to migrate data from other chat platforms (Slack is the obvious target) to Teams. There’s still no news about solid APIs for tenant to tenant migration or backup and restore for Teams. Microsoft is really interested in moving people off competitor platforms to Teams. It seems they are less interested in doing some of the heavy lifting involved in tenant management and restructuring.
Adding a New conversation button to the Teams client user interface might seem like an insignificant UI tweak. However, keeping replies with their topics is important because it helps users find information and helps compliance searches assemble full conversations. Not many would think about how a UI change affects compliance and eDiscovery searches, but we do…
The Microsoft Teams Praise app is used to acknowledge the achievements of people. Different badges exist to highlight various ways people contribute to teams. Now you can create custom badges and publish them for use in the Praise app. All sorts of interesting ideas come to mind. How artistic can you be?
Teams is adopting the common file sharing mechanism used by Office 365 applications. The change is now going on and should be deployed worldwide by the end of September. With Teams in the fold, we can say that sharing is done consistently across Office 365, which can’t be a bad thing.
Microsoft has spruced up the Teams meeting pre-join screen to gather all the settings that participants can use to configure their audio and video for a meeting. The browser interface is slightly different because browsers don’t support background effects. The new screens are better than before and are a good example of how to apply rationalization and simplification to UX design.
A recent change to Teams search means that matching files are included in the autosuggested list generated as users type in search terms. It’s a small but good change. The files data comes from SharePoint Online sites the user can access and their personal OneDrive for Business account.
Microsoft 365 Groups are used by applications like Teams and Yammer. The PowerShell Get-UnifiedGroup cmdlet finds groups, but can it find the groups enabled for Teams and Yammer? Here’s some idle musing on the topic which might or might not interest you.
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.