Manage the Yammer service in Office 365

When Yammer was a stand-alone service, there were Yammer-specific solutions to core aspects of the service; these were different from Office 365. For example, users logged in to the Yammer service using their email and password, administrators set up single sign-on solution with a tool called Yammer SSO, and called Yammer support to manage domains in Yammer. As Yammer seamlessly integrates with Office 365, administrators can manage key aspects of the Yammer service in Office 365, including identity, domain and license management. This is similar to how administrators manage other core Office 365 services. So, we strongly recommend that Yammer administrators learn about Office 365 administration and partner with Office 365 administrators to effectively manage Yammer.

Key benefits

Familiar procurement experience:    Office 365 is the popular cloud productivity solution from Microsoft with millions of users. Yammer is included in most of the Office 365 subscriptions, making it easier for customers to procure Yammer. As of February 1, 2016, Yammer is on by default in Office 365, and the Yammer service is automatically provisioned for every Office 365 tenant with a Yammer subscription. Say, customers sign up for a trial of Office 365 Enterprise E5 subscription, they automatically get Yammer provisioned without any additional steps. Also, Yammer will be activated for every eligible Office 365 tenant allowing Office 365 customers to seamlessly gain the full benefits of Yammer.

Familiar and powerful management experience:    Office 365 is built on  Azure Active Directory (Azure AD), Microsoft's multi-tenant cloud based directory and identity management service. Office 365 and Azure AD provide powerful tools for organizations, including a full suite of identity management capabilities (including multi-factor authentication, role based access control), ability to connect with your on premises directory service (enabling single sign on, user lifecycle management) and centralized user and license management (with powerful scripting capabilities). This lets administrators to manage Yammer just like other Office 365 services, and also provides powerful tools that were not available when Yammer was managed as a stand-alone service.

Compliance:    Organizations benefit from the industry-leading control, security and privacy  commitments of Office 365 when they are using Yammer—enabling collaboration to take place against a backdrop of trust. Yammer is now covered by the Office 365 Trust Center, which offers the protection of international and regional standards.

Seamless user experience with Office 365:    As you manage Yammer and other services in Office 365, you increasingly care about how effectively these services are used in your organization and that core experiences (like sign-in) are consistent, thereby reducing user confusion and internal support requests. In this context, it is important for the service to be seamlessly integrated with the Office 365 experience. For example, every Office 365 user who has a Yammer license will be able to easily access Yammer from the Office 365 app launcher or start a Yammer conversation from SharePoint, the Office 365 Video Portal and, coming soon, Delve and Skype Broadcast. This ensures that users get maximum value out of Yammer as part of Office 365.

Manage Yammer in Office 365

Below is a list of key capabilities, how the capability was addressed by Yammer as a stand-alone service, and how it's now addressed as part of Office 365. You can see that Yammer is a core service of Office 365, and can be managed seamlessly from Office 365, similar to other services.

Capability   

Yammer managed as a stand-alone service   

Yammer managed as part of Office 365   

Yammer availability in Office 365 tenants

Office 365 administrator performs Yammer Enterprise activation.

Yammer is seamlessly activated.

Login

Users sign-in with their email and password.

Users can sign-in to Yammer with their Office 365 credentials.

Single sign-on

Configured using Yammer SSO. This will be deprecated on Dec 1, 2016.

Configured using Azure AD Connect with the Enforce office 365 identity setting configured for the Yammer network.

User lifecycle management

Configured using Yammer DSync. This will be deprecated on Dec 1, 2016.

Configured using Azure AD Connect. Coming soon - user profile properties from Azure AD will be automatically updated in Yammer. Learn more about managing Yammer users across their life cycle from Office 365.

Administrator lifecycle management

Manually add administrators to Yammer.

Office 365 Global administrators are automatically synchronized to Yammer.

License management

Manually reconcile licenses with Yammer users.

Manage Yammer user licenses in Office 365

Domain lifecycle management

Call Yammer support to add or remove domains.

When you manage Yammer domains in Office 365, domains are automatically synchronized to Yammer.

Consolidate free Yammer basic networks

Call Yammer support to consolidate networks.

Use the self-service network migration wizard to consolidate networks.

Yammer networks and Office 365 tenants

As Yammer evolves from being a stand-alone service to being part of Office 365, the role of a Yammer network has evolved as well. Also, Yammer service procurement, management and end-user experiences are seamlessly integrated with Office 365. So, it is important for customers who had created stand-alone Yammer networks in the past to learn how Yammer can be managed as a service in Office 365. Also, for the best end-user and management experience, it is recommended that one Office 365 tenant is associated with just one Yammer network - if you are not in this configuration, we recommend you consolidate your networks/tenants to move to this state. To learn more, read About Yammer networks and Office 365 tenants.

Frequently-asked questions about managing Yammer in Office 365

Yammer Basic

Q: As Yammer is closely integrated with Office 365, can I still sign up for a free Yammer network?

A: Yes. You can still sign up for the free Yammer basic offer at www.yammer.com by entering your email and clicking on the Sign up button (as long as the domain was not verified on an Office 365 tenant that has a Yammer subscription). When you are ready to use the Enterprise features of Yammer (such as the ability to manage users or setup single-sign-on) you need to create an Office 365 tenant.

Yammer administrator lifecycle management

Q: How can I manage Yammer administrators in Office 365?

A: Any Office 365 user who is assigned a Global Admin role will be also made a Verified Admin in Yammer. When this role is removed from a user, their verified admin privileges on Yammer would also be removed.

  • 1 tenant to 1 network configuration: If the Office 365 tenant has more than 1 domains, all those domains will be synchronized with the Yammer network. And all the Global Admins on the Office 365 tenant (associated with any of the domains), will be synchronized to Yammer as well.

  • 1 tenant to many network configuration: If the Office 365 tenant has more than 1 networks associated with it, Global Admins on the Office 365 tenant will be synchronized to the Yammer network they are eligible to login to (see the Login section under the 1 tenant: many networks scenario for more details).

  • Many tenants to 1 network configuration: This is not a supported configuration. Global admins from the Office 365 tenant that was activated last will be synchronized to Yammer.

Yammer activation

Q: What exactly happens during Yammer activation?

A: Yammer activation connects the Office 365 tenant to the Yammer service, and happens automatically (more information in Yammer integration with Office 365). There are two key effects of Yammer activation.

  • Office 365 tenant is connected to the Yammer network for management: This includes upgrading the network to an Enterprise network (if needed) and starting Administrator Lifecycle management, so that the Office 365 Global Administrators can login to the Yammer network.

  • Office 365 tenant connected to the Yammer network for login: This enables users to login to the Yammer network with their O365 credentials.

Activation and existing network

Q: My company has a Free Yammer basic network on the contoso.com domain. My company also has an Office 365 tenant, to which we have verified and added contoso.com. When Yammer is activated automatically on our Office 365 tenant, will it create a separate network?

A: No. When Yammer is activated on an Office 365 tenant, we look for any existing Yammer networks, and connect the Office 365 tenant to the existing network, instead of creating a new network. In this case, the free contoso.com Yammer network will be upgraded to Yammer Enterprise and connected to the Office 365 tenant.

Activation and existing login

Q: My company has an active Yammer network and we login using our email and password. Our company has started adopting Office 365, but not all our user accounts have been created yet. As Yammer integrates closer with Office 365, will we be blocked from logging in with our email and password?

A: No. By default, Yammer supports login with either Office 365 credentials, or with email and password. If a user has a corresponding Office 365 account, the user will be prompted to login with their Office 365 credentials. But if they don't have a corresponding Office 365 account yet, they can continue to login with email and password. Also note that the Yammer administrator may optionally choose to Enforce office 365 identity in Yammer - this single-sign-on configuration forces everyone to login with their Office 365 credentials.

Activation and existing users

Q: I am an existing user of a Yammer network and login with my email and password. Once my network is connected to Office 365, will I get a new Yammer user account?

A: No. When you login for the first time using your Office 365 credentials, after successful login, we will try to match the email of the Office 365 account to an existing user. If we can't find one, we will create a new Yammer user. For more information read the article Office 365 sign-in for Yammer.

Domain lifecycle management

Q: My company is trying out an Office 365 trial subscription - our Office 365 account is contoso.onmicrosoft.com, and we have a corresponding Yammer network. Now we plan to verify and add the contoso.com domain, will that create a second Yammer network?

A: No. When you add the contoso.com domain to the tenant, it will be automatically added to the contoso.onmicrosoft.com network that was previously created. And users with contoso.com emails can start logging in to the same network.

Consolidating Yammer basic network

Q: My company has an Office 365 tenant with contoso.com domain in it - and we actively use the corresponding contoso.com Yammer network. Now we want to add our subsidiary domain tailspin.com to the same tenant, but discovered that tailspin.com has a separate free Yammer basic network. We want tailspin.com to start using the parent network, with its usage policies - is this possible?

A: Yes. You can use the self-service network migration wizard to consolidate the tailspin.com subsidiary network into the contoso.com parent network.

Moving Yammer data between Office 365 tenants

Q: My company has a tenant with contoso.com domain in it - we actively use the corresponding contoso.com Yammer network. We acquired tailspin.com which also has an Office 365 tenant and a Yammer network. Now we want to move the tailspin.com Yammer network into the contoso.com tenant - is this possible?

A: No. You can't move Yammer network between tenants, since the network is closely tied to Office 365 (domains, users, identity are all connected). Currently, you can Export data from the network of the acquired company for compliance purposes. When you move the domain tailspin.com to the contoso.com tenant, the tailspin.com domain will be automatically added to the contoso.com network. When the tailspin.com users are created on the contoso.com tenant, these users will be able to login to the network as new users.

Note that moving Yammer data between Office 365 tenants is different from self-service network migration of Yammer basic networks (which are not connected to Office 365).

When Yammer is part of Office 365, it is tightly integrated with Office 365 with the following implications:

  • Domain lifecycle:    When you remove a domain from an Office 365 tenant, the domain on the network will automatically be removed.

  • User lifecycle:    When you delete the user from an Office 365 tenant (before you remove the domain), the user is also deleted form Yammer.

  • Identity:    All users from the original tenant needs to move over to the new tenant.

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!

×