Configure Microsoft Flow for Sending Office365 SharePoint File Attachments in the Mails

Here, let us look how to configure Microsoft Flow for sending mails with Office 365 SharePoint library files as attachments.

Imagine there is a requirement of sending mails with SharePoint library files as attachments, if a file/item is created/uploaded. Previously we were creating tools for such requirements. Unfortunately, SharePoint designer doesn’t provide option for attaching files in the mails, in the configurations.

Microsoft Flow provides a solution for the above requirement. The solution just includes few configuration steps, which might take one or two minutes of your effort J

Use Case: Whenever a file is created in the folder, send out a mail notification with the uploaded file as attachment to a particular mail box.

Steps Involved:

The following steps shows the detailed configuration steps.

• Create a Microsoft Flow with a blank template as base.
• Select SharePoint connector, search and select “When a file is created in a folder” trigger. In the trigger, Provide the site address URL and select the necessary library/folder path.

Creating Office 365 SharePoint Custom Connectors on Microsoft Flow

Here, let us look how the custom connectors can be created for accessing SharePoint data on Microsoft Flow.

Microsoft Flow provides multiple connectors from various services including SharePoint to work with the data. The connectors contain multiple triggers and actions. For SharePoint connector by Out of the Box, Microsoft provides 8 triggers and 28 actions on Microsoft flow.

UseCase: Imagine you want to retrieve the SharePoint user profile data of some user. Currently there is no action available for MS Flow developers to retrieve SharePoint user profile data. Such triggers and actions can be created by developers on the Microsoft Flow platform. In this post, let us look how one such custom action can be created and used on the Microsoft Flow platform.

The configuration involves the following steps.

1. Configuring Azure AD Application, which provides necessary permissions and helps in authenticating the calls made from Microsoft Flow.
2. Generating the collection file (Swagger) using postman tool, which will be used as base file while building the custom connector.
3. Configuring the custom connector, which will make call to SharePoint to get the required data with necessary inputs.
4. Testing the custom connector created above.
5. Creating/Configuring the flow, which will also use the custom connector we have created above.

Configure Azure AD Application for Flow Authentications:

• Create a new app on the Azure Active directory.

Content Classification on Office 365 SharePoint using MS Flow and LUIS

In this post, let us look how the Office 365 SharePoint list content can be classified using Microsoft Flow with the help of LUIS text prediction techniques. Text added to Office 365 SharePoint list are classified and saved back to SharePoint using Microsoft Flow and LUIS.

Consider a scenario of having queries list, and admin wants the queries to be auto classified before routing the queries for solution. Microsoft Flow provides a LUIS connector, which helps in predicting and classifying the text being saved to SharePoint.

Note: In a layman scenario on LUIS portal, categories will be intents and queries will be utterances.

Connecting SharePoint and LUIS using Flow

The solution consists of three steps.

• Query is created on SharePoint: Flow is triggered, whenever a new item is created in the SharePoint list.
• Query category is predicted using LUIS: Flow uses LUIS Get Prediction action for classifying the item created. The action predicts the data using the trained app created on the LUIS portal. The output of this step will be matching intents (predicted scores) with the relevant scores.
• Query is updated with the category predicted: After classification, the top scoring intent from the above step is saved to the respective SharePoint list item’s category field.

Speech Recognition on Office 365 SharePoint with Azure Cognitive Service Speech API

In this post, let us see how speech recognition can be implemented using Microsoft Speech API on SharePoint portals using JavaScript client side libraries/SDKs. This shows how speech to text can be converted on Office 365 SharePoint using Azure Cognitive Services.

In our previous post, we have seen implementing Speech recognition using browser SpeechRecognition objects on SharePoint portals. This post is special for those people who love implementing speech recognition using Microsoft Speech API (Azure Cognitive service speech API).

Note: If you are interested only in the implementation, scroll down to the bottom section. :)

Azure Cognitive Service - Bing Speech API

Microsoft Speech API supports both speech to text and text to speech conversions. In this case, only we are focusing on speech to text conversion. Microsoft Speech API provides two approaches of speech to text conversion. One using the REST API and the other way is using the client libraries. We will be leveraging the client libraries, which provides speech SDK bundles.

Speech Recognition on Office 365 SharePoint

Let us look how the speech recognition can be implemented on Office 365 SharePoint portals. The article contains the introduction to speech recognition service (speech to text conversion), detailed approach for SharePoint, code and snapshots for easier implementation.

Speech Recognition

Speech recognition helps recognizing the real-time audio from the microphone and converts it to the respective text. This kind of interfaces helps in building the voice triggered apps like chat bots, etc.

There are two approaches of implementing speech recognition on SharePoint.

• First using the Speech Recognition interfaces.
• Other way is using the Azure Bing Speech API. It is built on top of WebSockets API. The Speech SDK is available as extensions, which can be leveraged for development.

Let us go with the first approach in this post. We are going to see how the speech recognition interfaces are integrated on to SharePoint applications. In my future articles, I will detail out the integration of Bing Speech API (second approach).