Yammer Service Description
Yammer is a best-in-class, secure, and private enterprise social network. Yammer empowers employees to be more productive and successful by enabling them to collaborate easily, make decisions faster, and self-organize into teams to take on any business challenge. It's a new way of working that naturally drives business alignment and agility, reduces cycle times, engages employees, and improves relationships with both customers and partners.
For a list of Office 365 plans that include Yammer, see Office 365 service families and plans.
To compare features across plans, see Compare Office 365 for Business plans.
You can export, save, and print pages in the Office 365 Service Descriptions. Learn how to export multiple pages.
For system requirements for Office 365, the monthly subscription-based service available for business, education, and government organizations, please see Office 365 system requirements.
Yammer is available through the following plans:
||Enterprise social networking - anytime, anywhere.
||Enterprise social networking with advanced security, administration and integrations.
The features and policies described in the Office 365 Platform Service Description don't apply to the Yammer service.
Yammer Enterprise Service Communications Policy
Yammer is a part of Office 365 and adheres to the Office 365 Change Management policy, but does not use Targeted release to roll out updates.
All Yammer users are subject to A/B feature testing. This allows Microsoft to test features for stability, performance and experience improvement across many environments and devices. Users within the same network may have varying experiences due to testing. It is not possible for customers to opt out of A/B testing.
Any changes (A/B tests, new features, deprecations, compliance boundaries, workflow changes) that require customer action or are expected to have a significant impact on customers will be communicated in advance. We've identified a scenario where Yammer makes a change that impacts a limited subset of users. An example of this might be changing or removing a capability, such as the Yammer Chrome Extension, that has low engagement but which a small number of users have enabled. In these cases, we believe direct communication to these users in addition to the usual communication channels to Verified Admins as listed in the above policy will deliver a good user experience for the subset of users impacted by a change. For changes categorized as either "Changes Requiring Action (Plan for Change)" or "Changes Requiring Awareness (Stay Informed)" that only affect a targeted set of users, we may directly notify those users. The following table has been updated to reflect this change.
The channels used to communicate will depend on the impact:
|Changes Requiring Action (plan for change) Admin required to make changes to keep the service running, updates that may have an impact on your organization's compliance
||Office 365 Message Center Emails direct to Yammer Verified Admins Office 365 RoadmapYammer Service Updates External GroupWith changes that affect a targeted set of users, we may also notify those users directly.|
|Changes Requiring Awareness (stay informed) Changes that do not require admin action, visual design changes
||Office 365 Message Center Office 365 RoadmapYammer Service Updates External GroupWith changes that affect a targeted set of users, we may also notify those users directly.|
|Non-critical Changes that are non-critical and do not require action or awareness, even though they may be observable by some users
||Will not be communicated broadly.|
Feature availability across Yammer plans
Need help figuring out which Yammer plan best fits your organization's needs? Use the following table to see which features are available in each plan. Click a feature name to read a short summary of how that feature works in Yammer.
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.