{"_id":"55761ac11ce9e6370050137b","parentDoc":null,"category":{"_id":"546b9082b47b5d1400109ee0","pages":["54737d5f1a20c70800e1895f","54737d801a20c70800e18961","54737d95007eb108007e03a8","547381da007eb108007e03c7","547382311a20c70800e1897a","55761ac11ce9e6370050137b"],"project":"545137a814af501a00b50cf9","version":"545137a814af501a00b50cfc","__v":6,"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2014-11-18T18:31:30.383Z","from_sync":false,"order":8,"slug":"yammer-embed","title":"Yammer Embed"},"user":"5490a27d0c7786160022fb30","version":{"_id":"545137a814af501a00b50cfc","project":"545137a814af501a00b50cf9","__v":11,"createdAt":"2014-10-29T18:53:28.525Z","releaseDate":"2014-10-29T18:53:28.525Z","categories":["545137a814af501a00b50cfd","545138eaa66f020800dbab4a","546b9072b47b5d1400109edf","546b9082b47b5d1400109ee0","546b9088b47b5d1400109ee1","546b909462515a14007ebc43","546b90a0b47b5d1400109ee2","546ced235884600e007a92f6","5481008eea7fd40b00cd7c2b","573b9d83ee2b3b220042291f","57be1efa15efc70e006a5f99"],"is_deprecated":false,"is_hidden":false,"is_beta":true,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"project":"545137a814af501a00b50cf9","__v":9,"updates":["5589db2e9883a40d00c4340d","57fbfa3e35c9ad0e00ac8a7e","5aa2fb7a5aa187006c95fb39","5aa2fbce8b7561001227296c"],"next":{"pages":[],"description":""},"createdAt":"2015-06-08T22:44:17.750Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":5,"body":"Only desktop browsers are supported with Yammer Embed at this time and Yammer Embed requires a [browser supported by Yammer](https://products.office.com/en-US/office-system-requirements#Browsers-section). See the Safari Cookie Support section in this doc for additional support information when using Safari.\n\n\n**Document Mode**\nInternet Explorer has a Document Mode feature which causes the browser to render the page as if it was running in an older version of IE. For the best experience with Yammer Embed, you should ensure the IE rendering mode for the page is set to \"edge\" mode.\n\n**Trusted Sites**\n\nInternet Explorer (all versions) may need to have Yammer URLs configured in the IE Trusted Sites zone.\nIn Internet Explorer security settings, add *.yammer.com and *.assets-yammer.com to the Trusted Sites zone. \n\n**Code Hosting**\n\nThe Yammer Embed code must be loaded from the Yammer CDN (*.assets-yammer.com) referenced in the documentation. Serving local copies of the Embed code to users is not supported because you will not be notified of updates, including security fixes, which are automatically deployed to the CDN.\n\n**Proxy and URL Whitelisting**\n\nIn some case you may need to allow additional URLs for Yammer through a firewall. Please refer to the [Yammer section](https://support.office.com/en-us/article/Office-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2?ui=en-US&rs=en-US&ad=US#BKMK_Yammer) of the O365 URLs and IP Address Ranges on TechNet.\n\n**Safari Cookie Support**\n\nSafari is much more restrictive when working with cookies. Any cookie that is solely created inside an iframe is considered a 'third party cookie' by Safari, and the browser will not send them with requests. This causes issues with our login flow, which uses cookies. This issue will show itself in a session where the user has never visited Yammer outside of the embed iframe. There are two potential workarounds:\n\na.) Have the user go to \"Safari Preferences >Privacy > Cookies and website data\" and set to \"Always allow\"\nb.) If the user is not using a private window, you can instruct them to open a new tab and navigate to Yammer.com. They do not have to login. Then return to the embed page and reload. \n\nEither workaround will fix the issue.","excerpt":"","slug":"requirements","type":"basic","title":"Requirements"}
Only desktop browsers are supported with Yammer Embed at this time and Yammer Embed requires a [browser supported by Yammer](https://products.office.com/en-US/office-system-requirements#Browsers-section). See the Safari Cookie Support section in this doc for additional support information when using Safari. **Document Mode** Internet Explorer has a Document Mode feature which causes the browser to render the page as if it was running in an older version of IE. For the best experience with Yammer Embed, you should ensure the IE rendering mode for the page is set to "edge" mode. **Trusted Sites** Internet Explorer (all versions) may need to have Yammer URLs configured in the IE Trusted Sites zone. In Internet Explorer security settings, add *.yammer.com and *.assets-yammer.com to the Trusted Sites zone. **Code Hosting** The Yammer Embed code must be loaded from the Yammer CDN (*.assets-yammer.com) referenced in the documentation. Serving local copies of the Embed code to users is not supported because you will not be notified of updates, including security fixes, which are automatically deployed to the CDN. **Proxy and URL Whitelisting** In some case you may need to allow additional URLs for Yammer through a firewall. Please refer to the [Yammer section](https://support.office.com/en-us/article/Office-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2?ui=en-US&rs=en-US&ad=US#BKMK_Yammer) of the O365 URLs and IP Address Ranges on TechNet. **Safari Cookie Support** Safari is much more restrictive when working with cookies. Any cookie that is solely created inside an iframe is considered a 'third party cookie' by Safari, and the browser will not send them with requests. This causes issues with our login flow, which uses cookies. This issue will show itself in a session where the user has never visited Yammer outside of the embed iframe. There are two potential workarounds: a.) Have the user go to "Safari Preferences >Privacy > Cookies and website data" and set to "Always allow" b.) If the user is not using a private window, you can instruct them to open a new tab and navigate to Yammer.com. They do not have to login. Then return to the embed page and reload. Either workaround will fix the issue.