Yammer Embed missleading message when beeing used in SharePoint

%3CLINGO-SUB%20id%3D%22lingo-sub-139236%22%20slang%3D%22en-US%22%3EYammer%20Embed%20missleading%20message%20when%20beeing%20used%20in%20SharePoint%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-139236%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20606px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F25997i41BC17036146CCF5%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22yam2.PNG%22%20title%3D%22yam2.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EWe%20are%20seeing%20this%20message%20when%20using%20Yammer%20Embed%20inside%20a%20SharePoint%20page.%20The%20message%20is%20missleading%2C%20because%20we%20are%20using%20IE11.%20The%20problem%20is%20inside%20of%20the%26nbsp%3BSharePoint%20masterpage%26nbsp%3Bthat%20forces%20the%20browser%20to%20run%20in%20IE10%20document%20mode.%3C%2FP%3E%0A%3CPRE%3E%26lt%3Bmeta%20http-equiv%3D%22X-UA-Compatible%22%20content%3D%22IE%3D10%22%26gt%3B%3C%2FPRE%3E%0A%3CP%3EYammer%20Embed%26nbsp%3Bshould%20continue%20to%20work%20in%20IE11%20inside%20of%20SharePoint%2C%20or%20the%20message%20should%20state%2C%20that%20Yammer%20Embed%20is%20not%20supported%20anymore%20inside%20of%20SharePoint.%26nbsp%3BThe%20latter%26nbsp%3Bis%20a%20very%20good%20way%20to%20kill%20Yammer%20within%20organizations.%20Running%20SharePoint%20in%20Edge%20mode%20by%20modifying%20the%20masterpage%20will%20destroy%20several%20features%20like%20the%20explorer%20view%20or%20Skype%20presence.%20So%20this%20is%20not%20a%20good%20option%20either....%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-139236%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EBugs%3C%2FLINGO-LABEL%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-148665%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20Embed%20missleading%20message%20when%20beeing%20used%20in%20SharePoint%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-148665%22%20slang%3D%22en-US%22%3EWe%20were%20seeing%20the%20same%20issue%20yesterday.%20Yammer%20Embeds%20in%20SPO%20were%20loading%20the%20wrong%20content%20even%20when%20FeedID%20was%20configured%20to%20the%20code.%20This%20morning%20it%20seems%20Embeds%20are%20loading%20correctly.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-148472%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20Embed%20missleading%20message%20when%20beeing%20used%20in%20SharePoint%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-148472%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20don't%20use%20it%20either.%20We%20use%3A%3CBR%20%2F%3E%3CBR%20%2F%3Eyam.connect.embedFeed(%7Bcontainer%3A%20'%23embedded-feed'%2Cnetwork%3A%20'yourdomain.com'%2CfeedType%3A%20'open-graph'%2CobjectProperties%3A%7Btitle%3A%20openGraphTitle%2Curl%3A%20openGraphUrl%2Ctype%3A%20'page'%2Cdescription%3A%20openGraphDescription%2Cimage%3A%20openGraphImage%7D%2Cconfig%3A%7Buse_sso%3A%20true%2CshowOpenGraphPreview%3A%20false%2ChideNetworkName%3A%20true%2CpromptText%3A%20'Comment%20on%20this%20newsarticle%3F'%2Cheader%3A%20false%2Cfooter%3A%20false%2CdefaultGroupId%3A%20'1234567'%7D%7D)%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-148410%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20Embed%20missleading%20message%20when%20beeing%20used%20in%20SharePoint%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-148410%22%20slang%3D%22en-US%22%3EWe're%20finding%20that%20embeds%20that%20won't%20load%20begin%20to%20work%20if%20we%20remove%20the%20network_permalink%20parameter%20which%20is%20interesting.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-148387%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20Embed%20missleading%20message%20when%20beeing%20used%20in%20SharePoint%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-148387%22%20slang%3D%22en-US%22%3E%3CP%3EYes%2C%20I%20got%20this%20one%20from%20the%20Yammer%20development%20site%2C%20to%20make%20sure%20I%20got%20the%20latest.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-148385%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20Embed%20missleading%20message%20when%20beeing%20used%20in%20SharePoint%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-148385%22%20slang%3D%22en-US%22%3EAh%2C%20an%20old%20JS%2C%20that%20would%20make%20sense....%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-148338%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20Embed%20missleading%20message%20when%20beeing%20used%20in%20SharePoint%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-148338%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20been%20seeing%20the%20exact%20same%20thing%20at%20some%20clients.%20Embeds%20not%20showing%20correct%20group.%20Straight%20code%20embeds%20keep%20staying%20loading...%3CBR%20%2F%3E%3CBR%20%2F%3EAt%20some%20clients%20with%20code%20embeds%20I%20replaced%20the%20script%20src%20to%3A%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%0A%3CPRE%20class%3D%22cm-s-neo%22%20data-mode%3D%22text%22%3Ehttps%3A%2F%2Fc64.assets-yammer.com%2Fassets%2Fplatform_embed.js%3C%2FPRE%3E%0A%3CP%3EUsing%20this%20reference%20stopped%20the%20problem%20of%20staying%20in%20loading%20state.%20Hope%20this%20helps...%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-148336%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20Embed%20missleading%20message%20when%20beeing%20used%20in%20SharePoint%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-148336%22%20slang%3D%22en-US%22%3EI%20wonder%20if%20they%20broke%20something%2C%20all%20our%20Yammer%20embeds%20in%20SharePoint%20online%20using%20the%20classic%20web%20part%20(still%20don't%20have%20the%20new%20one)%20or%20straight%20embed%20code%20are%20a%20complete%20mess%20this%20morning.%20Not%20loading.%20Loading%20the%20wrong%20content.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-148244%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20Embed%20missleading%20message%20when%20beeing%20used%20in%20SharePoint%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-148244%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20noticed%20message%20in%20O365%20Message%20Center%20(%3CSPAN%3EMC127395%3C%2FSPAN%3E%3A(%3C%2Fimg%3E%26nbsp%3B%3CSPAN%3EWe're%20changing%20the%20default%20document%20mode%20of%20all%20classic%20pages%20to%20be%20Edge%20mode%2C%20instead%20of%20Internet%20Explorer%20(IE)%2010%20mode.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2FDisplay-a-classic-SharePoint-Online-site-in-Internet-Explorer-10-document-mode-4b4572b7-9223-45ec-8497-557a643da12a%3Fui%3Den-US%26amp%3Brs%3Den-US%26amp%3Bad%3DUS%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2FDisplay-a-classic-SharePoint-Online-site-in-Internet-Explorer-10-document-mode-4b4572b7-9223-45ec-8497-557a643da12a%3Fui%3Den-US%26amp%3Brs%3Den-US%26amp%3Bad%3DUS%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-142482%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20Embed%20missleading%20message%20when%20beeing%20used%20in%20SharePoint%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-142482%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20also%20in%20a%20similar%20situation%2C%20using%20SharePoint%202013%20with%20a%20Yammer%20embed.%26nbsp%3BWe%20chose%20to%20change%20the%20SharePoint%20tags%20to%20IE11%20mode%2C%20to%20support%20the%20Yammer%20feed.%20This%20has%26nbsp%3Bdetriment%20to%20some%20functionality%20in%20the%20SharePoint%20Intranet%20site%2C%20which%20is%20a%20genuine%20downside.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20workaround%20of%20removing%20the%20banner%20on%20Yammer%20for%20IE10%20mode%2C%20with%20the%20knowledge%20that%20Yammer%20could%20stop%20working%20at%20anytime%20is%20a%20fragile%20path%20to%20take.%20It's%20not%20a%20great%20situation%20to%20be%20caught%20in-between%20these%20two%20technologies%20as%20is%20our%20current%20predicament.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAny%20update%20on%20formal%20support%20or%20fix%20for%20this%20scenario%20would%20be%20fantastic.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-140830%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20Embed%20missleading%20message%20when%20beeing%20used%20in%20SharePoint%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-140830%22%20slang%3D%22en-US%22%3E%3CP%3EIs%20just%20checked%20on%20our%20own%20tenant%20and%20no%20message%20is%20displayed%20anymore%20in%20IE11.%20I%20am%20going%20to%20check%20at%20some%20clients%20now%20which%20had%20the%20problem%20last%20week.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-140820%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20Embed%20missleading%20message%20when%20beeing%20used%20in%20SharePoint%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-140820%22%20slang%3D%22en-US%22%3E%3CP%3EAccording%20to%20the%20MS%20support%20they%20are%20publishing%20another%20banner%20message%20%3CSTRONG%3Etoday%3C%2FSTRONG%3E%20with%20updated%20content.%20Also%20they%20said%20that%20they%20are%20working%20with%20the%20Sharepoint%20product%20group%20to%20solve%20the%20issue%20in%20background%20but%20there%20is%20no%20ETA%20for%20this.%20Any%20update%20or%20insight%20from%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F20846%22%20target%3D%22_blank%22%3E%40Steve%20Nguyen%3C%2FA%3E%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-140415%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20Embed%20missleading%20message%20when%20beeing%20used%20in%20SharePoint%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-140415%22%20slang%3D%22en-US%22%3E%3CP%3EI%20opened%20a%20support%20case%20to%20MS%20support%20and%20got%20quick%20response%20that%20they%20have%20received%20multiple%20tickets%20for%20this%20issue.%20Banner%20was%20removed%20on%2022nd%20Dec%20and%20will%20be%20replaced%20with%20a%20new%20one%20(%3F)%20on%202nd%20January.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%2BIssue%20%3A%20Customer%20who%20are%20using%20IE%2011%20Browser%20are%20getting%20a%20banner%20message%20on%20Yammer%20Embed%20Feed%20stating%20that%20%22As%20of%20December%2015%2C%202017%20Yammer%20no%20longer%20support%20internet%20explorer%2010%20and%20will%20no%20longer%20work%20reliably%20on%20this%20browser.%20To%20continue%20using%20Yammer%2C%26nbsp%3B%20you%20must%20upgrade%20browser.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26gt%3B%26gt%3BIn%20what%20all%20scenarios%20is%20Yammer%20Embed%20being%20used%20by%20Customer.%3C%2FP%3E%0A%3CP%3E%2B%2BYammer%20embed%20is%20used%20by%20Customers%20on%20SharePoint%20On%20Premise%20Sites%2C%20SharePoint%20Online%20Sites%20and%20Custom%20Intranet%20Sites.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26gt%3B%26gt%3BIf%20Customer%20is%20using%20IE%2011%20browser%20%2C%20then%20why%20are%20they%20getting%20this%20banner%20message.%3C%2FP%3E%0A%3CP%3E%2B%2BCustomers%20who%20are%20using%20SharePoint%20On%20premise%20and%20SharePoint%20Online%20-%20SP%20by%20default%20forces%20the%20site%20to%20be%20rendered%20in%20IE%2010%20Document%20mode.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26gt%3B%26gt%3BWill%20Yammer%20show%20the%20Banner%20message%20if%20the%20browser%20is%20IE%2011%20however%20the%20document%20mode%20is%20IE%2010%3C%2FP%3E%0A%3CP%3E%2B%2BYes%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26gt%3B%26gt%3BAre%20there%20are%20plans%20by%20the%20Yammer%20Support%20Group%20to%20mitigate%20the%20end%20user%20impact%3C%2FP%3E%0A%3CP%3E%2B%2B%20Yes%2C%20As%20of%2022nd%20December%202017%20-%20the%20banner%20message%20has%20been%20hidden.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26gt%3B%26gt%3BTill%20when%20would%20the%20banner%20message%20be%20hidden%20from%20Yammer%20embed%20Feed.%3C%2FP%3E%0A%3CP%3E%2B%2BThe%20banner%20message%20would%20be%20hidden%20till%202nd%20January%202018%20(Might%20be%20extended%20depending%20on%20other%20dependencies)%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26gt%3B%26gt%3BWhat%20happens%20post%202nd%20January%20(or%20later)%3C%2FP%3E%0A%3CP%3E%2B%2B%20The%20banner%20message%20would%20be%20replaced%20by%20an%20Updated%20Banner%20message%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26gt%3B%26gt%3BWhat%20is%20going%20to%20be%20the%20content%20of%20this%20updated%20banner%20%3F%3C%2FP%3E%0A%3CP%3E%2B%2B%20We%20are%20currently%20not%20aware%20of%20what%20the%20new%20updated%20banner%20is%20going%20to%20say.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26gt%3B%26gt%3BWould%20Customer%20have%20an%20option%20to%20request%20removal%20of%20the%20updated%20banner.%3C%2FP%3E%0A%3CP%3E%2B%2B%20YEs%2C%20Customer%20can%20contact%20Microsoft%20Support%20for%20removing%20the%20updated%20Banner.%3C%2FP%3E%0A%3CP%3E%2B%2B%20Customer%20requesting%20for%20removal%20of%20updated%20banner%20-%20would%20mean%20that%20they%20now%20completely%20understand%20that%20Yammer%20would%20not%20work%20reliably%20or%20may%20become%20inoperable%20if%20used%20on%20IE%2011%20browser%20with%20IE%2010%20document%20mode%20and%20that%20they%20should%20ASAP%20upgrade%20to%20IE%2011%20Document%20Mode.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E%26gt%3B%26gt%3BWe%20can%20do%20that%20for%20our%20Custom%20Intranet%20Sites%2C%20but%20what%20about%20SharePoint%20On-Premise%20and%20SharePoint%20Online%2C%20it%20would%20still%20render%20and%20force%20our%20IE11%20browser%20to%20work%20in%20IE%2010%20document%20Mode.%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E%2B%2B%20Yammer%20product%20group%20continues%20to%20engage%20with%20SP%20PG%20-%20on%20this%20however%20we%20have%20no%20idea%20if%20SharePoint%20would%20update%20the%20settings%20for%20their%20sites%20to%20be%20rendered%20in%20IE%2011%20document%20mode.%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26gt%3B%26gt%3BDo%20Customer%20have%20an%20option%20to%20request%20for%20an%20ADVANCE%20opt-out%20of%20the%20banner%20that%20is%20going%20to%20be%20displayed%20on%202nd%20Jan%20(or%20later)%3C%2FP%3E%0A%3CP%3E%2B%2B%20Yes%2C%20we%20would%20need%20an%20Email%20from%20the%20GA%20for%20this.%20A%3CU%3Epproval%20in%20the%20below%20format%3A%3C%2FU%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CEM%3E%22I%20(Global%20admin%20email%20id)%20approve%20Microsoft%20to%26nbsp%3Bhide%20the%20banner%20from%20Yammer%20embed.%20I%20am%20aware%20that%26nbsp%3BYammer%20embed%20will%20get%20inoperable%20any%20time%20after%202nd%20January%202018%20even%20if%20the%20banner%20is%20hidden%26nbsp%3Bas%20Yammer%20has%20ended%20support%20for%20IE%2010%20Document%20mode.%20%3C%2FEM%3E%3CEM%3EYammer%20embed%26nbsp%3Bwould%20work%20on%20Modern%20Document%20Mode%20(IE%2011%20Document%20Mode)%3C%2FEM%3E%3CEM%3E%26nbsp%3B%26nbsp%3B%22.%3C%2FEM%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-140387%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20Embed%20missleading%20message%20when%20beeing%20used%20in%20SharePoint%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-140387%22%20slang%3D%22en-US%22%3EWe%20are%20also%20seeing%20this%20issue!%3CBR%20%2F%3EStrange%20enough%20it%20is%20not%20visible%20all%20users%20with%20IE11%2C%20even%20when%20we%20should%20have%20managed%20homogenous%20IT%20environment%20with%20same%20IE11%20version%20installed%20on%20all%20company%20computers.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-139964%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20Embed%20missleading%20message%20when%20beeing%20used%20in%20SharePoint%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-139964%22%20slang%3D%22en-US%22%3E%3CP%3EPlease%20do%20something%20to%20alleviate%20this%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F20846%22%20target%3D%22_blank%22%3E%40Steve%20Nguyen%3C%2FA%3E%26nbsp%3B%26amp%3B%20Yammer%20team!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-139666%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20Embed%20missleading%20message%20when%20beeing%20used%20in%20SharePoint%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-139666%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20visibility%20that%20the%20Yammer%20team%20is%20aware%20and%20discussing.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F20846%22%20target%3D%22_blank%22%3E%40Steve%20Nguyen%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-139399%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20Embed%20missleading%20message%20when%20beeing%20used%20in%20SharePoint%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-139399%22%20slang%3D%22en-US%22%3E%3CP%3EOther%20than%20telling%20the%20CEO%20%22ignore%20that%22%2C%20no.%3C%2FP%3E%0A%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-139397%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20Embed%20missleading%20message%20when%20beeing%20used%20in%20SharePoint%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-139397%22%20slang%3D%22en-US%22%3E%3CP%3EAlso%20receiving%20this%20error.%20Have%20you%20found%20a%20solution%20for%20this%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-139343%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20Embed%20missleading%20message%20when%20beeing%20used%20in%20SharePoint%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-139343%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20getting%20this%20message%20too.%20Can%20someone%20point%20to%20what%20the%20root%20cause%20is%3F%20Why%20did%20this%20start%20popping%20up%20today%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-139298%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20Embed%20missleading%20message%20when%20beeing%20used%20in%20SharePoint%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-139298%22%20slang%3D%22en-US%22%3EWhat%20is%20the%20solution%20to%20resolve%20above%20issue%20%3F%3C%2FLINGO-BODY%3E
Contributor

yam2.PNG

We are seeing this message when using Yammer Embed inside a SharePoint page. The message is missleading, because we are using IE11. The problem is inside of the SharePoint masterpage that forces the browser to run in IE10 document mode.

<meta http-equiv="X-UA-Compatible" content="IE=10">

Yammer Embed should continue to work in IE11 inside of SharePoint, or the message should state, that Yammer Embed is not supported anymore inside of SharePoint. The latter is a very good way to kill Yammer within organizations. Running SharePoint in Edge mode by modifying the masterpage will destroy several features like the explorer view or Skype presence. So this is not a good option either....

 

19 Replies
What is the solution to resolve above issue ?

We are getting this message too. Can someone point to what the root cause is? Why did this start popping up today?

Also receiving this error. Have you found a solution for this?

Other than telling the CEO "ignore that", no.


I have visibility that the Yammer team is aware and discussing.

 

@Steve Nguyen

Please do something to alleviate this @Steve Nguyen & Yammer team!

We are also seeing this issue!
Strange enough it is not visible all users with IE11, even when we should have managed homogenous IT environment with same IE11 version installed on all company computers.

I opened a support case to MS support and got quick response that they have received multiple tickets for this issue. Banner was removed on 22nd Dec and will be replaced with a new one (?) on 2nd January.

 

 

+Issue : Customer who are using IE 11 Browser are getting a banner message on Yammer Embed Feed stating that "As of December 15, 2017 Yammer no longer support internet explorer 10 and will no longer work reliably on this browser. To continue using Yammer,  you must upgrade browser.

 

>>In what all scenarios is Yammer Embed being used by Customer.

++Yammer embed is used by Customers on SharePoint On Premise Sites, SharePoint Online Sites and Custom Intranet Sites.

 

>>If Customer is using IE 11 browser , then why are they getting this banner message.

++Customers who are using SharePoint On premise and SharePoint Online - SP by default forces the site to be rendered in IE 10 Document mode.

 

>>Will Yammer show the Banner message if the browser is IE 11 however the document mode is IE 10

++Yes

 

>>Are there are plans by the Yammer Support Group to mitigate the end user impact

++ Yes, As of 22nd December 2017 - the banner message has been hidden.

 

>>Till when would the banner message be hidden from Yammer embed Feed.

++The banner message would be hidden till 2nd January 2018 (Might be extended depending on other dependencies)

 

>>What happens post 2nd January (or later)

++ The banner message would be replaced by an Updated Banner message

 

>>What is going to be the content of this updated banner ?

++ We are currently not aware of what the new updated banner is going to say.

 

>>Would Customer have an option to request removal of the updated banner.

++ YEs, Customer can contact Microsoft Support for removing the updated Banner.

++ Customer requesting for removal of updated banner - would mean that they now completely understand that Yammer would not work reliably or may become inoperable if used on IE 11 browser with IE 10 document mode and that they should ASAP upgrade to IE 11 Document Mode.

 

>>We can do that for our Custom Intranet Sites, but what about SharePoint On-Premise and SharePoint Online, it would still render and force our IE11 browser to work in IE 10 document Mode.

++ Yammer product group continues to engage with SP PG - on this however we have no idea if SharePoint would update the settings for their sites to be rendered in IE 11 document mode.

 

>>Do Customer have an option to request for an ADVANCE opt-out of the banner that is going to be displayed on 2nd Jan (or later)

++ Yes, we would need an Email from the GA for this. Approval in the below format:

 

"I (Global admin email id) approve Microsoft to hide the banner from Yammer embed. I am aware that Yammer embed will get inoperable any time after 2nd January 2018 even if the banner is hidden as Yammer has ended support for IE 10 Document mode. Yammer embed would work on Modern Document Mode (IE 11 Document Mode)  ".

According to the MS support they are publishing another banner message today with updated content. Also they said that they are working with the Sharepoint product group to solve the issue in background but there is no ETA for this. Any update or insight from @Steve Nguyen?

Is just checked on our own tenant and no message is displayed anymore in IE11. I am going to check at some clients now which had the problem last week.

We are also in a similar situation, using SharePoint 2013 with a Yammer embed. We chose to change the SharePoint tags to IE11 mode, to support the Yammer feed. This has detriment to some functionality in the SharePoint Intranet site, which is a genuine downside.

 

The workaround of removing the banner on Yammer for IE10 mode, with the knowledge that Yammer could stop working at anytime is a fragile path to take. It's not a great situation to be caught in-between these two technologies as is our current predicament.

 

Any update on formal support or fix for this scenario would be fantastic.

Just noticed message in O365 Message Center (MC127395:( We're changing the default document mode of all classic pages to be Edge mode, instead of Internet Explorer (IE) 10 mode.

 

https://support.office.com/en-us/article/Display-a-classic-SharePoint-Online-site-in-Internet-Explor...

 

 

I wonder if they broke something, all our Yammer embeds in SharePoint online using the classic web part (still don't have the new one) or straight embed code are a complete mess this morning. Not loading. Loading the wrong content.

I have been seeing the exact same thing at some clients. Embeds not showing correct group. Straight code embeds keep staying loading...

At some clients with code embeds I replaced the script src to:

https://c64.assets-yammer.com/assets/platform_embed.js

Using this reference stopped the problem of staying in loading state. Hope this helps... 

Ah, an old JS, that would make sense....

Yes, I got this one from the Yammer development site, to make sure I got the latest. 

We're finding that embeds that won't load begin to work if we remove the network_permalink parameter which is interesting.

We don't use it either. We use:

yam.connect.embedFeed({container: '#embedded-feed',network: 'yourdomain.com',feedType: 'open-graph',objectProperties:{title: openGraphTitle,url: openGraphUrl,type: 'page',description: openGraphDescription,image: openGraphImage},config:{use_sso: true,showOpenGraphPreview: false,hideNetworkName: true,promptText: 'Comment on this newsarticle?',header: false,footer: false,defaultGroupId: '1234567'}});

We were seeing the same issue yesterday. Yammer Embeds in SPO were loading the wrong content even when FeedID was configured to the code. This morning it seems Embeds are loading correctly.