Most of our customers are using SharePoint as both a communication and collaboration portal, benefiting from a single entry point to information, knowledge, calendars, task, apps and more. But today on O365, Microsoft Teams is also set to play a central role in day to day teams collaboration. How can we keep the convenience of a single access point for comm and coll (SharePoint) while fully embracing the power of Microsoft Teams ? Evolusys has solved the equation… keep on reading ;-)
We see Microsoft investing tremendous effort to make Teams to most efficient way to collaborate efficiently. Over time, Teams will replace Skype for Business, and be the go-to platform for most of an information worker’s day. But our customers (and ourselves) are struggling with one very relevant challenge : SharePoint is my single entry point for Communications, I do not want people to have to go to two different platforms for their work !
Microsoft is not proposing yet any built-in solution for that (we know it is on the roadmap for somewhere in 2018), therefore we built it.
Now let’s talk about our solution to expose a user’s Teams from SharePoint site. We will based our answer on two Microsoft products which are :
- The new SharePoint Framework (SPFx): This is page and web part model that provides full support for client-side SharePoint development. Today, SPFx is the the recommended way for SharePoint customisations, and it is now available both on O365 and on-premises with SP2016 Feature Pack 2.
- The Microsoft Graph API : The Microsoft powers all things O365. The graph is THE sesame to the creation of powerful extensions to O365, including Insights.
Microsoft just released a beta version of the Graph API, which exposes Teams related information (channels, pics link, …). Our solution was to build a SharePoint Framework web part, which leverages the MS Graph and lists all of the connected user’s Teams. From that point, you can decide to use it on any Modern site, to provide a quick and direct access to the user’s Teams.
The second objective of the web part was to give you the ability to directly open the clicked Team using the web and, if installed, the Teams application.
The goal here is not to show you how to fully build this web part, but you can find links to comprehensive information at the bottom of this blog.
Ok now we are ready, let’s first study the URL to do the deep link to a Teams channel. You can find it on the channel menu in Teams :
The link to the general channel of a Team is composed as follows :
The tenant ID is fixed, so this is easy, but to get the channel ID we will have to get first all Teams you joined, and then all channels of each team to get to the right channel.
Microsoft is providing all those info from the graph, using the following calls:
Into your code you will have 2 methods like :
To compose the link and display the Team don’t forget to remove the “-“ characters into the channel ID :
By finalizing all the code and doing a little bit of CSS you can have a nice and fully responsive web part, “Et Voilà !” :
To conclude building this web part is just a start to have more relationship between SharePoint and Teams and encourage the adoption of Teams into your company.
Choose, the right partner to build your SPFx web parts
Evolusys has been helping customers on Microsoft technologies for years. Theses engagements gave us :
- A solid understanding of your business needs
- A proven expertise on the Microsoft environment
- A privileged relationship with Microsoft
On top of all of these points, we strive to develop future proof solutions, leveraging the most up to date approaches, technologies and best practices.
When Microsoft first released the SharePoint Framework, Evolusys immediately started building SPFx PoCs . Based on these PoCs and similar projects, Evolusys believes that SPFx is the way to create the user experience of tomorrow in SharePoint !
- It will help you build more tools for you SharePoint sites
- It is open source
- It provides a simpler interface that make it easy to use and reponsive
- It is fast to market
- Agile and future proof
- And available On Prem and in the Cloud (with some twists)
You do not know where to START ?
How to build a SharePoint framework web part ? Made by Microsoft from 0 (setting up your dev environment) to 4 :
Secondly you need to know how to integrate the graph API, and you know what ? Microsoft is also proposing a tutorial for that here (example to list office 365 groups)!
Thanks for reading this, if you have any questions we would be happy to discuss further with you.