With Yammer on your PC, Mac, or mobile device, you can: Connect and engage across your organization. Tap into the knowledge of others. Use your Inbox to view, prioritize, and manage the most important messages and announcements.
When you assign user licenses as part of a bundled Office 365 subscription plan such as Office 365 Enterprise E3, the Yammer license is automatically assigned to the user. You can remove or assign Yammer licenses for specific users in the Microsoft 365 admin center or by using Windows PowerShell cmdlets for Office 365.
You can block users who don't have Yammer licenses from accessing Yammer by turning on the security setting Block Office 365 users without Yammer licenses (see Start blocking users who don't have Yammer licenses).
You need to be an Office 365 global administrator or user management administrator to do the following operations.
Only users with a Yammer license will see a Yammer tile in the Office 365 app launcher.
You assign or remove the Yammer license to users the same way you assign any other Office 365 Enterprise E3 license.
See Assign licenses to users in Office 365 for business and Remove licenses from users in Office 365 for business for more information.
You can use cmdlets in Windows PowerShell to assign Office 365 licenses. With Windows PowerShell, you can more easily see who has a license, and assign licenses for multiple users at the same time. For more information, see Use Office 365 PowerShell to assign licenses to user accounts. You can also bulk update licenses based on a CSV file. For more information, see Bulk license assignment to Office 365 users based on CSV.
Below are some example Windows PowerShell script snippets that you can use to manage Yammer licenses. Use them to develop a complete script for your organization.
The following example assigns a license from the litwareinc:ENTERPRISEPACK (Office 365 Enterprise E3) licensing plan to the unlicensed user belindan@litwareinc.com.
The following example unassigns the Yammer Enterprise license from the litwareinc:ENTERPRISEPACK (Office 365 Enterprise E3) to the user belindan@litwareinc.com.
If you'd instead like to enable Yammer for a user without affecting anything else in their license, you can run the above script but change:
to
The following example returns information about any users who are not currently licensed for Office 365.
It takes just a few steps to start blocking Office 365 users who don't have Yammer licenses. 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:
Make sure that you have turned on the setting to enforce Office 365 identity for Yammer users. You can assign or unassign Yammer licenses only to Yammer users who are managed in Office 365. So, to block Office 365 users without Yammer licenses, it is required that all Yammer users are managed in Office 365. The setting Block Office 365 users without Yammer licenses can be turned on only when the Enforce office 365 identity for Yammer users setting is turned on.
Make sure all current Yammer users have a Yammer license. When you start blocking Office 365 users without Yammer licenses, any user without a Yammer license will be unable to access Yammer. So before you begin, make sure that all of your current Yammer users have Yammer licenses. One method to check this is to go to the Export Users page in Yammer and export all users. Then compare that list to the list of users in Office 365 and make any changes required. For more details, see the article How to audit Yammer users in networks connected to Office 365.
Tell your users about this change. We strongly recommend that you tell users that you are starting to block Office 365 users without Yammer licenses, because it can disrupt their day to day usage of Yammer.
You must be a global administrator on Office 365 who was synchronized to Yammer as a verified admin to perform these steps.
If you are ready to block users who don't have Yammer licenses, follow these steps.
In Yammer, go to the Network Admin section, and choose Security Settings.
In the Security Settings page, go to the Enforce Office 365 Identity section, select the Enforce Office 365 identity in Yammer checkbox and confirm the selection. Enforcing Office 365 identity is a pre-requisite step to block users without Yammer licenses.
After the Enforce Office 365 identity in Yammer checkbox is selected, the Block Office 365 users without Yammer licenses checkbox will be available. Select the Block Office 365 users without Yammer licenses checkbox and then choose Save.
You see a confirmation message that asks if you are ready to start blocking Office 365 users without Yammer licenses.
The confirmation message shows the number of active users on the Yammer network. Make sure all the current Yammer users have Yammer licenses. For more details, see How to audit Yammer users in networks connected to Office 365.
If you want, you can automatically log out all current users, so that you can be sure that everyone using the Yammer service has logged in with their Office 365 identities and have a Yammer license. If you choose to do this, select the Log out all current users checkbox. We strongly recommend doing this at a time of minimal user activity (because users might be logged out in the middle of their work) and communicate it to them ahead of time.
If you are ready to start blocking Office 365 users without Yammer licenses, select Yes, I am ready to confirm your choice. This returns you to the Security Settings page where the Block Office 365 users without Yammer licenses checkbox is now selected.
Choose Save to save all your settings on the page.
If you don't choose Save but instead navigate away from the page, your settings will not take effect.
A: Per-user licenses let you assign Yammer to a subset of users in your company - typically for a geographical or team-by-team rollout. Only users with a license can see the Yammer tile in the Office 365 app launcher.
A: Licenses are enforced only for users who sign-in with Office 365 identity.
A: You can Enforce Office 365 identity for all your Yammer users.
A: You can export your list of users from Yammer and check for users who are not in Office 365. For more information, see Audit Yammer users in networks connected to Office 365.
-->If your Yammer network is eligible, you can use Microsoft 365 connected groups in Yammer.
You can tell if a group in Yammer is a Microsoft 365 connected group when you see the Microsoft 365 Resources section in the right navigation of the Yammer group:
Microsoft 365 connected groups have many advantages over non-connected Yammer groups:
To use Microsoft 365 connected groups in Yammer, make sure your Yammer network meets the following requirements:
You must enforce Office 365 identity for Yammer users. When you first enforce Office 365 identity there is a seven-day trial period, after which the Status of your Office 365 Identity Enforcement changes to Committed.
Since October 16, 2018, all Yammer networks must be in a 1:1 network configuration. This means you have one Yammer network that is associated with one Office 365 tenant. This is required as of October 16, 2018. For more information, see FAQ: Consolidating multiple Yammer networks.
Note
If you want to ensure that all of your groups are connected, please align your network to Native Mode. To learn more about Yammer in Native Mode, see Overview of Native Mode.
Here's how the process works after your network becomes eligible for connected groups:
About 24 hours after the Status in Office 365 Identity Enforcement changes to Committed:
In the Microsoft 365 (previously known as Office 365) Connected Yammer Groups section, the Status for your network will change to Enabled.
Any new groups created in Yammer that are eligible will automatically be created as Microsoft 365 connected groups.
After about one week, existing eligible groups will be converted to Microsoft 365 groups.
For a group to be eligible, the following criteria must be met:
The group owner must have Microsoft 365 group creation privileges. By default, all Microsoft 365 users have this privilege.
The group must be a public or private internal group. Unlisted private groups and external groups can't be Microsoft 365 connected groups.
The group must have an owner, and it must have members.
When you create a Microsoft 365 connected group from Yammer, in addition to your regular Yammer group features, the new Microsoft 365 group is created, and a new SharePoint site and document library, OneNote notebook, and Planner are created for the group. These resources can be accessed from the Yammer group page in Yammer.
If your network has the Yammer files stored in SharePoint feature that began rollout in December 2018, new files added to the group are stored in SharePoint. To see where Yammer files are stored for your network, go to How do I tell where my Yammer files are stored?
Important
If you create a Microsoft 365 group from any other app such as Outlook, it will not include Yammer. To have the connected group include Yammer, you must create the group in Yammer.
When your group is a Microsoft 365 connected group, you can manage many aspects of your group through the Microsoft 365 admin center, in addition to managing them through Yammer as discussed above. All groups from Yammer networks that are in Native Mode will be manageable through these admin centers. Some of the management capabilities that can be done through the Microsoft 365 admin center include:
In a connected group set up from Yammer, you can have group conversations in Yammer or in Outlook. You can send an email to a group in Yammer and it will appear in the group's Yammer messages, or use the group's name from the Outlook global address list (GAL) to send email to the group that goes directly to Outlook.
Your company can continue to use groups in Yammer and groups in Outlook based on which group type better fits the scenario for a team.
Email notifications for Yammer messages may be sent to users depending on the preferences that they have set in their Yammer notification settings. This applies both to connected and non-connected groups.
Yammer's integration with Microsoft 365 Groups started in 2017. Subsequent phases will address remaining groups types and deliver integration with Outlook calendar and enhancements for SharePoint and Planner. The best place to stay informed of change management is to follow the Yammer updates on the Microsoft 365 Roadmap.
A: In the Yammer admin center, go to Network Admin > Security Settings. In the Microsoft 365 (previously known as Office 365) Connected Yammer Groups section, the status for your network will show as Enabled.
A: No, but you can Manage who can create Groups. These restrictions do not apply to tenant admins.
A: No. Groups created by people who you have restricted from creating Microsoft 365 groups will not be Microsoft 365 connected.
A: No. The Microsoft 365 connected Yammer groups experience will work only for Office 365 tenant that is associated with a single Yammer network. See Network migration: Consolidate multiple Yammer networks for information on how to consolidate your Yammer networks. This is required for all Yammer networks as of October 16, 2018.
A: No, but you can [Manage who can create Groups, which will also apply to the conversion of existing groups. Only groups with at least one admin with group creation privileges can be connected to Microsoft 365.
If you apply new a creation policy, this will not retroactively change groups that are already connected to Microsoft 365. This will only impact new groups moving forward.
A: When your network first becomes eligible for connected groups, all groups that meet the criteria are converted to connected groups. After that, if a group that wasn't eligible becomes eligible, for example if your network has Microsoft group creation policies applied and you add a group admin with group creation permission, the group is not automatically connected. To have a group connected, you can submit a support request to have all eligible groups in your network connected.
A: Currently, only private and public internal groups can be connected groups. External groups and private-unlisted groups will be included in a later wave.
A: No. That setting is not available for Microsoft 365 connected Yammer groups.
A: No, a new group and resources specific to that new group are created when you create a Microsoft 365 connected group in Yammer. You can't connect a new Yammer group to an existing Microsoft 365 group, an existing SharePoint site or SharePoint document library, or an existing OneNote notebook.
A: Yes. This requires using PowerShell. Use the following cmdlet:
Set-UnifiedGroup -Identity [group_name] -HiddenFromAddressListsEnabled $true
For more information about Set-UnifiedGroup, see Set-UnifiedGroup.
A: Microsoft 365 connected Yammer groups can only be created in Yammer. Microsoft 365 groups created in other locations do not include a Yammer group.
A: No, this will be added in later waves. However, for Microsoft 365 connected Yammer groups, you can manage members and delete groups from the Microsoft 365 admin center. Metadata updates can also be applied to groups from the admin center.
A: No. This will cause a sync failure because external users are not managed by Azure AD.
A: More than 1,000.
A: All the associated Microsoft 365 content associated with the group is deleted. This includes the document library, OneNote notebook and Planner plans. These resources are soft-deleted, and can be restored by your administrator for up to 30 days.

For more information about deleting a community or group, see Delete a community or group in Yammer.
A: Yes. When a Microsoft 365 group is deleted because it expired, the Yammer group is deleted.
A: Yes. Any Microsoft 365 connected Yammer group can be converted to dynamic membership. See Create a dynamic group for requirements and limitations.
A: No, these are separate locations to store files but the members of the group have access to both locations. Files attached to Yammer messages or uploaded in a Yammer Files page are stored in Yammer cloud storage, and files uploaded directly to the groups SharePoint document library are stored in SharePoint.
We recommend storing content that needs the structure and management capabilities of SharePoint in the group document library. For easy, quick sharing of images and documents, or to stream videos in Yammer, we recommend continuing to use the default Yammer cloud storage.
Note
As of December 2018, we are in process of rolling out Yammer files stored in SharePoint. When your network gets this new feature, new files uploaded to Yammer are stored in the group's SharePoint document library in the Apps/Yammer folder. Any files uploaded before your network gets this new feature remain in Yammer cloud storage. To see where Yammer files are stored for your network, go to How do I tell where my Yammer files are stored?
A: Yes. Any new group created in Yammer will add the prefix and suffix from the group naming policy, and will not allow blocked words in the group name. For more information, see Microsoft 365 Groups naming policy.
Note that Yammer group names can't contain the following characters: @, #, [, ], <, or >. If the naming policy includes any of these characters, regular Yammer users will not be able to create groups in Yammer. Microsoft 365 admins can still create groups in Yammer.
When the automated conversion happened, it didn't convert groups that didn't meet the eligibility criteria. You can make the needed changes to make those groups eligible, and then create a support ticket to get them converted.
Before opening the support ticket:
Make sure all groups have an owner, and the owners all have Microsoft 365 group creation privileges.
Make sure all groups have members.
If you have unlisted (secret) groups, change them to private or public groups.
To find this information, you can do a data export and look in the groups.csv file. You'll need to cross-reference the owner list with the list of people who have Microsoft 365 group creation privileges.
