Integrate a Yammer network into SharePoint Server with social features

APPLIES TO: yes2013 yes2016 yes2019 noSharePoint Online

This scenario describes the prerequisites and recommended steps to integrate a Yammer network together with the SharePoint Server environment where you already use SharePoint social features.

Scenario prerequisites

For this scenario, we assume that:

  • You have SharePoint Server 2019, SharePoint Server 2016 or SharePoint Server 2013 SP1 or later installed.

  • Users already use the SharePoint Server Newsfeed social feature.

  • You're ready to switch to your Yammer network.

Scenario challenges

Many organizations already use social features in their SharePoint Server installation and have active and engaged communities that use these features. If you're ready to move towards Yammer, you have to manage both the technical implementation and the migration of users from one system to another.


There are no tools or processes available to help you move content from a Community Site to a Yammer Group. Going forward, you can keep the data in a Community Site and put a link on the SharePoint Community Site that points to the Yammer group where future discussions will occur.

Some communities might not want to immediately move to Yammer Groups. It's okay to let them continue to use the Community Site.

For new or old team sites, there's no option to automatically enable Yammer. Each site owner has to add Yammer using Yammer Embed or another custom integration. For information about how to use Yammer Embed to add a Yammer feed to a SharePoint page, see Add the Yammer embed widget to a SharePoint page.

SharePoint Server 2013

A common problem in SharePoint Server 2013 installations is that social features don't work across multiple farms. When you move to a single Yammer network, you eliminate this problem.

Many customers have active SharePoint Communities based on the Community Site Collection template. After you deploy SharePoint Server 2013 SP1, the Community Site Collection template is still available to use. A Community Site resembles a Yammer Group. We recommend that you have the users in these sites start conversations in new Yammer Groups. By using a Yammer Group, a community can share information, ask questions, and seek answers to problems.

Step 1: Set up directory synchronization

Office 365 uses Azure Active Directory for identity management, and Yammer Enterprise can be set up to Enforce Office 365 identity for Yammer users. If you're using an on-premises directory, in order to manage users in one place, you need to sync your on-premises directory with Azure Active Directory by using Azure Active Directory Connect.

For more information, see Plan for directory synchronization for Office 365 and Integrate your on-premises directories with Azure Active Directory.

Step 2: Disable default SharePoint Server social features

After you set up directory synchronization, disable the default SharePoint Server social features.

Step 3: Use Yammer Embed

After you disable the default SharePoint Server social features, use the Yammer embed widget to include Yammer feeds on SharePoint pages.

See also


Integrate Yammer with on-premises SharePoint Server environments

Social scenarios with Yammer and SharePoint Server

Other Resources

Integrate Yammer with other applications

Yammer - Admin Help