License Requirements for Built-In HTTP-Actions

Like (1) Share

Report

Posted on 27 Sep 2024 11:59:30 by TGX

Hi :)

a colleague of mine noticed a change of the built-in HTTP-Actions when using the new Flow Designer.

Previously the Runtime-Value has been Premium for these Actions, however in the new Designer, they changed it to in-app / Built-In.

In Addition in The Power Platform Admin Center, when Checking Our DLP Policies the Connector-Class for the HTTP-Connector is now "integrated" (rather than "Premium").

So we wondered if there has been a change in the required License for using the HTTP-Actions.

In the List of my Flows, the Created Flows with HTTP-Actions still show the Diamond (Premium Icon).

However if I Try To run them, with a Standard-License (like M365-licenses) they run without any further required addional licensing.

Finally i tried to connect a Flow with an HTTP-Action to a Canvas App.

After Publishing the App. The License Requirement still said "Standard" and i was able to run the app without any problems.

So in Conclusion all signs point towards a switch for the licensing requirements regarding the HTTP-Connector, but i wasnt able to find any definitive proof by Microsoft to confirm this.

Does anyone have some official Information or Blogposts regarding this topic?

Thanks for any answers in advance and have a nice day :)

Categories:

Licensing

I have the same question (0)

All responses (2)

Answers (0)

Suggested answer

Pstork1 68,214 Most Valuable Professional on 27 Sep 2024 at 12:58:57

Like (0)

Report

License Requirements for Built-In HTTP-Actions

I don't believe there has been any reclassification of the HTTP connector for licensing purposes. It has been reclassified to make it easier to find. But to use HTTP REST calls with a standard license you still need to use one of the actions that embeds that in a different connector like SharePoint or Groups. As you point out the documentation still lists it as Premium. The fact that you can run it with a standard license just means the software doesn't catch the requirement for premium. That happens occasionally, but doesn't change the legal licensing requirement. As you can see its still marked premium when you make a new connection.

Was this reply helpful? Yes No
TGX 24 on 27 Sep 2024 at 13:13:01

Like (0)

Report

License Requirements for Built-In HTTP-Actions

Thanks for your Input @Pstork1 :)

The Screenshot you provided lists the HTTP With Microsoft Entra ID Connectors.

You are correct that these are still Premium Connectors, and they are correctly labeled across the board (Old Designer, New Designer, Admin Center) and they are behaving as expected (requiring a Premium License to execute).

However The Connector i am refering to is the built in HTTP-Action which does not require any Authorization through Entra ID.

This Connector does not need any connection and in return is not listed as an option under connections.

As you pointed out, just because something does work without a license, does not mean it is allowed/legal.

Thats the reason i want to gather more information about the topic to make an informed decision going forward.

Was this reply helpful? Yes No