Using the Usage Policy in Yammer

When you work with a system, whatever system it is, you need to have a set of rules, what is allowed, what is not allowed, what kind of behavior is desired on the service, … in short a Usage Policy. The problem with most usage policies is that people just don’t read them, because they are complex, not easy to find, not up-to-date, etc.

In Yammer we have a feature called Usage Policy, which can be found in Admin > Design and Configuration > Usage Policy


I’ve checked the Require users to accept .. and the Display policy reminder in sidebar. This gives me the certainty that my users have to accept it before they can use Yammer and they can easily retrieve it because is always shown in the sidebar.


My admin user who was logged in when I activated this and hadn’t accept the Usage Policy got the follow popup.


When I invited a new user, he got during registration the following:


So I couldn’t register my new user without confirming this. When the Usage Policy was updated the new user got as well a nice popup to warn him about the updates.

Activating Yammer Enterprise in Office 365

Yammer Enterprise has been released as a part of Office 365 Enterprise Plans. Now how do you activate it and more specific how you connect it to your already existing network(s).

First thing first activation:

When you enter your Office 365 dashboard you should see this when your tenant is ready for Yammer:


You can click on the Yes, activate Yammer Enterprise for my network.

When you already have a Yammer version connected your domain or you need to create one, that’s the easiest way and according to documentation also the recommended way.

When you want to upgrade multiple networks; e.g. when your users don’t share a common email address or work in disparate business units or unrelated subsidiaries, then you need to upgrade a primary network first, and contact Yammer Enterprise Support to upgrade additional networks

When upgrading and merging domains; e.g. an organization that has multiple business units or subsidiaries that want to take advantage of the collaboration and administrative features of Yammer Enterprise but don’t share a common email domain; we recommend that you choose the most relevant existing network, that is, the network with the most content or users to be your parent network. You’ll want to consider this option carefully because merging email domains will cause users to lose access to any content that was created in their original Yammer network. you might want to contact Yammer Enterprise Support to work through the plan for a network merge.