Update: Oct 6, 2020
Thank you all for the feedback on this blog, and through other sources. Some customers and partners won’t be able to fully transition to using MSAL 2.0 because of the lack of Application Permissions in Azure Active Directory (AAD). This feature allows running an app in the background without requiring users to sign in.
As such, we’re removing the December 1 for exclusive support of AAD tokens with the Groups API. Groups API will continue to support both the legacy Yammer OAuth Tokens and AAD tokens until further notice.
We encourage using AAD tokens with Yammer where applicable (e.g.Single Page JS Application, Server Side Application). We will publish further updates here. Thank you.
Starting December 1 2020, Yammer Groups API endpoints will only support the usage of Azure Active Directory (AAD) tokens. Yammer Groups API endpoints will no longer support the usage of Yammer OAuth tokens. Microsoft recommends that customers and partners transition to using Microsoft Authentication Library (MSAL) and AAD tokens with the Yammer API.
Last year, we announced Native Mode, which gets your network ready to experience Microsoft 365 integrations. Native Mode requires that all your users are created in AAD, all Groups are Microsoft 365 Connected and all Yammer Files are stored in SharePoint Online. With the move to files in SharePoint, Yammer Files API started require using AAD tokens.
As Yammer continues its journey to integrate into the Microsoft 365 ecosystem, there will be even more shared Yammer experiences across Microsoft 365, such as with Teams, Outlook, and other applications. All of these require using AAD tokens. Yammer's OAuth token cannot be accepted to conduct these operations. Over time all Yammer API endpoints will be changed to exclusively support AAD tokens.
Starting December 1, 2020, Yammer Group API endpoints that are used to Update, Delete Groups, and manage Group Membership and Group Admins will only support AAD tokens. Using Yammer OAuth tokens will result in a bad request response from the server. Create and Read operations will be supported with Yammer OAuth tokens, however using AAD tokens for all API scenarios with Yammer is strongly recommended.
The change is applicable to the following documented Yammer Groups API endpoints:
And also applicable to undocumented Yammer Groups endpoints:
What should you do?
We’re committed to working with the developer community in transitioning to the new world of AAD tokens! Please check out the resources below, post your questions/comments here, or email firstname.lastname@example.org.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.