Network location Licensing
Hi, It says in the article below that to restrict access by the network locations IP address from the SharePoint web admin portal you need AD P1/P2 https://docs.microsoft.com/en-us/sharepoint/control-access-based-on-network-location but in this article albeit a lot older it says you don't need azure ad premium. https://techcommunity.microsoft.com/t5/microsoft-sharepoint-blog/introducing-conditional-access-by-network-location-for/ba-p/39274 was the licensing requirements changed at some point? If it was do you need just 1 license or would you need to license all users in your O365 tenant?
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?
SharePoint Licensing when migrating
For our current on-premise SharePoint environment (2010), we have 7 licenses and we are allowed to install 2019 if we like. I want to first setup 2019, build the sites, test it, and then migrate content. If the licenses are currently being used, how do I install 2019 without transferring the license over first? Is there a trick to it? How does everyone handle this?