Sunday, December 18, 2022

Friends of Microsoft Teams - Week 50 - 2022 (December 12 - December 18)

Hello Friend of Microsoft Teams,

Find below a list of public posts and updates on Microsoft Teams (and Microsoft 365) that have been published in Week 50 of 2022, December 12 - December 18.

Feel free to share with your partners, customers, colleagues, and peers.


What's New in Microsoft Teams (and Microsoft 365):

 Field Advisories:


M365 Message Center :


  • Teams :

(Updated) Microsoft Teams Detailed Call History Feature Update MC439275 · Published Sep 26, 2022 · Last updated Dec 15, 2022

Updated December 15, 2022: We have updated the rollout timeline below. Thank you for your patience.

Users will now get a more comprehensive view into whether calls were transferred or forwarded in Microsoft Teams' call history.

This message is associated with Microsoft 365 Roadmap ID 98455

General Availability: We will begin rollout in mid-October (previously late September) and expect rollout to be completed by late October (previously mid-October).

Government Clouds: Rollout will begin in late October and is expected to be completed by mid-January 2023 (previously early December).


Fixing timestamp format in Teams meeting Transcripts files MC485792 · Published Dec 15, 2022

We will be rolling out a fix to update the timestamp format in .docx and .vtt Teams meeting transcript files to follow the WebVTT timestamp standard. More specifically, the current timestamp, for example, 0:0:0.0 --> 0:0:1.890, will be updated to 00:00:0.0 --> 00:00:1.890 after this fix gets rolled out.

Note: If your organization does not have a dependency on the timestamp of .docx or .vtt transcript files you can safely disregard this message.

We will begin rolling this out in mid-January and expect to complete by the end of January.


Microsoft Teams: Mention Everyone in chat MC485628 · Published Dec 15, 2022

Similar to how users mention individuals in chat, users will now have the option for “Everyone” within their options for mentions. After typing @, users will see the same people results they see today, but a new option, “Everyone” will be available. By selecting Everyone and sending the message, a notification will be sent to all users in the group chat based on their selected notification settings. Users can adjust how they are notified within their Teams notification settings.

This message is associated with Microsoft 365 Roadmap ID 101573

We will begin rolling out in late January and expect to complete rollout to desktop, iOS and Android in late February 2023.


General availability - Receive all chats messages in all scopes MC485096 · Published Dec 14, 2022

The resource-specific consent (RSC) permissions model for receiving all message, originally developed for Microsoft Teams Graph APIs, is being extended to bot scenarios. This feature was available for the channel scope and now is being extended to chat scope.  With RSC, conversation owners can consent for a bot to receive all user messages in standard channels and chats without being @mentioned.

This change is related to Microsoft 365 Roadmap ID: 100883

Available now


(Updated) Graph API for Teams Meetings Transcripts MC400569 · Published Jul 14, 2022 · Last updated Dec 13, 2022

Updated December 13, 2022: We have updated the rollout timeline below. Thank you for your patience.

New org-wide application permissions and RSC application permissions have been introduced to make sure that apps can access meeting transcripts for a specific meeting. Resource specific consent (RSC) permissions, specifically enables admins to authorize users to provide consent to apps, so they get specific access to a Teams meeting’s transcripts to which it is installed to, rather than providing them access across the entire tenant.

This message is specifically associated with post-meeting transcripts access for apps - Microsoft 365 Roadmap ID: 95788 that allows authorized apps to access Teams Meetings transcripts once the meeting is over.

This API will be published to beta in end of July 2022 and to GA in late February (previously mid-January 2023)


(Updated) Export feature in Teams Admin Center MC337332 · Published Feb 28, 2022 · Last updated Dec 12, 2022

Updated December 12, 2022: We have updated the rollout timeline below. Thank you for your patience.

Teams admin center is adding support for downloading the data from the list pages like teams list page, members list page, channels list page and users list page. The downloaded data will be in the form of a CSV file. Admins can click on the “Export” icon placed on the table headers in these pages to generate the data and download the CSV from the downloads section in the header of the Teams admin center.

This message is associated with Microsoft 365 Roadmap ID: 85704

We will begin rolling this out in early March and expect to complete the rollout by late January (previously late November).


  • Microsoft 365/Viva :




For the latest information/updates you can always check these resources :


Disclaimer :

If others are interested to receive these “Friends of” messages directly from me, they can always share their contact details with me.

Or if you/they no longer want to receive these “Friends of” emails, just reply per email and I will remove you from this “Friends of” DL


Kind Regards/Vriendelijke groeten/Med vänlig hälsning/Salutations,

Mattias Kressmark

Disclaimer :

The content of this communication and its attachments (if any) is for general information purposes only and does not under any circumstance constitute a binding offer or acceptance of Microsoft Ireland Operations Limited, Microsoft NV/SA or any other Microsoft Group affiliate, unless this is expressly stated in a separate document executed by a person with sufficient powers to do so. The content shall not be considered to supplement or amend the terms of any existing agreement with Microsoft Ireland Operations Limited, Microsoft NV/SA or any other Microsoft Group affiliate. Furthermore you are reminded that the content is solely based on the limited information provided to us at the time of this communication and it will be subject to possible changes occurring hereafter.

No comments:

Post a Comment