Microsoft plans to make the Dynamic View feature available for Teams meetings in mid-March. The signs are that the enhanced presentation of meeting content will make attending meetings a tad more engaging. Not much can be done with visual tweaks to rescue boring meetings where presenters drone on about stuff they should cover in a few minutes, but maybe the changes made by Dynamic View will brighten attendee spirits, We can but hope.
Attendees of Teams meetings now have the ability to share their opinion of the proceedings through live reactions, a set of emoticons ranging from thumbs-up to laugh. Reactions appear on attendee cards or float up from the bottom of the screen when material is beiing shared. Tenants can disable reactions uising Teams meeting policies, but meeting organizers can change meeting settings to allow reactions in specific events. Although it seems like a feature that doesn’t add much for a business user, reactions have their place – if used intelligently!
Now deployed to Office 365 tenants, large Teams meetings can support up to 20,000 view-only attendees, if an organization chooses to update its Teams meeting policies. Interestingly, this is a feature which Microsoft originally planned to license under its Teams advanced communication add-on, but the growth of large meetings in organizations might have forced their hand to bring the feature to mainline Teams.
Teams desktop clients are being updated with a new history menu to reveal the last 20 locations visited by a user in their Teams session. It’s a much faster way to get back to something than the older back arrow method. Another example of how Microsoft is refining the Teams client UI to remove little bits of friction and make everything work more smoothly. Or so they say.
Microsoft is changing the way new teams are created in the Teams admin center to make sure that their settings are consistent with teams created in other interfaces. It’s a good idea because it means that all teams are then created equal. Organizations who wish to use different settings can update teams once they’re created using either PowerShell or the Graph API.
The Teams desktop and browser clients are gaining an offline send capability. Messages sent offline are queued locally and go when the network reappears. Connectivity must be resumed within 24 hours. If not, users need to review the messages to make sure that it still makes sense to resend them.