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 https://www.yammer.com/widget/configure.

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.

092916_1345_EmbedaYamme8.png

And the following two line at the end

092916_1345_EmbedaYamme9.png

Explanation of the added lines:

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

<script type=”text/javascript” src=”https://c64.assets-yammer.com/assets/platform_embed.js”></script>

Tips: Add *.yammer.com 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 Yammer.com, 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.

Advertisements

Office 365 groups and Microsoft Dynamics CRM

Leave a comment

Office 365 groups are a great way to collaborate. Microsoft has added integration of the Office 365 groups with Microsoft Dynamics CRM. As an example you could create an Office 365 group for a new account or a new opportunity that you have in your CRM.

In order to use the groups in CRM, there are some configurations to be done by your administrator.

Here is what you need to do to enable Office 365 group collaboration from Microsoft Dynamics CRM.

Requirements

To be able to use Office 365 groups your users need an Office 365 licence with an Exchange Mailbox and SharePoint Online.

Then you will need to deploy the group solution in your CRM entity

Deploy Office 365 Group solution to CRM

Connect to your Office 365 subscription using the tenant global administrator account, in the Office 365 Admin Center click on CRM

In the CRM Online Administration Center,

  • Click on Instances
  • Select your CRM Online instance
  • Click on the pen beside Solutions to add the Office 365 Groups solution.

If the solution is already installed you will see it listed in the Manage your Solutions section

Manage Permissions

The following steps will explain you how to verify permission In order to integrate Office 365 Groups in Microsoft Dynamics CRM

Click on CRM from the App Launcher

Click on Settings, then Security

In the Security page, click on Security Roles

Select the security role that you want to allow to use the Office 365 Groups

  • Click on the Customization Tab
  • In the Miscellaneous Privileges section, make sure that ISV Extensions is selected

Configure Office 365 groups in CRM

To configure the Office 365 groups, go back to the CRM administration tool

  • Click on Settings
  • Click on Office 365 Groups

Add an Entity, in my example I have added Account

Note that you have the option to auto create a group when an Account is created

Then click Publish All

Create an Office 365 group for a CRM Account

To create an Office 365 Groups for a CRM account

  • Goto CRM from the App Launcher
  • Click on the menu, select the Sales Group
  • In the Customers Section select Accounts

In the account list:

  • Select your account
  • On the nav bar click on the arrow next to your account
  • Click on Office 365 groups

Here I have Selected Bellows College, you have the option of creating a new group or joining an existing group.

When creating a new group you will see the following message

Once the group creation is completed, you will have full access to the Office 365 Group from your CRM Account

You can read more about Office 365 Groups in this article: https://tremblayse.wordpress.com/2016/09/19/office-365-groups-and-planner-the-new-collaboration-way/

Groups guest access for external user

Leave a comment

Microsoft has recently announced that it is now possible to grant access to Office 365 Groups for external users with the new guest access.

https://blogs.office.com/2016/09/08/introducing-guest-access-for-office-365-groups/

Enabling guest access for external users is something that a lot of people were waiting for, so I have decided to test it out for you to show how easy it is to grant guest access to external users and to see what type of permissions is given to the guest user.

To show you how it works, I started by creating a new group:

Then I added a new member with a Hotmail account, the account is seen as a guest (see image below).

“Guest access works for any email accounts including corporate and consumer domains (such as Outlook.com or Gmail.com).” source: https://blogs.office.com/2016/09/08/introducing-guest-access-for-office-365-groups/

When adding an external member, you see the following message to notify you that the guest will have access to the group content. (it does not say what type of access, and you cannot select the type of access to grant the guest).

It will take some time (minutes) before the external user has access to the external content.

He will eventually receive the following email to welcome him to the group.

Once the external user clicks on the link to read group files, he will be asked to sign in to Office 365

Once the external user has signed in he will be able to view the Shared documents and the Shared Notebook from the Office 365 Group.

He will be able to add, modify, delete and sync documents in the Shared Library.

The External user will also be able to send email to the group to create a new conversation

See below the new conversation published to the group from the external user.

The guest user will also be able to add pages, lists, libraries and apps to the site.

At the moment of writing the external user does not have access to the group Shared conversation (but will receive email for each new conversations), Shared Calendar and Shared Tasks (Planner).

I hope that this helps you understand better how to grant access to external user and what an external user will be able to do in your Office 365 Groups.

If you want more information about Office 365 Groups you can read this other article that I posted on the subject https://tremblayse.wordpress.com/2016/09/19/office-365-groups-and-planner-the-new-collaboration-way/

I will be watching the announcements at the Microsoft Ignite conference this week!

There are at least 30 sessions at ignite that will talk about Office 365 Groups
https://myignite.microsoft.com/sessions?q=%22office%20365%20groups%22#ignite-html-anchor

Watch Microsoft Ignite Keynote session

Leave a comment

The Microsoft Ignite Conference will take place in Atlanta next week. It’s the top Microsoft technology conference. This year again it was sold out. It’s the first time in many years that I am not attending.

If you are not going to be at the Ignite, you can still watch the sessions that are presented. They are normally available shortly after their live performance to watch from your home or Office!

Other sessions like the Microsoft Ignite Keynote will be available in live streaming at http://ignite.microsoft.com.

Be ready on Monday September 26th at 9:00 AM EDT, to watch the Keynote!

Here is the description of the Keynote:

Technology continues to rapidly evolve, offering us new ways of working and powering digital transformation for all organizations. Key to our ability to harness technology is our ability to evolve with it, to harness new capabilities and learn new skills. Join Scott Guthrie, Executive Vice President, Microsoft; on Monday morning to start Microsoft Ignite. Scott will focus on how technology enables digital transformation and, along with guests, demonstrate new technologies. He will also discuss how IT is transforming and detail investments and programs to help enable this.

 

Office 365 Groups and Planner – the new collaboration way!

2 Comments

Last week I was speaking at SharePoint Saturday Cambridge (UK) about groups and planner. Every time I talk about groups and Planner I am surprise that there are still some people that don’t know much about it, so I decided to do a little write up about it.

What are Groups for?

Groups makes it easy for Office 365 users to share: Email, calendar events, documents, notes and tasks (when Planner is available to all). There is a mobile app to access and update Group content. With the Group connectors, you are able to view information from multiple external collaboration and productivity tools/apps in your Group.

“Office 365 Groups is a feature developed with collaboration in mind. It works with the Office 365 apps you use already so you can collaborate with your teammates when writing documents, creating spreadsheets, working on project plans, scheduling meetings, or sending email.” Source: https://support.office.com/en-us/article/Learn-about-Office-365-Groups-b565caa1-5c40-40ef-9915-60fdb2d97fa2

What is required to have Groups?

Groups are part of Office 365 and requires one of these Office 365 subscriptions:

  • E1-E5
  • A1-A4
  • G1-G4
  • Business Essentials
  • Business Premium
  • Business, Small Business Premium at Midsize Business plans
  • Kiosk

To participate in Groups, users need both a OneDrive for Business license and an Exchange Online license.

How to create Groups?

Office 365 Groups can be created in different ways. The easiest way is to open Outlook Online or Outlook 2016 and create a new group.

Office 365 Global administrators can create groups for the Tenant administration portal or from the Office 365 mobile administration tool.

When Planner will be available on your tenant, a groups will be created when you create a new Planner plan.

If you have configured Groups and Dynamics CRM integration, you will be able to create groups from Dynamics.

Groups can also be created with PowerShell

Who can create Groups?

Out of the box any one with the right Office 365 subscription and an Exchange Online Mailbox is able to create a Group.

Can we manage who can create Groups?

The Office 365 Global Administrator can apply rules to:

  • Disable Group creation for everyone or for a subset of users
  • Set up naming convention for new groups (adding prefixes or suffixes when creating Groups and email address)
  • Add quotas to Groups
  • Allow send as the Group

Note: At the moment of writing this article, some of these rules don’t apply when you create Plans (Planner) or when you create groups from CRM. It’s on the roadmap to fix these issues.

In the next weeks I will try to publish some How to articles to help you to use and manage the Groups.

Microsoft Technical Communities

Leave a comment

Microsoft has launched the new Microsoft Technical Communities.

“The Microsoft Tech Community is an evolution of the Office 365 Network, growing to support new Azure; Windows Server, and SQL Server Communities and in future many more communities. The URL of the new community will change soon to http://techcommunity.microsoft.com and redirects will be in place for any existing URL on the http://network.office.com domain”

Source:
https://techcommunity.microsoft.com/t5/Community-Announcements/Announcing-the-Microsoft-Tech-Community/m-p/8691#M50

This will be the new place to get technical information, you will be able to ask questions and have experts from around the world that will be available to help you. The idea is not new, we had MSDN Forums, Yammer groups etc. The new technology should make it easier to users to ask questions and to find technical answers.

Microsoft is moving away from the Yammer groups to the new Tech community, here is the answer from Microsoft to someone that was wondering what will happen to the existing Office 365 Network on Yammer that has now been moved to the new Tech Community.

“Hi Sergio, posts from the Office 365 Network on Yammer will not be migrated to the Microsoft Tech Community. On September 15th all existing members of the Office 365 Network will not have access to the old network. If there is any content (files, notes etc) that you want to keep, please do so before the network closes.

To provide some more info that I have mentioned previously on the Office 365 Network for additional context:

•The move of the Office 365 Network away from Yammer is to allow for unauthenticated viewing and indexing community results via search. This scenario of supporting Internet-public forums is not what the Yammer product is for. We believe there are other, more important investments for Yammer that will benefit customers more. Yammer is for collaborating and communicating in smaller (yet still large – our largest today would be around 500k-600k users) organizations and networks.

As a company we are still very much committed to Yammer as a product. We believe it provides a best-in-class enterprise social solution for our customers and we have millions of Office 365 customers using Yammer. The product team are making many changes to handle this scale.

•The Office 365 Network provides tremendous value to our customers through the power of network knowledge and collective experience sharing, which would be highly beneficial if discoverable by Bing and Google search. However today most customers who have not joined the Office 365 Network on Yammer can’t find that information. We have not turned SEO on but already we have seen a huge spike in membership. Of course the shutdown of this network is an impetus to drive people to the Microsoft Tech Community. If this community did not provide value to its members we wouldn’t see us hitting over 10,000 members today. We expect many more to join during Microsoft Ignite and after the event has finished. SEO will be turned on before Microsoft Ignite.

•We established early on that read-only access is not possible on Yammer networks. If that option was available to us we would have explored it further but sadly it isn’t.

Migration of conversations is a loaded topic because 1) for a migrated conversation to be meaningful every person on that thread needs to be a member of the community. 2) Turning SEO on means anyone can view and read your conversations. The Office 365 Network on Yammer was a closed network and community results could not be searched. To respect the privacy of members who do not wish to have their conversations found via search engines, we are not migrating conversations to the new community that allows for unauthenticated viewing.”

If you have not signed in yet goto : https://techcommunity.microsoft.com to enjoy the new community