New Feature Launched in Microsoft Teams End Meeting & Multiple Chat Feature
Microsoft Teams Application has always been improving based on the feature’s availability in the Teams Application. Microsoft has been enhancing the features some based on the existing Skype for Business Application and some based on the User Voice Request. New Features Released in the April Update of Microsoft Teams Application There were requests wherein the Microsoft Teams Meeting used to continue even after all the participants have left the meeting. One of the primary features available in Skype for Business Application was missing in Microsoft Teams Application of End Meeting, With the latest Microsoft Teams Application Released in April with the version 1.3.00.8663 Microsoft has released the End Meeting in Microsoft Teams Application. Here is the below snapshot of the Feature Availability. The Feature released is available with both the Meet-Now Meetings and with the schedule Microsoft Teams Meeting New Features Rolling in the April – May Updates of Microsoft Teams Application Multi-Window Chat is a new Microsoft Teams feature which enables users to multitask more efficiently by popping out their chat conversations into separate windows. We'll begin roll-out to all customers starting in early April and expect to complete the roll-out by the end of May.This enhancement is related to Microsoft 365 Road mapID 57292. How does this affect me? Once available users will be able to engage in chat sessions in windows outside the Teams client.There are several ways users can pop-out their conversations: Double-click on a conversation in the chat list. Click “Pop out chat” from the context menu for a chat in the chat list. Click the ‘pop out’ button in the top-right corner of the chat header. Use the slash command /pop name. Double-click on an avatar picture Hover over a chat in the chat list and click on the 'pop out' button What do I need to do to prepare? Multi-Window Chat will be enabled by default and there is nothing you need to do to prepare for this change. You may want to update training and documentation as appropriate
