Yammer SSO and DSync deprecation - FAQ

Yammer single sign-on (SSO) and directory synchronization (DSync) are being deprecated and will no longer work after December 1st, 2016. For more information about this deprecation and steps you can take to switch from using Yammer SSO and DSync to using the familiar Office 365 tools to setup single sign-on (Office 365 sign-in with federated identity) and directory synchronization (Azure Active Directory Connect), see Plan for Yammer SSO and DSync deprecation.

Q: What functionality is being removed from Yammer?

A: Yammer single sign-on (SSO) and Yammer directory synchronization (DSync) are being removed from Yammer. These were legacy tools developed by Yammer prior to being acquired by Microsoft. As Yammer improves its integration with Office 365, we are eliminating the need for customers to learn and maintain separate tools. Customers should transition to leveraging the familiar Office 365 tools to set up single sign-on (Office 365 sign-in with federated identity) and directory synchronization (Azure Active Directory Connect). For more information, see Plan for Yammer SSO and DSync deprecation.

Q: How is this change being communicated to customers?

A: Based on the Yammer Enterprise Service Communications Policy, this change has been communicated in each of the following channels to make customers aware:

  1. An update to documentation: Plan for Yammer SSO and DSync deprecation.

  2. A Yammer blog post: Enforcing Office 365 identity in Yammer now available

  3. An Office 365 Message Center posts for admins

  4. Yammer admin emails

  5. An announcement in the Yammer Office 365 Network: Enforce Office 365 Identity in Yammer is now available!

Q: When will Yammer SSO and DSync stop working?

A: Yammer SSO and DSync will stop working on December 1st, 2016. After April 1st, 2016, Yammer networks cannot set up new configurations or make significant changes to configurations of SSO or DSync. For more information, see Deprecation schedule for Yammer SSO and DSync.

Q: What is the recommended timeframe to change over to Office 365 sign-in?

A: For a smooth transition we recommend switching over to Office 365 sign-in as soon as practical for your organization, unless you are a user of one of the three scenarios listed below. To avoid user impact, you should complete your transition before December 1st, 2016 by taking the steps outlined in How to transition to using Office 365 sign-in for Yammer and Azure Active Directory sync. Users of the below features should review the Office 365 Roadmap to check when these will become available:

  • Per-user licenses:    The ability to use licensing to block Office 365 users from accessing Yammer.

  • User property sync:    Synchronizing user property changes from Office 365 into Yammer.

    Note:  One-time user property population for new users is available today.

  • User lifecycle:    Improvements to the existing user lifecycle functionality to suspend and block user access for users with accounts blocked in Office 365.

  • Multiple Yammer networks associated with one Office 365 subscription    Support for connecting one Office 365 subscription to multiple Yammer networks for login and user lifecycle management.

Q: What should I use instead of Yammer SSO and DSync?

A: Customers can use the familiar Office 365 tools to setup single sign-on (Office 365 sign-in with federated identity) and directory synchronization (Azure Active Directory Connect) instead of Yammer SSO and DSync. Follow the steps in How to transition to using Office 365 sign-in for Yammer and Azure Active Directory sync to switch to using these tools.

Q: What are the replacements for the various scenarios or behaviors Yammer SSO and DSync are used for?

A: If you are using Yammer SSO or DSync for specific scenarios or behaviors, please review the following: Yammer SSO scenarios and their replacement and Yammer DSync scenarios and their replacement.

Q: What do I need to do to transition to using Office 365 sign-in for Yammer and Azure Active Directory sync?

A: Follow the steps in How to transition to using Office 365 sign-in for Yammer and Azure Active Directory sync. Note that the Office 365 tool for sign-on can be configured by the customer (self-service) whereas Yammer SSO requires contacting the Yammer support team. Yammer networks that currently use Yammer SSO will need to transition to using Office 365 sign-in for Yammer. Before you begin, make sure all current Yammer users have a corresponding Office 365 identity (otherwise you could disrupt users’ access to Yammer).

Q: How do I enforce Office 365 identity in Yammer?

A: Before you begin, make sure all current Yammer users have a corresponding Office 365 identity (otherwise you could disrupt users’ access to Yammer). We recommend communicating this change to your users using the communication template provided in Start enforcing Office 365 identity in Yammer. Then it takes just a few steps to start enforcing Office 365 identity in Yammer. These steps can be found in the article: Enforce office 365 identity for Yammer users.

Q: Do I need to contact Yammer for switching over to Office 365 sign-in or Azure Active Directory Connect?

A: No, administrators can configure the Office 365 tool for sign-in themselves, rather than having to contact the Yammer support team.

Q: Is there an option to opt out of moving to Office 365 sign-in or Azure Active Directory Connect?

A: No, as Yammer integrates more tightly with Office 365, we are removing redundant tools that are unique for Yammer.

Q: What will happen if I do not take any action by December 1st, 2016?

A: If you do nothing by December 1st 2016, the following will no longer work:

  • Yammer SSO:    Yammer single sign-on will stop working. The network will start using Office 365 identity (if the network is associated with an Office 365 tenant) or legacy Yammer identity (log in with Yammer-specific username and password).

  • Yammer DSync:    Yammer directory synchronization will stop working. Changes made in your on-premises Active Directory will not be reflected in Yammer.

Q: If I run into issues, who should I contact?

A: Please follow your tenant’s normal process to open an Office 365 support request. See Contact Office 365 for business support.

Q: How do I know if I am impacted by this change?

A: Yammer verified admins will receive an email about being identified as a current user of the Yammer SSO or DSync features. Additionally, Office 365 Message Center communications have been sent out.

Q: Are there any special scenarios that I need to be aware of?

A: Yes, some customers will have additional steps to perform depending on how their current Yammer network is setup. Yammer admins will be able to identify which scenario applies to their network. These scenarios are:

  1. No Office 365 tenant is mapped to your Yammer network.

  2. One Office 365 tenant is associated with multiple Yammer networks.

  3. Multiple Office 365 tenants are associated with one Yammer network.

Please note that a Yammer network is associated with an Office 365 tenant if the domain on the network has been verified on the Office 365 tenant. The next question walks you through the steps you need to take if you one of the above scenarios applies to your environment.

Q: If I fall into a special scenario, what additional steps will I need to take?

A: Based on the scenario that applies, you will need to take the following steps:

  1. No Office 365 tenant is mapped to your Yammer network.

    Create a tenant and connect it to Yammer by following the steps in the Yammer Activation Guide.

  2. One Office 365 tenant is associated with multiple Yammer networks.

    If you have one tenant connected to multiple Yammer networks, we strongly recommend that you consolidate networks. You can see all the networks connected by visiting the Network Migration page. If, for some business reason, you cannot consolidate networks, you can still transition one of your Yammer networks to the single sign-on and DSync equivalents in Office 365 by activating Yammer in the domain associated with the network, while you wait for Office 365 to support multiple Yammer networks associated with one Office 365 subscription.

  3. Multiple Office 365 tenants are associated with one Yammer network.

    • Domains on your Yammer network have been associated with more than one Office 365 tenant. An Office 365 tenant is associated with the Yammer network if a domain on the network has been added as a verified domain on the Office 365 tenant.

    • To switch from Yammer SSO and DSync to Office 365 sign-in for Yammer, you will first need to take a special step to get to a state where all domains in each Yammer network map to exactly one Office 365 tenant. That step consists of choosing between these two options for each Yammer network they have:

      • Move all the domains in the Yammer network into a single Office 365 tenant.

      • Remove domains from the Yammer network, such that it shares domains with a single Office 365 tenant only. This will make any users with email addresses in the removed domains get their own separate Yammer network.

Q: Can I transition to using "Enforce Office 365 identity" on my network and still keep using the legacy Yammer DSync tool for user profile synchronization?

A: Microsoft recommends moving off of the deprecated Yammer DSync technology that will stop working on December 1, 2016. If you plan to move off of Yammer DSync but have an immediate business need, you can continue using legacy Yammer DSync tool (until December 1, 2016) for user profile synchronization together with Office 365 sign-in and the Enforce Office 365 identity switch.

Q: When we enforce Office 365 identify for Yammer, will all our Office 365 Tenant Admins also become Yammer Admins?

A: Yes, all Office 365 global admins will become Yammer admins once the Yammer network is mapped to the Office 365 tenant. Yammer admins, however, will not automatically become Office 365 global admins.

Q: How will enabling the "Enforce Office 365 identity" switch for Yammer affect guest users on our network?

A: Guests and external users follow the authentication method of their home network, not the one of the guest network they are also part of. This is the same behavior Yammer SSO followed, so no disruption should happen here. Only users homed in your own network will be affected by the Enforce Office 365 identity setting in your network.

Q: We use Yammer SSO and Active Directory Federation Services (AD FS) to authenticate users and we have a rule to block specific users based on Active Directory attributes. If we were to enforce Office 365 identities, could we continue to prevent specific users from accessing Yammer?

A: Please review the Office 365 Roadmap to confirm when we will be delivering per-user licensing for Yammer. Combined with enforcing Office 365 identity, per-user licensing will allow you to block users from Yammer the same way other Office 365 services do. More details on per-user licensing will be released as we get closer to the release.

Q: How quickly does the change in settings to switch over to Office 365 sign-in with federated identity take place?

A: The cutover is immediate, there are no delays and no downtime. If the option to Log out all current users is selected, then that is also applied immediately and users will need to log in again with Office 365 identities when they return to Yammer.

Q: When the cutover happens, will the data sync between Yammer and Active Directory change?

A: No. When you provision new users, that process will bring their properties from Azure Active Directory and Office 365 into Yammer.

Q: Are there certain users that will not be able to use Yammer?

A: Users in Office 365 can access Yammer directly, or by using Office 365 if they have a license assigned. In the 1st quarter of 2016, Yammer will offer an admin option to enable blocking unlicensed users from accessing Yammer. When this mode is enabled, any users who do not have an assigned Yammer Enterprise license in their Office 365 tenant will not be able to use Yammer. Licenses are available with many plans such as: Office 365 Enterprise E3, Yammer Enterprise Standalone, and so on.

Q: Can administrators control invitation emails for networks when Office 365 sign-in is enabled?

A: No. Administrators cannot control email invitations sent to users. With Yammer DSync it was possible to customize the content invitations emails sent by that tool, but all other invitations used the system format. With Office 365 sign-in and Azure Active Directory provisioning, all email invitations are sent in the system format, and any Yammer DSync customizations no longer apply unless the user was invited by DSync.

Yammer DSync supported a custom welcome message displayed to users in the Yammer site when they accepted an invite from DSync. Office 365 sign-in has an improved initial experience for users, and this custom welcome message is only displayed if the user clicks through an invite from DSync.

Q: Where can I get more information?

The following resources are available with more information:

Share Facebook Facebook Twitter Twitter Email Email

Was this information helpful?

Great! Any other feedback?

How can we improve it?

Thank you for your feedback!

×