[null, {"document_url": "https://support.office.com/en-gb/article/Enforce-Office-365-identity-for-Yammer-users-008f940b-6bec-47fc-bcc6-9c6133467562", "unformatted_src": "https://support.content.office.net/en-us/media/9e32ab1b-fc3a-4839-b2da-7be1229c339b.png", "src": "https://support.content.office.net/en-us/media/9e32ab1b-fc3a-4839-b2da-7be1229c339b.png", "formatted_filename": "e ab b fc a b da be c b", "alt_text": "When a user logs in, they first enter their email address. If Office 365 identity is enforced, they log in with their Office 365 identity. If it is not enforced, but their email is in Office 365, then they log in with their Office 365 identity. If it is n"}, null, {"document_url": "https://support.office.com/en-gb/article/Enforce-Office-365-identity-for-Yammer-users-008f940b-6bec-47fc-bcc6-9c6133467562", "unformatted_src": "https://support.content.office.net/en-us/media/2402bc0f-f2ac-435f-bdb3-be65dbf2d153.png", "src": "https://support.content.office.net/en-us/media/2402bc0f-f2ac-435f-bdb3-be65dbf2d153.png", "formatted_filename": "bc f f ac f bdb be dbf d", "alt_text": "Screenshot showing a Verified Admin account that is synced as a Global Administrator in Office 365"}, null, {"document_url": "https://support.office.com/en-gb/article/Enforce-Office-365-identity-for-Yammer-users-008f940b-6bec-47fc-bcc6-9c6133467562", "unformatted_src": "/Images/SOC-Facebook.png", "src": "https://support.office.com/Images/SOC-Facebook.png", "formatted_filename": "SOC Facebook", "alt_text": "Facebook"}, {"document_url": "https://support.office.com/en-gb/article/Enforce-Office-365-identity-for-Yammer-users-008f940b-6bec-47fc-bcc6-9c6133467562", "unformatted_src": "/Images/SOC-Linkedin.png", "src": "https://support.office.com/Images/SOC-Linkedin.png", "formatted_filename": "SOC Linkedin", "alt_text": "LinkedIn"}, {"document_url": "https://support.office.com/en-gb/article/Enforce-Office-365-identity-for-Yammer-users-008f940b-6bec-47fc-bcc6-9c6133467562", "unformatted_src": "/Images/SOC-Mail.png", "src": "https://support.office.com/Images/SOC-Mail.png", "formatted_filename": "SOC Mail", "alt_text": "Email"}, null]


Enforce Office 365 identity for Yammer users

Applies To: Office 365 Admin More... Less

As Yammer becomes a core service for your organization, you’ll want users to be able to log into it seamlessly, just like any other Office 365 service. Additionally, you’ll probably want to maintain a single identity for all Office 365 users for easier user management. You can achieve both of these goals by enforcing Office 365 identity in Yammer. By enforcing Office 365 identity in Yammer and configurating federated identity for Office 365, admins can achieve single sign-on (SSO) capabilities for all services in Office 365, including Yammer.

How enforcing Office 365 identities in Yammer works

The following flowchart shows what happens when a user logs in to Yammer. Below is the user’s login experience when Office 365 identity is and is not enforced for Yammer:

The following table compares the user login behavior when Office 365 Identity is enforced or not enforced. Note that Office 365 identity is not enforced by default.

Start enforcing Office 365 identity in Yammer

It takes just a few steps to start enforcing Office 365 identities in Yammer. However, turning this setting on can accidentally disrupt users’ access to Yammer. So before you begin, do the following to make sure your Yammer users can continue working smoothly:

You must be a global administrator on Office 365 who was synchronized to Yammer as a Verified Admin to perform these steps. To check if your account was synchronized, you can go to the Network Admin page on Yammer and check the Admins section. Global administrators will sync to Yammer only if their user principal name (UPN) in Office 365 matches a domain on Yammer. The following screenshot shows what a synced admin looks like on the Admins page in Yammer. If you are ready to enforce Office 365 identity in Yammer, follow the steps below.

To start enforcing Office 365 identity in Yammer

Stop enforcing Office 365 identity in Yammer

When you stop enforcing Office 365 identities in Yammer:

If you no longer want to enforce Office 365 identities, you can follow the steps below to stop. You must be both a Yammer verified admin and an Office 365 global administrator to perform these steps.

To stop enforcing Office 365 identity in Yammer


Q: Once Office 365 Identity Enforcement is set to 'Committed Enforcement', why can't I revert it back?

A: Once your organization has committed to enforcing Office 365 identity and has one Office 365 tenant associated with a single Yammer network, connected groups will be enabled for this network.. In this configuration, whenever a group is created in Yammer,  a connected Office 365 group is also created, and users can take advantage of tools like SharePoint, Planner and OneNote connected to the group. At this point, reverting the 'Enforce Office 365 Identity' setting will be disruptive to the user experience, since users who login with their user names and passwords cannot access these connected resources any more.

Q: How will this change impact guest and external users?

A: Guests and external users will continue to follow the login settings and requirements of their home network, and will be unaffected. This is the same behavior Yammer SSO followed.

Q: How long does it take for this setting to be applied?

A: Enforce Office 365 Identity is applied immediately after the setting is set.

Q: We use the same ADFS configuration in Yammer and Office 365. Should we log users out during the transition?

A: Yes. Logout ensures all users logged in after that are connected to their Office 365 identity, which connects users for user lifecycle management from Office 365 and also provides a consistent experience for them, with things like Office 365 suite navigation.

Q: What is the experience for users being logged-out when enforcing Office 365 identities?

A: Users will be logged out of their web and mobile sessions immediately and will be required to login in all their devices and browser sessions again, this time using their Office 365 identity configuration and credentials.

Q: How can I audit and clean up Yammer users when compared to Office 365 and Azure AD?

A: You can audit Yammer users in networks connected to Office 365 and take appropriate actions based on it. See more information and examples in How to audit Yammer users in networks connected to Office 365. Get new features first
Join Office Insiders

