Yammer Web Part -- prompt to allow 3rd party cookies

%3CLINGO-SUB%20id%3D%22lingo-sub-299055%22%20slang%3D%22en-US%22%3EYammer%20Web%20Part%20--%20prompt%20to%20allow%203rd%20party%20cookies%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-299055%22%20slang%3D%22en-US%22%3E%3CP%3EUsers%20just%20started%20reporting%20that%20they%20are%20now%20being%20prompted%20to%20allow%203rd%20party%20cookies.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Eis%20this%20something%20new%20that%20has%20just%20happened%3F%26nbsp%3B%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%222018-12-11_12-41-00.png%22%20style%3D%22width%3A%20790px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F62410i5FC169E109C64920%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%222018-12-11_12-41-00.png%22%20alt%3D%222018-12-11_12-41-00.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-299055%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EYammer%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EYammer%20Embed%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-299164%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20Web%20Part%20--%20prompt%20to%20allow%203rd%20party%20cookies%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-299164%22%20slang%3D%22en-US%22%3EWe%20had%20this%20issue%20in%20the%20past%20if%20I%20remember%20correctly%20but%20the%20error%20display%20was%20completely%20different%20%2C%20it%20was%20nothing%20to%20do%20with%20the%20Yammer%20Web%20part%20and%20there%20was%20an%20issue%20with%20the%20browser%20update.%3CBR%20%2F%3E%3CBR%20%2F%3EHope%20this%20helps!%3C%2FLINGO-BODY%3E
MVP

Users just started reporting that they are now being prompted to allow 3rd party cookies. 

 

is this something new that has just happened? 2018-12-11_12-41-00.png

 

1 Reply
We had this issue in the past if I remember correctly but the error display was completely different , it was nothing to do with the Yammer Web part and there was an issue with the browser update.

Hope this helps!