Hi,
we are an organization have +2000 users. all users have E3 or E5 license. We are planning to make some applications with power apps and power automate. such as travel requests, vacations, claims, form approvals and so on.
my questions here,
Please I need the best practice and design recommendation.
Thank you
Solved! Go to Solution.
In that case you will want to use the button trigger so the flows run under each user’s account & you will want to avoid any premium or non-standard connectors in both the app & the flows.
Those licenses will be enough for Power Apps using only standard connectors. So this usually limits you to datasources like Excel or preferably SharePoint that use standard connectors.
The developer doesn’t technically need a per user or greater license if you only plan to use standard actions in Power Automate. But you may just want to pay the $15/mo to ensure some user can use premium connectors in non-button (scheduled or cloud) triggered flows.
I usually use a service account as the owner of all the apps & automations to ensure easier succession planning if someone leaves.
Be aware if you are using a button trigger like a Power Apps trigger, and you use a premium action in that flow, then every end user will need a premium license or you will need to license the flow instead of the users.
thank you for the info, one question, as I mentioned we are +2000 users and I am going to use one service account as the owner of all applications. but i will face an issue that each user will access the app and trigger a flow, will be triggered under the owner account which is the flow maker instead of the user account. is there a way to make the flow whenever is triggered will be triggered by the user account not the owner. as each user has 2000 request API per day as well as the owner account. if all users will use the apps and flows triggered under the owner account, I don't think 2000 request API are enough for +2000 users!
Thanks
In that case you will want to use the button trigger so the flows run under each user’s account & you will want to avoid any premium or non-standard connectors in both the app & the flows.
User | Count |
---|---|
26 | |
14 | |
12 | |
10 | |
8 |
User | Count |
---|---|
51 | |
29 | |
28 | |
24 | |
20 |