Hello,
Calling @timl, @wyotim, @Anonymous, @mr-dang, @v-monli-msft, @CarlosFigueira and all PowerAppers.
I'd like to show our admins the power of the PowerApp community by crowdsourcing some experiences here if possible.
We're doing longetivity planning for PowerApps within our organization and I'd love some community input on the best practices for the following considerations:
Your insights are really appreciated!
Thank you
Solved! Go to Solution.
Hi Eric,
These are good questions. Setting up multiple environments for Dev, UAT, Prod, etc. is a good best practice. I would recommend it. I am also in favor of service accounts. I had wished you were able to join us last Wednesday and Thursday--many of these topics had come up.
I'm not sure what everyone's handle is on the forum (those who were at the events), but perhaps one of them can share more granularity about service accounts and using environments. Depending on details of setup, some sensitive content might be better suited for PM or email.
@emckinney81 @MartinLee @KeithWhatling
Here's some briefs on what's coming up for admins:
And a shortcut to all the notes about the Road Map:
https://aka.ms/businessapplicationsreleasenotes
Brian
Hi ericonline
I am currently using an AD 'service account' for the purpose of publishing and sharing apps within my company (power.apps@xxx.com). Considerations were:
I actually develop the apps on my account and once they are 'finished' I extract them and import them into the Power.Apps account which is very simple. For example, Flows associated with the app are automatically extracted and recreated.
I am currently publishing all apps within the same environment.
So far this is working very well! 🙂
Hi ericonline
I am currently using an AD 'service account' for the purpose of publishing and sharing apps within my company (power.apps@xxx.com). Considerations were:
I actually develop the apps on my account and once they are 'finished' I extract them and import them into the Power.Apps account which is very simple. For example, Flows associated with the app are automatically extracted and recreated.
I am currently publishing all apps within the same environment.
So far this is working very well! 🙂
Hi ericonline
I am currently using an AD 'service account' for the purpose of publishing and sharing apps within my company (power.apps@ooo.com). Considerations were:
I actually develop the apps on my account and once they are 'finished' I extract them and import them into the Power.Apps account which is very simple. For example, Flows associated with the app are automatically extracted and recreated.
I am currently publishing all apps within the same environment.
So far this is working very well! 🙂
Awesome feedback, thank you @DanielaH!.
Can I ask you:
Hi Eric,
These are good questions. Setting up multiple environments for Dev, UAT, Prod, etc. is a good best practice. I would recommend it. I am also in favor of service accounts. I had wished you were able to join us last Wednesday and Thursday--many of these topics had come up.
I'm not sure what everyone's handle is on the forum (those who were at the events), but perhaps one of them can share more granularity about service accounts and using environments. Depending on details of setup, some sensitive content might be better suited for PM or email.
@emckinney81 @MartinLee @KeithWhatling
Here's some briefs on what's coming up for admins:
And a shortcut to all the notes about the Road Map:
https://aka.ms/businessapplicationsreleasenotes
Brian
Hi ericonline,
Yes we were having the same discussion around security/governance, but the need to run apps through a generic account was simply unavoidable. You could restrict the account to not have access to the network, or force the O365 license to only run predefined applications (PowerApps, Flow, whatever the account needs access to) to reduce the security concerns.
I think security will never be happy with generic accounts and the best you can do is limit what someone 'could' do with it if they gained access.. 😉
Will be interesting to hear the recommendations and tips of others.
Thank you again for the great feedback.
Continuing the convo if you have the time:
Hi ericonline
Good point.. this was just one of the suggested solutions I received from our security guys, which I dismissed in our case since the apps need access to SharePoint. We essentially restrict what applications the account can run, if it can only run PowerApps and access the data source the security concerns are reduced I guess. 😉
Great resources. Thank you very much @mr-dang.
User | Count |
---|---|
140 | |
137 | |
77 | |
77 | |
71 |
User | Count |
---|---|
226 | |
180 | |
68 | |
68 | |
58 |