Home

Flow licensing for HTTP connector

%3CLINGO-SUB%20id%3D%22lingo-sub-816508%22%20slang%3D%22en-US%22%3EFlow%20licensing%20for%20HTTP%20connector%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-816508%22%20slang%3D%22en-US%22%3E%3CP%3EThere%20is%20lot%20of%20conflicting%20advice%20about%20licensing%20required%20for%20HTTP%20Connector.%20Microsoft's%20decision%20to%20make%20this%20a%20premium%20connector%20has%20really%20complicated%20our%20licensing%20structure.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EScenario%201%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3EA%20Flow%2C%20'Main%20Flow'%2C%20is%20triggered%20from%20SharePoint%20list%20item%20creation%2Fupdate.%20This%20flow%20triggers%20another%20flow%20using%20HTTP%20connector.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EScenario%202%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3EA%20Flow%20'Request%20flow'%20is%20triggered%20from%20SharePoint%20list%20item%20creation%2Fupdate.%20This%20flow%20triggers%20another%20flow%2C%20'Provisioning%20Flow'%20using%20HTTP%20connector.%20Provisioning%20Flow%20itself%20uses%20HTTP%20connector%20to%20invoke%20graph%20API.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20scenario%201%20%26amp%3B%202%2C%20how%20many%20P1%20licenses%20are%20required.%20Does%20the%20developer%20building%20the%20Flow%20needs%20P1%20license%20whereas%20users%20able%20to%20create%20or%20update%20list%20items%20in%20SharePoint%20can%20stay%20with%20O365%20E3%3F%20Or%20does%20everyone%20(developer%20as%20well%20as%20users%20with%20permissions%20on%20the%20List)%20need%20a%20P1%20license%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EReally%20hoping%20for%20some%20Microsoft%20guidance%20to%20solve%20this%20conundrum%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-816508%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EHTTP%20Connector%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ELicensing%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Flow%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-818014%22%20slang%3D%22en-US%22%3ERe%3A%20Flow%20licensing%20for%20HTTP%20connector%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-818014%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F79705%22%20target%3D%22_blank%22%3E%40Gurdev%20Singh%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThey're%20changing%20the%20licensing%20structure.%20To%20get%20access%20to%20premium%20connectors%20you'll%20have%20to%20either%20do%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20'Flow%20Per%20User'%20License%3A%20%2415%2Fuser%2Fmonth%20with%20a%20minimum%20of%2020%20users.%3C%2FP%3E%3CP%3EOR%20'Flow%20per%20Business%20Process'%20%24500%2Fmonth%20for%205%20active%20workflows.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUsing%20the%20current%20licensing%20structure%2C%20I%20believe%20the%20creator%20alone%20would%20need%20a%20P1.%26nbsp%3B%20The%20flow%20would%20essentially%20run%20as%20the%20creator.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Gurdev Singh
Contributor

There is lot of conflicting advice about licensing required for HTTP Connector. Microsoft's decision to make this a premium connector has really complicated our licensing structure.

 

Scenario 1

A Flow, 'Main Flow', is triggered from SharePoint list item creation/update. This flow triggers another flow using HTTP connector.

 

Scenario 2

A Flow 'Request flow' is triggered from SharePoint list item creation/update. This flow triggers another flow, 'Provisioning Flow' using HTTP connector. Provisioning Flow itself uses HTTP connector to invoke graph API.

 

In scenario 1 & 2, how many P1 licenses are required. Does the developer building the Flow needs P1 license whereas users able to create or update list items in SharePoint can stay with O365 E3? Or does everyone (developer as well as users with permissions on the List) need a P1 license?

 

Really hoping for some Microsoft guidance to solve this conundrum?

1 Reply

@Gurdev Singh 

They're changing the licensing structure. To get access to premium connectors you'll have to either do:

 

The 'Flow Per User' License: $15/user/month with a minimum of 20 users.

OR 'Flow per Business Process' $500/month for 5 active workflows.

 

Using the current licensing structure, I believe the creator alone would need a P1.  The flow would essentially run as the creator.

 

 

 

Related Conversations
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
flashing a white screen while open new tab
cntvertex in Discussions on
14 Replies
Tabs and Dark Mode
cjc2112 in Discussions on
23 Replies
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
28 Replies