{"_id":"581cdaa8bb096b0f002e61d1","user":{"_id":"5638f69b22afbc0d001f23c1","username":"","name":"Yammer Platform DL"},"__v":0,"project":"545137a814af501a00b50cf9","initVersion":{"_id":"545137a814af501a00b50cfc","version":"1.0"},"createdAt":"2016-11-04T18:59:52.721Z","changelog":[],"body":"Now that we are approaching December 1, 2016 -- the deprecation date in [last year's announcement](https://support.office.com/en-us/article/Plan-for-Yammer-SSO-and-DSync-deprecation-847366a4-30c8-49d1-94cc-9d2452f6d43a)  -- a few developers have asked if this will impact their clients' ability to access their apps/integration.  The quick answer is \"no.\" The more detailed answer: As long as your integration uses the Yammer auth flow, your clients will continue to have access. At most, users may need to \"allow\" your app's auth permission again as the switch to O365 identity causes tokens issued through Yammer identity to be invalidated. \n\nWhen enforcing O365 Sign-In, admins have the option to sign all users out, so the invalidation may happen at one time rather than gradually. A few recommendations to help your clients with a smooth transition:\n\n1) Review your integration to ensure a graceful handling of invalid tokens.\n\n2) Ensure that your Yammer network is activated on an Office 365 tenant and [users can login to Yammer using their Office 365 credentials](https://support.office.com/en-us/article/Office-365-sign-in-for-Yammer-b1745e3c-d4d7-4e20-a155-ebf85106b998) . To test your applications with a full range of scenarios, you can sign up for [an Office 365 trial subscription that includes Yammer](https://products.office.com/en-us/business/office-365-enterprise-e5-business-software). \n\n3) For Yammer Embed, your clients may need to add [Yammer fully qualified domain names (FQDNs)](https://support.office.com/en-us/article/Office-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2#bkmk_yammer) to their Trusted Sites for Internet Explorer, if they've already had to modify Trusted Sites in the past. Your clients may have a very specific configuration dependent on their environment.\n\nThanks for asking!","slug":"reminder-yammer-sso-deprecation","title":"Reminder: Yammer SSO Deprecation"}

Reminder: Yammer SSO Deprecation


Now that we are approaching December 1, 2016 -- the deprecation date in [last year's announcement](https://support.office.com/en-us/article/Plan-for-Yammer-SSO-and-DSync-deprecation-847366a4-30c8-49d1-94cc-9d2452f6d43a) -- a few developers have asked if this will impact their clients' ability to access their apps/integration. The quick answer is "no." The more detailed answer: As long as your integration uses the Yammer auth flow, your clients will continue to have access. At most, users may need to "allow" your app's auth permission again as the switch to O365 identity causes tokens issued through Yammer identity to be invalidated. When enforcing O365 Sign-In, admins have the option to sign all users out, so the invalidation may happen at one time rather than gradually. A few recommendations to help your clients with a smooth transition: 1) Review your integration to ensure a graceful handling of invalid tokens. 2) Ensure that your Yammer network is activated on an Office 365 tenant and [users can login to Yammer using their Office 365 credentials](https://support.office.com/en-us/article/Office-365-sign-in-for-Yammer-b1745e3c-d4d7-4e20-a155-ebf85106b998) . To test your applications with a full range of scenarios, you can sign up for [an Office 365 trial subscription that includes Yammer](https://products.office.com/en-us/business/office-365-enterprise-e5-business-software). 3) For Yammer Embed, your clients may need to add [Yammer fully qualified domain names (FQDNs)](https://support.office.com/en-us/article/Office-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2#bkmk_yammer) to their Trusted Sites for Internet Explorer, if they've already had to modify Trusted Sites in the past. Your clients may have a very specific configuration dependent on their environment. Thanks for asking!