HTTP with Microsoft Entra ID connector
There are two similar http connectors for Microsoft Entra ID in Power Automate:
HTTP with Microsoft Entra ID (preauthorized)
HTTP with Microsoft Entra ID
Both connectors are premium and don't have triggers; hence, they need something else to trigger the flow like Microsoft Forms, SharePoint, or manually triggering the flow.
HTTP with Microsoft Entra ID (preauthorized)
This connector is used to fetch resources from various web services (SharePoint API, Dataverse API) that are already authenticated by Microsoft Entra ID or from an on-premises web service.
The following screenshot shows the two actions that are currently available: Get web resource and Invoke an HTTP request.
You can use the Get web resource action to retrieve web resources by issuing an HTTP GET request.
The Invoke an HTTP request helps you access data from an endpoint by using one of the known HTTP verbs, such as GET, DELETE, PATCH, POST, and PUT.
A couple of currently known issues and limitations of the HTTP with Entra ID connector are:
The connector encodes the request body into base64 encoding; hence, it should be used to call network services that expect the request body in this format. You can't use this connector to call a network service that expects the request body in raw binary format.
If you get an error similar to { "error": { "code": "Forbidden", "message": "" } }, it could be because this connector has a limited set of scopes. If your scenario requires something more advanced, make sure that you use the HTTP connector or create a custom connector.
The throttling limit for the API calls per connection is 100 calls for every 60 seconds. For more information, see known issues and limitations.
An example of using the HTTP with Entra ID (preauthorized) connector is invoking an HTTP request to Microsoft Graph to get the logged in users information.
