Support yammer app#46
Merged
Merged
Conversation
…audience for yammer
This reverts commit 93575a3.
synth
requested changes
Jul 1, 2025
synth
left a comment
synth
left a comment
Owner
There was a problem hiding this comment.
Actually, tests are failing, can you please review?
synth
approved these changes
Jul 2, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Auth 2.0 authentication for Yammer is deprecated. Has been re branded to Viva engage. Now to access legacy Viva Engage ( Yammer ) APIs, it is recommended to use Yammer API registered via Azure Portal. This PR kind of differentiates between Microsoft graph and Yammer profile, so bearer token returned does not throw invalid audience error.
Note:
We supply explicit yammer scopes before applying for bearer token. Yammer scopes can be
Yammer docs