Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

No cookies to display.

Pages Menu
TwitterRssFacebook

Posted by on Aug 16, 2021 in Microsoft Teams

Microsoft Teams meeting create/update/get just got new attributes in GA to control attendee experience

Microsoft Teams meeting create/update/get just got new attributes in GA to control attendee experience

The Microsoft Graph REST APIs that let developers create new Microsoft Teams meetings (as well as GET existing meetings and update meetings via POST requests) have just been updated with new attributes to control the attendee experience of those meetings.

These new properties are now part of the onlineMeeting resource type which is passed to the Create/Update methods and returned from the Get methods. They have previously only been on the /beta endpoint, now they are in GA.

The new properties which can now be set and read are:

  • allowAttendeeToEnableCamera – Indicates whether attendees can turn on their camera in the meeting
  • allowAttendeeToEnableMic – Indicates whether attendees can turn on their microphone in the meeting
  • allowMeetingChat – Specifies the mode of meeting chat
  • allowTeamworkReactions – Indicates whether Teams reactions are enabled for the meeting

They are all booleans apart from allowMeetingChat, which is actually of type meetingChatMode – which can be one of “enabled”, “disabled” or “limited”. “limited” chat means chat is enabled but only for the duration of the meeting call.

These new properties have been in beta since around April/May [ref] and it’s great to see them promoted to GA – meaning that they can now be used in production environments and thus included by developers in solutions where more granular control is needed over the meeting creation experience.

Written by Tom Morgan

Tom is a Microsoft Teams Platform developer and Microsoft MVP who has been blogging for over a decade. Find out more.
Buy the book: Building and Developing Apps & Bots for Microsoft Teams. Now available to purchase online with free updates.

Post a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Share to Microsoft Teams