Regarding PowerApps the same best practice can be troublesome because datasource connections run in the context of the user opening the PowerApp. Regarding Flow my best practice indeed is to use a generic service account and share Flows with Co-owners. Flows and PowerApps are built under my account and shared with our AppDev Admin so he's able to view and edit them if I'm not available.ĭoes your service account have full licensed access to everything with a G1/E1 license? How do you setup security on the service account so nobody uses it? For the other connections I use either my unlicensed Azure Admin account (Azure searches) or my regular O365 account (for email). I have an unlicensed service account in Azure for any SharePoint connections, with admin access to all sites. I've been wondering the same thing from a best practice perspective. Do I use service account(s) that have "God" like permissions? What are my options? I don't want to use individual user accounts because what if that user leaves the company or switches departments and there permissions change (maintenance nightmare). At the moment all the connectors I'm using are under the O365 umbrella of apps. I've been playing around with flow and powerapps for a couple of months now and I'm starting to actually create some enterprise solutions for the company but I don't want my account to be used for the connectors. That way, if your account is removed from the corporate system, some-one else can take over from the Service Account and share as required. To switch a Flow (there may be other ways) when first setting up, log in as the service account, then make a copy, turn this one on and then the one under your name off. Your question is quite valid - I use a generic service account and make it the owner of all PowerApps and Flows and then share them with myself as co-owner. Subject: What Account to use for Connections
0 kommentar(er)
