Power Automate’s Super Connector: The HTTP with Microsoft Entra ID

In the Power Platform, there’s no shortage of connectors—over a thousand, in fact. But which one takes the crown as the ultimate connector? The answer is likely not what you’d expect. Drumroll, please… It’s the HTTP with Microsoft Entra ID (preauthorized) connector. Specifically, the “Invoke an HTTP request” action.

Let’s dive in, shall we?

Why It’s Powerful (Like a Sizwe Dhlomo tweet, but in connector form)

This connector is essentially the Swiss Army knife of Microsoft’s ecosystem. In theory, it’s a universal connector that lets you tap into any Microsoft API you’re authorized to use. In layman’s terms, if it’s an API, this connector can help you call it. You can even access endpoints that are undocumented. Basically, it’s your backstage pass to the Microsoft world.

It’s perfect for those times when the connectors you need just don’t exist. Fancy an HTTP version of the Admin connectors? Well, now you’ve got one. You can even fetch flow logs directly, without having to mess with Dataverse. The options are endless—well, almost.

How to Use It (It’s like setting up a braai, but with APIs)

To use this connector, you’ll need to specify a couple of things: the root URL and the resource principal URL. The root URL is the base URL of the API you want to access (think https://graph.microsoft.com/ or https://api.flow.microsoft.com/), while the resource principal URL is the permission you need for the API.

Quick tip: Most of the time, you can just use the root URL for the resource principal. But don’t get too comfortable—sometimes the .default scope will mess with your plans, especially if the resource has a custom endpoint.

The Problems (Because no good thing is without its flaws)

First off, there’s a UI quirk: you can’t create connections in the new UI. It’s like trying to find a parking spot at Canal Walk on a Saturday—frustrating. But don’t worry, just switch to the Classic UI, create the connection, then switch back.

Next, the scope setup is a bit tricky for non-techy users, meaning it could lead to some support tickets from people who don’t quite get the whole URL and permission thing.

Finally, admins beware: This connector opens up a lot more options than you might realise, and it’s not the easiest to track through DLP policies.

Final Thoughts

So, is it the connector for everyone? Probably not. It’s overkill for simpler tasks, and you’re better off sticking to more specific connectors in those cases. But when you need something more flexible (and you’ve got the right permissions), the HTTP with Microsoft Entra ID connector is your MVP.

Power Automate’s Super Connector: use it wisely, and you’ll have access to an entire universe of possibilities.

Source Info: https://dev.to/wyattdave/power-automate-the-super-connector-3gbe