Best practices for Power Automate with service account

Hi jjdev-nz

We do exactly the same thing in our organisation. We created a normal user (not a service account in MS terms) equiped him with an E3, dynamics 365 license (for premium connectors) and a PA per user license. Then we migrated all business critical flows to this user and share the individual flow with the devs/owner of the flows for ajdustments. The user who owns the flows is managed centrally by a few users in the IT department.

This user only owns flows in a dedicated productiv environment where only he and the IT department is able to create any flows or apps.

For power apps we use additonally power apps per app license.

We came up with this solution/idea after reading the following part of "Establish an environment strategy" documentation from microsoft: https://docs.microsoft.com/en-us/power-platform/guidance/adoption/environment-strategy

But I'm still confused if we are acting correlty in the boundarys of microsofts power automate licensing.