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 21, 2021 in Development, Microsoft Teams

Protect what’s important: creating Teams with sensitivity labels via API & template

Protect what’s important: creating Teams with sensitivity labels via API & template

You’ll soon be able to specify a sensitivity label when creating a Microsoft Teams team via Microsoft Graph APIs or when creating from templates. Sensitivity labels are a way of classifying different teams according to their content and applying different rules around access control etc.

There’s a new roadmap item that describes this feature, with a status of “in development”:

For API calls, the most likely way this will be implemented is by specifying the value in the team resource type provided when POSTing to create a new team. There is already a classification property there now which is an optional field that “typically describes the data or business sensitivity of the team”, so I imagine this is the property that will be used for this (if it isn’t already – it almost looks like it would work today, but I haven’t tried it).

The estimated release date is September 2021, although it can take some time to roll out across the world. It also appears that this tenant will go live at the same time for multiple Microsoft Cloud types including DoD, GCC and GCC High.

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