AMA: multiplexing rules

[takolota]

Do multiplexing rules apply to both destination data-sources & the methods of transmitting data, or just to the methods of transmitting data?

For example, if I make a Logic App on a consumption plan to sync a SharePoint list & SQL database, what are the rules & licensing requirements?

Given it is a consumption license like a per-flow license, can I run this without all the SP users needing licenses?

https://docs.microsoft.com/en-us/power-platform/admin/power-automate-licensing/faqs

  

If my understanding is correct, this may depend on whether a SQL server is licensed by Cores or by CALs (Client Access Licenses).
https://metrixdata360.com/license-series/sql-server-licensing-explained/

So would the end users need a premium license if the consumption-plan Logic App used premium connectors?

And even if they did need a license for premium actions, Logic Apps has many standard connectors for things, like SQL, that are usually premium in regular Power Automate flows. So even just their E3 or E5 license would cover them for any Logic Apps standard connectors. Correct?

Is this a valid reading of the policies?

[Pstork1]

I know this kind of ducks the question, but doesn't calling a Logic App use a custom connector or an HTTP call?  So it would already require a premium license no matter what connectors the logic app uses.

[PriyaKodukula · Accepted solution]

For example, if the flow is talking to a sql server connector(premium) and the flow is invoked by 100 users. To be compliant below licenses are needed, 

1. All the users need a premium Power Automate per user license or the flow needs a Per flow license(recommended)

And

2. All the users need sql server licenses 

[takolota]

@PriyaKodukula @Pstork1 

No, in this example case I’m talking about directly connecting a Logic App to a SharePoint list. So there is no separate flow with an HTTP request.

Also the SQL connector is not premium in Logic Apps.

That does get to my actual use-case though where I found a reliable way to connect a Power App to a Logic App flow using only standard connectors & no HTTP call.

And from the SQL documentation, I do not think all the users need a SQL license if it’s using Cores licensing which also isn’t a user-based licensing.

https://metrixdata360.com/license-series/sql-server-licensing-explained/

See at this point I believe I have a way to interact with SQL data in anything a Logic App on a consumption plan can connect to and a way to indirectly interact with SQL data from Power Apps with only the E3 & E5 licenses my users already have.

From what I’ve read it seems to comply with each part of Microsoft policies. Now I’m more curious that if Microsoft notices more people doing it the way I found, will they go & change their future policies & rules to try to prevent losing some revenue?

[takolota]

@PriyaKodukula @Pstork1 

So even if there is some licensing requirement for premium connectors, my method from Power Apps to Flow to Logic Apps to SQL doesn’t include anything designated as a premium connector.

Thus it should fall under the last bullet point in this documentation:

[PriyaKodukula]

@takolota - If there are no Power Automate Flows in this solution, probably the question should be posted in Logic Apps/Power Apps forum to get the right audience