Leave a comment

Last night at the SharePoint Québec Usergroup meeting we had a great discussion about the collaboration tools that are available with Office 365. SharePoint, Groups, teams, Yammer, Onedrive for Business and all.

Here a few links that were shared in order to help understand better the different tools.

Microsoft Teams, groups and Yammer general information


Deploying and governing groups

Get the Latest on Office 365 Groups – Overview, What’s New and Roadmap







SharePoint Online Public Web sites

Leave a comment

Public Web Site has not been available to new Office 365 tennant for a while.

Existing tenant that had a public web site could still use it.

Beginnig May 1 2017 you will not be able to use your SharePoint Online Public Web site… Unless you required to keep your site until March 31 2018.

Steps to request to keep your site until March 31 2018.

1. Log in to the SharePoint Admin Center.
2. Click Settings.
3. Select the I’d like to keep my public website until March 31, 2018 option.

Act now if you have a SharePoint Online Public Web site.

More information


SharePoint Online Site Mailbox

Leave a comment

Microsoft has announced that SharePoint Online site mailbox are going away.

If you were not using them, it is not an issue. However, you will not be able to create new site mailbox stating in March 2017.

Your existing site mailboxes will continue to work for a while, but you should plan to transition to Office 365 groups.

Here is the message received in the message center:


Office 365 first release

Leave a comment

Microsoft makes frequent updates to Office 365.

In order to prepare and test these updates, an Office 365 tenant administrator can allow everyone or specific users to have access to these features before they are publicly available.

This gives you time to test and prepare the documentation to train/notify your users about the changes the upcoming changes in Office 365

It is very simple to activate.

  • Logon to your Office 365 Admin center with your tenant administration account.
  • Go to Settings/Organisations profile
  • Edit the release preferences to allow access to the first release

Note: It might take up to 24 hours to be activated.


More information about first release:

Error accessing Managed account in SharePoint Central Administration

Leave a comment

If you are trying to access you managed accounts in SharePoint Central administration site

And you receive this error:

It’s probably because you have created a new managed account with “Enable automatic password change”.  This issue should not happen if you have the latest SharePoint build number.

In order to fix the problem you need to use PowerShell to find the account that is set to “Automatic password change”

Get-SPManagedAccount | ? {$_.AutomaticChange -eq $true} | SELECT UserName

Once you have found the account, use PowerShell to remove the “Automatic password change” for the problem account.

$SPMA = Get-SPManagedAccount “<DOMAIN>\<UserName>”
$SPMA.AutomaticChange = $false

Then you will be able to access “Configure Managed account” in the SharePoint Central Administration site.

Microsoft SharePoint Server 2016 feature pack 1

Leave a comment

Microsoft SharePoint Server 2016 is great, but Microsoft wants to make it better. They are constantly adding new features in Office 365 and SharePoint Online. Microsoft has learnt of lot from running SharePoint farms with millions of users, they want you to be able to benefit from their knowledge when you are using Microsoft SharePoint Server on premises.

During the week of the Microsoft Ignite conference in Atlanta, Microsoft announced the launch of Microsoft SharePoint Server 2016 feature pack 1.

Feature Pack 1 will be included in the SharePoint Server 2016 November Public Update. It was also announced that a Feature Pack 2 is planned for the 2nd half of 2017.

Here is a recap of the announcements about Feature Pack 1 (plus my comments) from this presentation at Microsoft Ignite conference.

Last May Microsoft talked about the concept of Feature pack. We knew it was coming, we just did not know when. According to Bill Baer the SharePoint 2016 Server Feature Pack 1 was released 6 months ahead of time.

Before the Feature Pack Microsoft had a long release cycle for new features. SharePoint major release were every 2-3 years, services packs every year, monthly CUs. But CUs and Service Packs did not bring any new features.

As I said earlier new features in Office 365 and SharePoint Online are introduced very rapidly. With the old release pattern SharePoint Server 2016 users would have had to wait 2-3 years to get new features. This would have been way to long. This is way Microsoft came out with the idea of Feature packs.

For feature pack 1, Microsoft focused on three main groups IW, IT and Developers.

  • For the IT they are bringing new MinRoles, Hybrid Auditing, hybrid Taxonomy and Administrative action logging (see below for more information)
  • For the developers they are bringing the OneDrive API 2.0

Information Worker

For Information Workers they wanted to bring the OneDrive for business user experience which is fast and responsive allowing to easily add, copy, move, rename and share documents.

They also added the possibility to add custom tiles to the App Launcher.

To add a custom tile, it’s as easy as adding an item to a list.

Min Roles

When Microsoft SharePoint Server 2016 came out, they introduced the concept of Min Roles. It’s a set of predefined roles that you can set when adding a server to a Microsoft SharePoint Server 2016 farm.

In the Min Role mode, SharePoint will automatically configure the services based on the selected server’s role to make sure that performance is optimized for the role.

When SharePoint Server 2016 came out there were 6 Min Roles: Front-end, Application, Distributed cache, Search, Custom and Stand-Alone.

Building a SharePoint Farm in Min Role mode required at least 4 SharePoint servers. This was not suitable for many small organizations.

With the Feature Pack 1, the SharePoint team added 2 more roles: Front-end with Distributed cache and Application with Search.

Thanks to Feature Pack 1 smaller organization will be able to deploy a SharePoint Server 2016 farm in the Min Role mode with only 2 SharePoint servers instead of 4.

More information on Min Roles:

Hybrid Auditing (preview state)

Microsoft has made a big investment in auditing in Office 365 with the Security and Compliance center. You can search and report about user’s file access, administrative actions and much more.

With the Feature Pack 1 you will be able to use the Office 365 Audit Log Search to also view activities that happened against sites and contents in your Microsoft SharePoint Server Farm.

See below a few of the activity reports that are available in the Security and Compliance Center:

File and folder activities

Sharing and Access request

Site administration

To access the Security and Compliance center reports in the App Launcher click on Security and Compliance
When in the Security and
Compliance center, click on Search and Investigation, then on Audit log Search

Click on the following link to find out more about Hybrid Auditing

Hybrid Taxonomy (Preview state)

With the SharePoint Server 2016 Feature Pack 1, you will be able to use the new Hybrid Taxonomy to share your taxonomy between Office 365 and a Microsoft SharePoint Server 2016 farm. It’s important to know that synchronization will be only one way, from Office 365 to SharePoint 2016 Managed Metadata.

From this site:

“A new hybrid feature that is currently in progress for SharePoint Server is SharePoint hybrid taxonomy. SharePoint hybrid taxonomy allows SharePoint administrators to create shared taxonomies (managed metadata) between their on-premises SharePoint Server and SharePoint Online. With SharePoint hybrid taxonomy, changes and updates to your SharePoint Online taxonomy are replicated to your SharePoint Online sites as well as your SharePoint Server sites. Configuration is simple and you can use the included tools to migrate your existing on-premise taxonomy to SharePoint Online and create a shared taxonomy from existing taxonomies.”

Note: Hybrid Taxonomy will also be available to SharePoint Server 2013 farms as part of the September 2016 Cummulative Update.

Administrative action logging

With Feature Pack 1, it is now possible to add logging for Administrative actions in the Usage and Health data collection.

As an example, you can find out when password reset settings for service accounts has been changed or when someone has added or removed users from the SharePoint Farm administrator group.

In order to query the logs you can use the following PowerShell command : Get-spusagedefinition –identity “Administration actions” | Merge-SPUsagelog -StartTime “08/11/2016 3:50 AM” | Select User, ActionName, Timestamp | Sort Timestamp

See image below to view the results.

You can also query the UsageDb with Transact SQL. It’s one of the few dbs that Microsoft allows to use Transact SQL to query.


Having these new features in SharePoint Server 2016 is a great news and brings more compelling reasons to migrate your environment to SharePoint Server 2016 and run it in Hybrid mode. Don’t wait anymore!

Embed a Yammer feed in a SharePoint page

1 Comment

Recently I was asked by a customer if we could replace the SharePoint Newsfeed by a Yammer feed. He wanted to filter out discussions based out on the page where the discussion was created, but also wanted to have one central place for all the feeds. Using Yammer Feed also provides a way to access the feed with the Yammer mobile app.

The SharePoint Newfeed is present in the home page of a team site and provides a way to have a feed on the home page or other pages. The SharePoint NewsFeed provides a site feed, when you add the WebPart to multilpage pages you see all the feeds for the site.

The look is very similar between the two feeds.

SharePoint NewsFeed Yammer Feed

We started by creating a new Yammer Feed called Page Conversation.

1. Logon to your Yammer Network

2. Create a new group called Page Conversation

3. Retrieve the FeedId of the group

The group FeedId will be required later to generate the embed code. You can find the FeedId in the URL of the Yammer group

Once the Yammer group is created we needed to generate the code to embed in the page.

1. To generate the embedded code to add to our SharePoint page, you need to go to this page

In order to filter the Yammer Feed based on the page where it was created, you need to use Open Graph as the Feed Type and Page for the OpenGraph type.

See the image below for the configuration options:

Note: make sure to replace the Network permalink value by your Network and the Default group_id by the FeedId of the group that you created.

2. Once you click on Apply Changes, the embed code will be generated and will appear in the bottom left of this page.

Copy the code to notepad.

3. Adjusting the code

In order for the code to run on the SharePoint page, you need to add the following lines at the beginning of the generated code.


And the following two line at the end


Explanation of the added lines:

The following line is necessary to call the Yammer JS library.

<script type=”text/javascript” src=””></script>

Tips: Add * in Internet Explorer Trusted zone.

The following div will help to make sure the width of the WebPart will stay aligned with the other WebParts on the page

<div id=”embedded-feed” style=”height:800px;min-width:350px;”></div>

The following function is to make sure the the code will only load when the page is completely load, to avoid conflict with the page load of the other components on the page

window.onload = function () {

Adding the code to a page

You can add the code to a page in many different way. In this demonstration we will use a script editor WebPart.

1. Create or edit and existing Wiki page

2. Add a Script WebPart to your page

3. Edit the Script Editor WebPart to add the code snippet

4. Paste your code and click insert and save your page

5. You can repeat the steps to add the script editor WebPart (and the code) in multiple pages.

Each pages will display only the feed that was created in the page.

If you access the Yammer group from, the 2 conversations are shown in the Yammer Group

In another article I will explain how to create and publish a Yammer Page Feed Web Part to the WebPart Library so it can be easily re-used in any pages.

Older Entries