{"id":5799,"date":"2021-01-26T06:00:50","date_gmt":"2021-01-26T14:00:50","guid":{"rendered":"https:\/\/officedevblogs.wpengine.com\/?p=5799"},"modified":"2021-11-17T12:44:11","modified_gmt":"2021-11-17T20:44:11","slug":"microsoft-graph-mailbag-batch-requests-with-power-automate-custom-connectors","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/microsoft-graph-mailbag-batch-requests-with-power-automate-custom-connectors\/","title":{"rendered":"Microsoft Graph Mailbag – Batch requests with Power Automate custom connectors"},"content":{"rendered":"

In this Microsoft Graph Mailbag post we will cover the benefits of building Power Automate custom connectors for Microsoft Graph. \u00a0This includes details of Microsoft Graph JSON Batch, ways to create custom connectors, and how to use them in the process automation flows. For those unfamiliar, Power Automate<\/a> is a no-code\/low-code platform that provides us everything about automation for manual tasks. You can leverage Power Automate using built-in connectors or you can build your own custom connector to use in flows.<\/p>\n

\"\"<\/p>\n

If you are interested in creating a Microsoft Graph JSON Batch Custom Connector for Power Automate today, there is a great tutorial available in Microsoft Graph Docs. Visit Microsoft Graph Power Automate Tutorial<\/a> for step-by-step guidance.<\/p>\n

Please be sure to follow this blog series using https:\/\/aka.ms\/MSGraphMailbag<\/a> or with RSS using https:\/\/developer.microsoft.com\/graph\/blogs\/feed\/?tag=MSGraphMailbag<\/a>.<\/p>\n

Using built-in connectors vs. building your own custom connector<\/h2>\n

There are many out of the box Power Automate connectors that use the Microsoft Graph to communicate with specific endpoints of Microsoft products. However, there is no built-in connector that communicates directly with the Microsoft Graph to cover the entire API, so that some scenarios may require calling the Microsoft Graph directly from Power Automate flows.<\/p>\n

\"\"<\/p>\n

Addressing scenarios for calling Microsoft Graph directly, the HTTP connector in Microsoft Power Automate enables flexible integrations if you don\u2019t need to cache a user’s credentials. On the other hand, for the cases where you need to grant specific delegated permissions that require a user\u2019s credentials, a custom connector can be created to provide a wrapper around the Microsoft Graph API and enable consuming the API with delegated permissions. Another benefit of building a custom connector is to be able to leverage and reuse the same connector in various Power Automate flows for different scenarios.<\/p>\n

Why Microsoft Graph JSON Batch?<\/h2>\n

One of the scenarios that requires creating a Microsoft Graph custom connector could be automating the process of team creation and configuration on Microsoft Teams<\/strong>. For this scenario, we can create a custom connector that consumes Microsoft Graph Teams APIs to create a team. Additionally, we would like to add members and to create channels, then we will need to create new custom connectors for these actions.<\/p>\n

\"\"<\/p>\n

The more practical approach would be creating a custom connector for Microsoft Graph JSON Batch endpoint to enable multiple Microsoft Graph calls in Power Automate flows, so that we can reuse our custom connector in different Microsoft Graph related scenarios.<\/p>\n

Quick introduction to Microsoft Graph JSON batching:<\/strong> JSON batching let us combine multiple requests into a single JSON object, so we can make several requests in one HTTP call. For example, a client might want to compose a view of unrelated data such as:<\/p>\n