Update February 24, 2020: Removing the temporary support that associates AAD tokens with Yammer OAuth tokens at the end of March 2020.
We’re rolling out a new feature where all new files uploaded into Microsoft 365 Connected Yammer Groups will be stored in SharePoint Online by default. With files stored in SharePoint Online, third-party apps using Yammer authentication to access Yammer Files API endpoints and performing file operations (such as upload, preview, download and delete) will get an error on those API calls.
Reason: The Yammer OAuth token does not include Azure Active Directory (AAD) claims, which is required for accessing files stored in SharePoint Online.
What are we doing?
We have been providing temporary support that allows third-party apps using Yammer Authentication to access Yammer Files endpoints to perform file operations (such as upload, preview, download and delete) on files in SharePoint by associating Azure Active Directory (AAD) tokens with Yammer OAuth tokens.
We are now moving to the next stage of the migration; we will begin removing the temporary support that associates AAD tokens with Yammer OAuth tokens at the end of March 2020.
This temporary support will be fully removed by the end of April and after that third-party apps using Yammer Authentication to access Yammer Files endpoints to perform file operations will no longer be able to successfully access the files and those API calls will receive an error.
We have recently changed auth requirements for third-party apps to conduct operations on Yammer files API, with Yammer files moving to SharePoint Online. We’re providing advance notice to help you prepare for this change, help resolve issues, and improve documentation and guidance.
What can you do?
You can continue to use the Yammer Files API to access files in Yammer storage without any further action.
However, if you have a third-party application that needs to perform operations on Yammer files stored in SharePoint Online for Microsoft 365 Connected Yammer groups, then we recommend that your application uses AAD authentication and leverages AAD libraries to refresh AAD claims when they expire. If AAD claims are missing or expired, then file operations will be rejected.
For more information on how to generate and manage AAD Access Tokens, see the Authentication Libraries page.
We are also previewing a new API to upload files into Yammer Groups. An AAD token is required for uploading files into an Microsoft 365 Connected Yammer Group. Read the documentation here.
As Yammer integrates further into Microsoft 365, we’re excited for additional platform opportunities through the Azure Active Directory. Recently, we announced preview support for using AAD tokens with all documented Yammer v1 APIs and are working on adding more support. Check out the resources below for information on creating an AAD app and calling Yammer APIs. We encourage the developer community to explore developing their Yammer apps in Azure AD. There’s also code samples in Yammer’s GitHub repo and in the links below.
The following limitations have been identified and we’re planning on addressing them:
We’re interested in all your feedback so please be sure to comment on this blog. If you would like to discuss in detail then please email us or join the Monthly Yammer Platform and API Office Hours, first Wednesday of every Month from 11am to 12pm Pacific Time. We realize that this time may not be convenient for all our partners and customers, so we're considering expanding the office hours to other time zones in the near future. We're looking forward to engaging with you. Thank you!
Resources from this blog:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.