Today, we are pleased to announce the latest additions to Teams Microsoft Graph APIs, including resource-specific consent permissions for chats and delegated permissions for tags. These additions complete the capabilities for chats and tags APIs that enable you to integrate applications into how users communicate.<\/p>\n
As main elements in collaborations, chat messages are supported through various Microsoft Graph APIs. For example, we can think of an application that requires a ticketing system to streamline customer support.<\/p>\n
When a customer messages<\/a> a support agent in this app, conversation items can quickly become tickets to address the customer’s concerns or invite other agents to collaborate. To give other agents context, Tabs<\/a> can be created to share important details. Once the ticket has been actioned, messages can be exported<\/a> and the chat lifecycle can repeat.<\/p>\n Following an application workflow, permissions must be granted to access chat messages. What permissions<\/a> accomplish at their core is to access data in Microsoft Graph via consent process by the user, admin, or team owner.<\/p>\n Chat messages already support delegated permissions<\/a> and application permissions.<\/a> The first function is on behalf of the signed-in participant, and the second requires admin consent. These permissions allow applications to read and write chat messages and members of 1:1 or group threads, so applications can offer individualized solutions or target a participant\u2019s specific tasks.<\/p>\n With the recent resource-specific consent permissions<\/a> for chat messages APIs (beta), team owners and chat owners can grant consent<\/a> for an application to access and modify chat data. These permissions allow applications to read, write, and manage chat messages and settings. They also read the applications installed in a chat and its meeting properties, and can access media, join calls and send notifications to chat participants.<\/p>\n As organizations grow, there is a constant challenge knowing the right group of people to reach, searching for items with the information of the participants to contact can lead to delays in collaboration.<\/p>\n With the latest teamworkTag<\/a> APIs (beta), you can categorize people based on attributes, such as roles, projects, skills, training, or location. For example, a \u201cNurse\u201d or \u201cManager\u201d or \u201cDesigner\u201d tag enables you to create groups of people in Teams without typing every single name. This is because tags function as targeted communication. Once a tag is applied,<\/a> communicating with the right people becomes a quicker task.<\/p>\n Users can @mention in a channel when a tag is added so everyone assigned with that tag will receive a notification. For example, you can use an @customerSupport tag to reach to all customer service agents. This notification works just as if the agents were @mentioned individually.<\/p>\n Tags currently support delegated permissions<\/a> and application permissions.<\/a> Both of these enable teamworkTags to read and write tags in Teams on behalf of the signed-in participant and the second requires an admin consent to function.<\/p>\n Thanks for taking the time to learn more about chat messages and tags capabilities. They equip different collaboration patterns as unique as each organization.<\/p>\n Happy coding! We look forward to seeing what you build!<\/p>\n","protected":false},"excerpt":{"rendered":" Today, we are pleased to announce the latest additions to Teams Microsoft Graph APIs, including resource-specific consent permissions for chats and delegated permissions for tags.<\/p>\n","protected":false},"author":69096,"featured_media":9677,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[3,128],"tags":[198],"class_list":["post-9647","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-microsoft-graph","category-microsoft-teams","tag-teamwork-and-communications"],"acf":[],"blog_post_summary":" Today, we are pleased to announce the latest additions to Teams Microsoft Graph APIs, including resource-specific consent permissions for chats and delegated permissions for tags.<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts\/9647","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/users\/69096"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/comments?post=9647"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts\/9647\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/media\/9677"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/media?parent=9647"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/categories?post=9647"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/tags?post=9647"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Tags<\/strong><\/h2>\n