Unanswered

Clarification of Service Principal Account and full licencing

(0) Share

Report

Posted on by gazzo1967

1,151

Hi
Can someone please clear this up for me regarding Service Principal Account (SPA).

Our Organisation has approx 3300 users predominately on E2 E3 licences.

I currently build all the Power Apps and Automate with my account without Premium Connectors.
But moving forward i have advised the organisation to create a service principal account with a better licence' so
1. Provide resilience for the organisation.. If i leave then everything still works after my account deleted.
2. so that the SPA can carry out some premium connector functions in the background (such as write SharePoint List data to a SQL Server) that i would like to run in the future not vast amounts but enough actions to warrant the increased licence cost.

Is this an 'OK' thing to do?

I have read a lot about this and even had it suggested in another post about this is good practice to have an SPA but wanted to check.
Apparently our IT Dept via their consultant are saying we can't do this!

regards Gary

Categories:

General topics

I have the same question (0)

All responses (3)

Answers (0)

Jay-Encodian 2,920 on at

Like (0)

Report

Hey @gazzo1967

Using a 'service account' for Flow for connection authentication or even actual flow creation is just good practice IMHO.

All to often connections are created using the Flow authors account... and when there is an issue with the account or they leave an organization the Flows fail.

What you can't do (my understanding) is license the service account for premium features, and then allow no-premium licensed users to use that flow... any benefiting user should also have a license which permits premium. From memory... and would need validation, if the Flow is invoked via SharePoint library associated Flow, this doesn't apply.

But.... you really need to verify this with your reseller directly, whilst I'm possibly correct today I may not be in 6 weeks time! 🙂

A good resource to review: https://docs.microsoft.com/en-us/power-platform/admin/pricing-billing-skus

HTH

Jay

Was this reply helpful? Yes No
gazzo1967 1,151 on at

Like (0)

Report
@Jay-Encodian
Hi
thank you for the response maybe would help if i was clearer in my explanation of use
Example
A user Powerapp developed to gather data and inserted into a sharepoint list.

Flow runs in back ground that sends out confirmation email etc
Currently this is done by my user account and is all working but want it done via an SPA.

Then under the SPA i can have a separate flow that will copy the data from the sharepoint list and put it into an SQL Server (which requires a Premium Connector)
The SPA will not be running any Premium connectors directly from a user powerapp to write directly to SQL..
The reasoning behind this is access.. teams of people can happily access sharepoint lists but we dont want the going into the database directly which is essentially going to be a data archive/warehouse

hopefully that makes sense:)
Gary

Was this reply helpful? Yes No
Jay-Encodian 2,920 on at

Like (0)

Report

Hi @gazzo1967

I can see the greyness of the scenario as you could argue that the Flow which moves data to SQL isn't part of the app.

Personally, I think this is tenuous as you have a PowerPlatform solution which is accessed by X number of users, and part of the solution uses a premium connector to add data to SQL. Therefor, all users using the solution should be licensed for premium connectors.

However, run it through with your Microsoft account contact or your reseller to get confirmation.

HTH

Jay

Was this reply helpful? Yes No