Microsoft Teams now supports roles for meetings. You can assign the presenter role to specific participants, who then have rights to present and other actions, like recording the meeting. Everyone who’s not a presenter is an attendee. These folk stay nice and quiet and listen to what’s going on and all the good information shared by the presenters.
The Azure Active Directory Group Naming policy generates display names for new Office 365 Groups created by various applications. You can include a prefix or suffix in a group name, The approach taken by email favored prefixes because this gathered all distribution lists together in one place in the GAL. However, prefixes work better with applications like Teams.
The Microsoft Immersive Reader exists to make messages more readable for those who need a little help. It’s built into Office apps like Teams and OWA. Most people don’t know this or don’t need to use the reader, but those who do need support to access and understand text will find the Immersive Reader very helpful.
Some new and updated cmdlets in a new version of the Teams PowerShell module are available to support private channels. The cmdlets and parameters are pretty straightforward for anyone used to working with Teams through PowerShell. Remember to read up and understand all about private channels before trying to work with them through PowerShell.
Microsoft is rolling out an upgraded rich federated experience for Teams to replace the previous plaintext 1:1 chat experience. When enabled, you’ll be able to send rich formatted text, emojis, and stickers to external Teams users in other Office 365 tenants and greatly increase the impact of your thoughts. The upgrade is rolling out now and should be complete worldwide by early December 2019.