Forum Discussion
Licensing for Premium Connectors
Ryan,
Both the app creator and consumer will need to have a P1 or P2 license.
Ryan Stone, what BrianTJackett says is incorrect. Only the maker has to get Flow plan 1/2. The rest of the company can use the Flow.
It's not the most straightforward messaging, but you only need P1 or P2 for the maker.
MicrosoftDaniel Laskewitz I'm checking around internally for verification. The latest threads I've seen have some nuance to them. The most straightforward answer I see is that whichever user / account is used for the connection to the Premium Connector requires the Plan 1 / 2 license. Not simply a matter of the author vs. flow executor.
If User A authors a flow and uses their own credentials (User A) for the connection and then User B uses the flow (still with User A credentials tied to the connection for Premium Connector) then only User A needs a Plan 1 / 2 license.
If however User A authors a flow and User B uses their own credentials in the connection for Premium Connector then User B needs to have a Plan 1 / 2 license.
Hoping to get someone from Flow PG to comment / verify on here, stay tuned.
- Correct! In my answer, assumption was made that the maker would connect to the premium connector.
I frequently create flows under a service account, connect to a premium connector with that service account (which has P1/P2) and then I use the Flow in different places (sometimes PowerApps, sometimes the Flow runs on the "SharePoint - When an item is created" trigger, etc).Daniel Laskewitz
If I read the following article it seems like the users are the ones that has to have the P1 or P2 license, not the maker?
https://techcommunity.microsoft.com/t5/Office-Retirement-Blog/UPDATED-Updates-to-Microsoft-Flow-and-PowerApps-for-Office-365/ba-p/289589https://docs.microsoft.com/en-us/microsoft-365/community/powerplatformlicensingforcitizendeveloper#practical-application
Use of "service accounts" in many platform integrations can bring challenges in terms of security management and compliance with licensing agreements with various software vendors. Always use caution when recommending/implementing this in platform projects to avoid to expose your client to risks.
Also when a user will want to use a premium connector configured by admins, he will be asked to authenticate to connect to the other service (e.g. Sales Force, Service Now, etc, …) Not sure IT Admin will want to share service accounts credentials.
