web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / Designated App Owner A...
Power Apps
Answered

Designated App Owner AD Best Practices

(2) ShareShare
ReportReport
Posted on by Microsoft Employee

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:

 

  • Is anyone utilized AD "service accounts" or the like, for app authoring instead of individual user accounts? 
    • Ex: "powerapps@mycompany.com" vs. "eric@mycompany.com"
    • If so, what are some considerations before embarking?
      • AD Security
      • Account permission issues
      • Connector issues
      • Governance experience, etc.
  • Is anyone utilizing different PowerApps environments for specific purposes? 
    • Ex1: Dev, Trial, Prod
    • Ex2: Environment for each department or team
    • If so, what are some considerations before creating these env's?
      • We found one already: On-prem Data Gateway only works in the Default env. 

Your insights are really appreciated!


Thank you

Categories:
I have the same question (0)
  • Community Power Platform Member Profile Picture
    Microsoft Employee on at

    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:

     

    • Account needs to have sufficient O365 license to ensure the account can use anything it needs including PowerApps, Flow, SharePoint, Power BI, etc...  we provided an E3 license. 
    • The benefit is that 'Power Apps' now appears as an app author not my individual name.
    • Key reason was that IT can now support PowerApps through this account, rather than everything running through my individual account.
    • Account needs to be granted permission to anything it uses, specifically the database. I primarily work with SharePoint lists so I just share those with this account.

    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! 🙂

     

  • Community Power Platform Member Profile Picture
    Microsoft Employee on at

    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:

     

    • Account needs to have sufficient O365 license to ensure the account can use anything it needs including PowerApps, Flow, SharePoint, Power BI, etc...  we provided an E3 license. 
    • The benefit is that 'Power Apps' now appears as an app author not my individual name.
    • Key reason was that IT can now support PowerApps through this account, rather than everything running through my individual account.
    • Account needs to be granted permission to anything it uses, specifically the database. I primarily work with SharePoint lists so I just share those with this account.

    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! 🙂

     

  • Community Power Platform Member Profile Picture
    Microsoft Employee on at

    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:

     

    • Account needs to have sufficient O365 license to ensure the account can use anything it needs including PowerApps, Flow, SharePoint, Power BI, etc...  we provided an E3 license. 
    • The benefit is that 'Power Apps' now appears as an app author not my individual name.
    • Key reason was that IT can now support PowerApps through this account, rather than everything running through my individual account.
    • Account needs to be granted permission to anything it uses, specifically the data source. I primarily work with SharePoint lists so I just share those with this account.

    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! 🙂

     

  • Community Power Platform Member Profile Picture
    Microsoft Employee on at

    Awesome feedback, thank you @Anonymous!. 

     

    Can I ask you: 

    • Do you have any governance around the use of the service account? 
    • I know our security dept does NOT like to use generic accounts.
    • How have you all addressed this piece?
  • Verified answer
    Brian Dang Profile Picture
    3,976 on at

    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 @Anonymous

     

    Here's some briefs on what's coming up for admins:

    https://docs.microsoft.com/en-us/business-applications-release-notes/October18/powerapps/trusted-enterprise-grade-platform-for-administrators

     

    And a shortcut to all the notes about the Road Map:

    https://aka.ms/businessapplicationsreleasenotes

     

    Brian

  • Community Power Platform Member Profile Picture
    Microsoft Employee on at

    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.

  • Community Power Platform Member Profile Picture
    Microsoft Employee on at

    Thank you again for the great feedback. 

     

    Continuing the convo if you have the time: 

    • If the service account (for lack of a better term) doesn't have network access, do you know if it can still be used to author a PowerApp that has Flows or Sends Emails? 
  • Community Power Platform Member Profile Picture
    Microsoft Employee on at

    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. 😉

  • Community Power Platform Member Profile Picture
    Microsoft Employee on at

    Great resources. Thank you very much @mr-dang.

  • wyotim Profile Picture
    2,545 on at

    @ericonline, it is an honor to be called out, especially given the others you mentioned as well. Thanks for that!

     

    Unfortunately, I have little to add as we don't currently use separate environments or service accounts, though the service account idea is on my radar. Full disclosure: the company I work for is pretty small and I am the sole tech/data employee. As such, I have only used my company account to create things in PowerApps as it was just easier to do so. Smiley Embarassed

     

    That said, I will offer one practice that I have been using in lieu of environments. One way I track what level of access the app is by the color of the app icon. Pretty simple but it is decently effective. For example, our field supervisors get red apps, our office apps are blue, and test apps are yellow. Incidentally, I do a similar thing with our PowerBI reports by using color schemes.

     

    I also have a similar practice to @Anonymous when it comes to publishing apps. I found that things would get a bit funky for our field employees when I would make changes to apps and not publish them. So I started the practice of having parallel test apps where I can develop changes or add features at my leisure and then replace the production versions when things were ready to go out. This gives a bit better version control as well and could make for easily segmented test and production groups if needed.

     

    Great topic and I look forward to learning from what others are doing!

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the June Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Apps

#1
WarrenBelz Profile Picture

WarrenBelz 326 Most Valuable Professional

#2
11manish Profile Picture

11manish 168

#3
sannavajjala87 Profile Picture

sannavajjala87 75 Super User 2026 Season 1

Last 30 days Overall leaderboard