Microsoft Flow In 10 Days - Day Eight - Flow With Graph API

Now, click “Add an app” to register our new app.

Enter the application name and click “Create”.

On the next page, take a note of the Application ID.

Next, we will create the App Secret or the Secret ID. Click on “Generate new Password”.

Note down the secret carefully; it will not be displayed again.

The next step is to provide the permissions for our application. Let's move to the Microsoft Graph Permissions.

Click on the “Add” button of the Application Permissions.

This lists out all the available permissions.

Out of these, we will select

1. Sites.ReadWrite.All (SharePoint)
2. Files.ReadWrite.All (One Drive and SharePoint).

Based on your application's requirement to query different resources, these permissions should be selected.

Finally, click on "Save" to register your app.

Now, there is one more thing pending. That is, to get the consent (approval) from the tenant admin. For that try constructing the below URL.

https://login.microsoftonline.com/<tenantid>/adminconsent?client_id=<appid>&state=12345&redirect_uri=https://localhost

To get the tenant ID, we can go by a couple of ways.

Azure Portal - Azure Active Directory - Properties - Directory ID

Using Postman client – Check this fantastic article by Santha Kumar here

Once we get the tenant ID, we can construct the above URL and send it to Admin for approval. Once he/she clicks on the link and logs in with the Tenant Admin credential, click on “Accept” to give the approval.

The next page might be showing an error as we haven’t configured any exit URLs, but that is ok. Our app is registered successfully now.

This can be confirmed in the Enterprise Apps in Azure Portal. As we have registered the app and we have the App ID, App Secret and Tenant ID, finally we are going to build the flow.

Create a flow taking a blank template. For creating a flow and more info about Triggers and Actions, check my previous posts. This time, I am going to manually trigger the flow.

Click on New step and type “variable”. Select the action “Initialize Variable”

Set the client id (app id), client secret, tenant id in 3 different variables so that it can be used multiple times in our flow.

First set client id variable.

Enter the variable name in the “Name” field. I have named it as “client id”

Set the Type to “String”.

Enter the client id that we have got earlier while registering the app in the Value field.

Likewise create 3 variables for the 3 attributes.

Next step is to send the HTTP call (Microsoft Graph API call)

Select HTTP as the next action.

I am going to check the details about one of my site collections “csharpcorner”

For that, the Graph endpoint is - https://graph.microsoft.com/v1.0/sites?search=csharpcorner

This can be confirmed by checking in the Graph Explorer.

Now, click on “Show advanced options” to select the authentication mode.

I am selecting “Active Directory Oauth”. All the remaining fields have to be filled as it as from the figure given below.

Once this setup is done, it is time to test the flow. Check my day 1 post here to understand how to test a flow.

In the body part of the output, we get the details of the site.

Our Flow has run successfully. This json output can be used in the further flow steps based on your needs.

Thus we have successfully built a flow that invokes a Graph API and gets data from SharePoint. By changing the API end points in this flow , we can interact with different services in O365.

Thanks for reading!!! Let me know in the comments if you have any queries.

Happy reading folks!!!