OAuth2 Error trying to sign into Yammer

%3CLINGO-SUB%20id%3D%22lingo-sub-33303%22%20slang%3D%22en-US%22%3EOAuth2%20Error%20trying%20to%20sign%20into%20Yammer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-33303%22%20slang%3D%22en-US%22%3E%3CP%3EWhen%20creating%20a%20new%20Flow%20template%2C%20choose%20%22Yammer%20-%20When%20there%20is%20a%20new%20message%20in%20a%20group%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20first%20thing%20it%20makes%20you%20do%20%2C%20of%20course%2C%20is%20authenticate%20with%20Yammer.%20So%2C%20we%20click%20SIgn%20in%2C%20we%20enter%20user%2Fpass.%20All%20good%2C%20then%20it%20pops%20up%20the%20Yammer%20page%20that%20says%20%22Your%20credentials%20will%20be%20forwarded%20to%20Microsoft%20PowerApps%20(Europe)%2C%20we%20click%20%22Alllow%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20soon%20as%20we%20do%20that%2C%20i%20get%20the%20OAuth2%20error%20that%20says%20this%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CDIV%20class%3D%22container%22%3E%3CDIV%20class%3D%22ng-scope%22%3E%3CDIV%20class%3D%22ng-scope%22%3E%3CDIV%20class%3D%22subsection-manage%20section-manage-flow%20ng-scope%22%3E%3CDIV%20class%3D%22row%20flow-designer-container%22%3E%3CDIV%20class%3D%22column%20medium-11%22%3E%3CDIV%20class%3D%22msla-container%20msla-host-processsimple%22%3E%3CDIV%20class%3D%22msla-designer-container%22%3E%3CDIV%20class%3D%22msla-designer-canvas%22%3E%3CDIV%20class%3D%22msla-designer-canvas-parallel%22%3E%3CDIV%20class%3D%22msla-card-container%22%3E%3CDIV%20class%3D%22msla-card-flex%22%3E%3CDIV%20class%3D%22msla-card-view-div%22%3E%3CDIV%20class%3D%22msla-card-view%22%3E%3CDIV%20class%3D%22msla-card-caption%22%3E%3CDIV%20class%3D%22msla-card%20msla-card-selected%20msla-card-fixed-width%22%3E%3CDIV%20class%3D%22msla-card-body%22%3E%3CDIV%20class%3D%22msla-error%22%3E%3CDIV%20class%3D%22msla-error-text%22%3EOAuth2%20authorization%20flow%20failed%20for%20service%20'Yammer'.%20OAuth%202%20sign%20in%20failed%20to%20exchange%20code%20for%20access%20token.%20Client%20credentials%20in%20request%20body.%20Response%20status%20code%3DForbidden.%20Response%20body%3A%20Your%20network%20is%20not%20allowed%20to%20request%20an%20OAuth%20token%20for%20this%20Application%20Client%20credentials%20in%20request%20Basic%20authorization%20header.%20Response%20status%20code%3DNotFound.%20Response%20body%3A%20invalid%20client%20application%3C%2FDIV%3E%3CDIV%20class%3D%22msla-error-text%22%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%20class%3D%22msla-error-text%22%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%20class%3D%22msla-error-text%22%3EAnyone%20have%20any%20ideas%3F%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-33303%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Flow%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-354574%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth2%20Error%20trying%20to%20sign%20into%20Yammer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-354574%22%20slang%3D%22en-US%22%3E%3CP%3EEncountering%20the%20same%20error%20in%20test%20tenant%20where%203rd%20Party%20is%20enabled.%20Please%20confirm%20if%20this%20works%20only%20in%20Corporate%20tenants%20only%20and%20not%20in%20the%20test%20licence%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20658px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F83920i7AC9D4BE5849B3C2%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%224.png%22%20title%3D%224.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-181123%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20OAuth2%20Error%20trying%20to%20sign%20into%20Yammer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-181123%22%20slang%3D%22en-US%22%3E%3CP%3EHere%20is%20what%20i%20found%20here%3A%20%3CA%20href%3D%22https%3A%2F%2Fpowerusers.microsoft.com%2Ft5%2FBuilding-Flows%2FFlow-cannot-connect-to-Yammer%2Fm-p%2F8090%23M2116%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fpowerusers.microsoft.com%2Ft5%2FBuilding-Flows%2FFlow-cannot-connect-to-Yammer%2Fm-p%2F8090%23M2116%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E%22%3C%2FSPAN%3E%3CSPAN%3EThis%20error%20is%20commonly%20thrown%20when%20the%20Yammer%20organization%20you%20belong%20to%20has%20explicitly%20disabled%20support%20for%20third%20party%20integrations.%20You%20should%20speak%20with%20your%20administrator%20on%20getting%20this%20enabled.%3C%2FSPAN%3E%3CSPAN%3E%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EYou%20should%20talk%20to%20your%20Office%20365%20Administrator%20to%20make%20sure%20Authentication%20is%20set-up%20correctly%20and%203rf%20party%20apps%20are%20allowed.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-181089%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20OAuth2%20Error%20trying%20to%20sign%20into%20Yammer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-181089%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%20I%20have%20%223rd%20Party%26nbsp%3BApplications%22%20enabled%2C%20but%20this%20does%20not%20solves%20the%20issue.%20Any%20other%20ideas%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-37600%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20OAuth2%20Error%20trying%20to%20sign%20into%20Yammer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-37600%22%20slang%3D%22en-US%22%3EHi%20Russ%3CBR%20%2F%3EI%20had%20the%20same%20error%20until%20i%20enabled%203rd%20party%20apps%2C%20so%20I'm%20pretty%20sure%20this%20is%20the%20solution%20to%20your%20issue.%3CBR%20%2F%3EHow%20can%20you%20connect%20to%20your%20Yammer%20account%20from%20a%203rd%20party%20app%20(ie%20Flow)%20if%203rd%20party%20apps%20are%20not%20allowed%20on%20your%20Yammer%20network%20%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-37495%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20OAuth2%20Error%20trying%20to%20sign%20into%20Yammer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-37495%22%20slang%3D%22en-US%22%3E%3CP%3Ehi%20Andy%3C%2FP%3E%3CP%3EStill%20doesn't%20work%20for%20me...%3C%2FP%3E%3CP%3EI%20raised%20a%20call%20on%20MS%20just%20before%20xmas%2C%20no%20response%20yet..%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20do%20not%20currently%20have%20the%20'Alllow%203rd%20party%20apps'%20set%2C%20Is%20yours%20set%20to%20allow%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-37493%22%20slang%3D%22en-US%22%3ERE%3A%20OAuth2%20Error%20trying%20to%20sign%20into%20Yammer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-37493%22%20slang%3D%22en-US%22%3EMicrosoft%20fixed%20this%20mid%20December%20-%20was%20a%20known%20issue.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-37492%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth2%20Error%20trying%20to%20sign%20into%20Yammer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-37492%22%20slang%3D%22en-US%22%3EHi%20Andy.%20You%20may%20want%20to%20see%20my%20reply%20below%20in%20case%20it%20solves%20your%20issue.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-37395%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth2%20Error%20trying%20to%20sign%20into%20Yammer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-37395%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20are%20getting%20this%20error%20because%20you%20do%20not%20have%20permission%20to%20connect%203rd%20party%20apps%20to%20your%20Yammer%20network.%3C%2FP%3E%3CP%3EYou%20need%20to%20Authorize%203rd%20Party%20Apps%20in%20the%20Yammer%20Network%20Admin%20Settings%20(Network%20Admin%26gt%3B%20Configuration%20%26gt%3B%20Enabled%20Features).%3C%2FP%3E%3CP%3ENote%3A%20this%20will%20enable%203rd%20party%20apps%20for%20your%20entire%20Yammer%20network%20and%20your%20users%20will%20have%20access%20to%20the%20Yammer%20app%20directory.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-35004%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth2%20Error%20trying%20to%20sign%20into%20Yammer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-35004%22%20slang%3D%22en-US%22%3EYes%20we%20found%20that%20the%20case%20for%20the%20powerapps%20and%20flow%20environment%20for%20Europe...%20worked%20for%20the%20US%20environment%2C%20but%20there%20are%20no%20options%20to%20change%20default%20environment%20locations...%3CBR%20%2F%3E%3CBR%20%2F%3ECome%20on%20Microsoft%20Ive%20had%20a%20ticket%20open%20for%20more%20than%20a%20week%20about%20this...%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-34965%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth2%20Error%20trying%20to%20sign%20into%20Yammer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-34965%22%20slang%3D%22en-US%22%3E%3CP%3ESame%20issue%20here...%20outside%20US..%26nbsp%3B%3CIMG%20id%3D%22smileysad%22%20class%3D%22emoticon%20emoticon-smileysad%22%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Fi%2Fsmilies%2F16x16_smiley-sad.png%22%20alt%3D%22Smiley%20Sad%22%20title%3D%22Smiley%20Sad%22%20%2F%3E%3C%2FP%3E%3CP%3EAnyone%20from%20Microsoft%20reading%20this%20thread%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-33608%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth2%20Error%20trying%20to%20sign%20into%20Yammer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-33608%22%20slang%3D%22en-US%22%3E%3CP%3EI%20thought%20it%20was%20just%20us%2C%20we%20are%20having%20the%20same%20issue.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20cannot%20connect%20Yammer%20in%20Powerapps.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAndy%20Tyrer%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-33307%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth2%20Error%20trying%20to%20sign%20into%20Yammer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-33307%22%20slang%3D%22en-US%22%3E%3CP%3EHere%20are%20the%20screenshots%2Cif%20anyone%20has%20an%20idea%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-33304%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth2%20Error%20trying%20to%20sign%20into%20Yammer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-33304%22%20slang%3D%22en-US%22%3E%3CP%3EIt%20has%20to%20be%20something%20wtih%20it%20being%20from%20out%20of%20the%20US%2C%20because%20it%20works%20fine%20on%20my%20test%20tenant%20and%20using%20my%20account%20that%20is%20inside%20the%20US%3C%2FP%3E%3C%2FLINGO-BODY%3E
Frequent Contributor

When creating a new Flow template, choose "Yammer - When there is a new message in a group"

 

The first thing it makes you do , of course, is authenticate with Yammer. So, we click SIgn in, we enter user/pass. All good, then it pops up the Yammer page that says "Your credentials will be forwarded to Microsoft PowerApps (Europe), we click "Alllow"

 

As soon as we do that, i get the OAuth2 error that says this

 

 

OAuth2 authorization flow failed for service 'Yammer'. OAuth 2 sign in failed to exchange code for access token. Client credentials in request body. Response status code=Forbidden. Response body: Your network is not allowed to request an OAuth token for this Application Client credentials in request Basic authorization header. Response status code=NotFound. Response body: invalid client application
 
 
Anyone have any ideas?

 

13 Replies

It has to be something wtih it being from out of the US, because it works fine on my test tenant and using my account that is inside the US

Here are the screenshots,if anyone has an idea

I thought it was just us, we are having the same issue.

 

We cannot connect Yammer in Powerapps.

 

Regards

 

Andy Tyrer

Same issue here... outside US.. Smiley Sad

Anyone from Microsoft reading this thread?

Yes we found that the case for the powerapps and flow environment for Europe... worked for the US environment, but there are no options to change default environment locations...

Come on Microsoft Ive had a ticket open for more than a week about this...

You are getting this error because you do not have permission to connect 3rd party apps to your Yammer network.

You need to Authorize 3rd Party Apps in the Yammer Network Admin Settings (Network Admin> Configuration > Enabled Features).

Note: this will enable 3rd party apps for your entire Yammer network and your users will have access to the Yammer app directory.

Hi Andy. You may want to see my reply below in case it solves your issue.
Microsoft fixed this mid December - was a known issue.

hi Andy

Still doesn't work for me...

I raised a call on MS just before xmas, no response yet..

 

We do not currently have the 'Alllow 3rd party apps' set, Is yours set to allow?

Hi Russ
I had the same error until i enabled 3rd party apps, so I'm pretty sure this is the solution to your issue.
How can you connect to your Yammer account from a 3rd party app (ie Flow) if 3rd party apps are not allowed on your Yammer network ?

Hi, I have "3rd Party Applications" enabled, but this does not solves the issue. Any other ideas?

Here is what i found here: https://powerusers.microsoft.com/t5/Building-Flows/Flow-cannot-connect-to-Yammer/m-p/8090#M2116

 

"This error is commonly thrown when the Yammer organization you belong to has explicitly disabled support for third party integrations. You should speak with your administrator on getting this enabled."

 

You should talk to your Office 365 Administrator to make sure Authentication is set-up correctly and 3rf party apps are allowed.

Encountering the same error in test tenant where 3rd Party is enabled. Please confirm if this works only in Corporate tenants only and not in the test licence? 

4.png