I've just posted a tip on how to consume CSOM with Azure Active Directory Apps and behind that tip, there is a broader question regarding the various ways to interact with SharePoint Online. Today, we have three possible methods:
- SharePoint Add-Ins (here I'll be targetting Provider-Hosted Apps only)
- Azure Active Directory Apps
A while ago, I wrote a series of blog posts on how to develop Yammer Apps and what you could expect from the Yammer App model in scenarios where you'd leverage Yammer from SharePoint. Since then, Microsoft has added the possibility to consume Yammer REST APIs from Azure Active Directory Apps.
Azure Active Directory Apps represent the new way of consuming Microsoft's SaaS applications among which SharePoint Online. When it comes to the latter, it's a little hard to see the added value of AAD Apps versus SharePoint Add-Ins. Admittedly, it's not a revolution when it comes to SharePoint. However, from a broader perspective, this new technology represents a single coherent way to address Microsoft SaaS applications as a whole. It currently includes Yammer, SharePoint Online, Exchange Online, PowerBI, AAD, OneNote, Office 365 Unified API and Office 365 Management API.
As some of you asked, I developed a FARM solution that targets On-Premises SharePoint installations. Deploying the solution is an easy game since it's about deploying the WSP to your FARM. I've updated the CodePlex project and ajusted the documentation accordingly. Just download the version of your choice (Cloud or On-Premises) available here https://spoautotagging.codeplex.com/
SharePoint Online Auto-Tagging Add-In Improvements (Keyword creation, Lemmatization, Entity Recognition, Thresholds ...)
I have improved the Auto-Tagging Add-In, it now comprises the following features:
- Enterprise Keywords recognition and creation
- Lemmatization process
- Named entity recognition (Persons, Organizations and Locations)
- High Auto-Tagging precision for Managed Termsets thanks to custom properties including regular expressions
- The possibility to specify thresholds for keyword recognition and creation
- The possibility to define a noise words list
I've just released an Auto-Tagging Add-In for SharePoint Online. In a nutshell, it's a Cloud-Hosted App having a remote web site and a remote web service deployed in Azure PaaS.
Therefore, it is required to have an Azure Tenant to test and deploy it. The tagger leverages SharePoint out of the box taxonomy features and is configurable via custom properties associated to terms. By default, no term will be tagged automatically until you explicitely create properties that instruct the tagger how to automatically make the match between the taxonomies and document content.
In SharePoint On-Premises, you can simply deploy your web services within SharePoint and target them via _vti_bin or you can even create your own REST endpoint and target them via _api/myendpoint...
As you know, external sharing can be controlled at site collection level to allow or not sharing with external users. However, until now, if you allow sharing, it is by default with the entire world. The sharing invitation will be sent to the e-mail address of the person you're sharing the site/document with. When that person clicks on the invite, she is invited to login with either a Microsoft Account, either an Organizational Account which is created in the AAD. Afterwards, the user is added to the group/assigned direct permissions.
Here is the demo code of a solution I showed at BIWUG. As a reminder, here is what the App does:
- When installed into a Host Web, it attaches security event receivers to the Calendar list of the Host Web in order to send Calendar events to Yammer OpenGraph
In this case, I prefered to show something simple rather than actual LOB events but the principle remains the same.
From a technical point of view, the App makes use of :
- An Azure Storage Queue to log events
- An Azure Web Site to host SharePoint Remote Event Receivers