Flow licensing for HTTP connector
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?
HTTP Method Vulnerabilities
I am new to this security remediation task. I have resolved some vulnerabilities using the IIS Mgr when it is available but in my most recent tasks, these vulnerabilties are showing up on Windows servers that do not have IIS installed and thus NO IISMgr. How do I resolve these HTTP Method vulnerabilties?