Some of the key questions I have are around permissions and owners of the app:
- If an app is created by a Power Apps admin then that admin is deleted, will the app still function?
- If a connector is created by a Power Apps admin then that admin is deleted, will that connector still function?
- If an app or connector is created by a Power Apps admin will the app run under that specific user? if so are there any issues that we may come across if this is the case, for example limitations etc.
- Is it necessary or good practice to use a "service account" for each Power App created instead of creating it under an actual admin user account? what are the benefits doing it this way?
- If we were to create a "service account" for each app, will this account require the same permissions and license as well as access to data sources and connectors to build apps?
- If we were to use a "service account" if the password expires or the account is deleted will it have any impact to existing apps or connectors created by this service account?
- Are there any considerations or limitations that we need to consider when designing and managing our environment going forward?
Please help me on my queries.
Solved! Go to Solution.
Hi @MeghanaMothiki I will respond within every point.
1 - If an app is created by a Power Apps admin then that admin is deleted, will the app still function?
R: Yes the Power Apps will still working. Also this Power App it will be catalogued as orphaned Power App.
2 - If a connector is created by a Power Apps admin then that admin is deleted, will that connector still function?
R: No, it not will work because the connector use the user identity to connect.
3 - If an app or connector is created by a Power Apps admin will the app run under that specific user? if so are there any issues that we may come across if this is the case, for example limitations etc.
I can not understand 😕 Please provide me more info and I will try to help you 🙂
- Is it necessary or good practice to use a "service account" for each Power App created instead of creating it under an actual admin user account? what are the benefits doing it this way?
R: Yes it's a good practice! It is recomendet because when you have a lot of users creating Power Apps and some of these leave the company you will have many problem, with a service account you prevent that. It's highly recommended for Production app.
- If we were to create a "service account" for each app, will this account require the same permissions and license as well as access to data sources and connectors to build apps?
R: In my opinion I think that you don't need to create a service account for each Power App. But replying to you question, if the service account just will need to create (maker) you don't need to acquier a premium license, in developing you don't need premium license it is required only when you want to run Power App as a normal user.
- If we were to use a "service account" if the password expires or the account is deleted will it have any impact to existing apps or connectors created by this service account?
R: Yes. Power Apps it will be still working as an orphaned app but connectors can't will connect and you will need to reconnect with another account.
- Are there any considerations or limitations that we need to consider when designing and managing our environment going forward?
R: Yes I recommend this points:
Detect which Power Apps are critical and what are not. For example if you have a Power App that afects to the entire organization that will be catalogues as Critical in that case I recomend to create 3 environaments (Dev, Test, Prod).
Not share with individual users, user Azure AD security groups.
Implement DLP.
Create a service account by Tenant or by Environment. In some cases it could be interesting to create a service account for a specific Power Apps.
I hope it helps!
Have nice day 🙂
Hi @MeghanaMothiki I will respond within every point.
1 - If an app is created by a Power Apps admin then that admin is deleted, will the app still function?
R: Yes the Power Apps will still working. Also this Power App it will be catalogued as orphaned Power App.
2 - If a connector is created by a Power Apps admin then that admin is deleted, will that connector still function?
R: No, it not will work because the connector use the user identity to connect.
3 - If an app or connector is created by a Power Apps admin will the app run under that specific user? if so are there any issues that we may come across if this is the case, for example limitations etc.
I can not understand 😕 Please provide me more info and I will try to help you 🙂
- Is it necessary or good practice to use a "service account" for each Power App created instead of creating it under an actual admin user account? what are the benefits doing it this way?
R: Yes it's a good practice! It is recomendet because when you have a lot of users creating Power Apps and some of these leave the company you will have many problem, with a service account you prevent that. It's highly recommended for Production app.
- If we were to create a "service account" for each app, will this account require the same permissions and license as well as access to data sources and connectors to build apps?
R: In my opinion I think that you don't need to create a service account for each Power App. But replying to you question, if the service account just will need to create (maker) you don't need to acquier a premium license, in developing you don't need premium license it is required only when you want to run Power App as a normal user.
- If we were to use a "service account" if the password expires or the account is deleted will it have any impact to existing apps or connectors created by this service account?
R: Yes. Power Apps it will be still working as an orphaned app but connectors can't will connect and you will need to reconnect with another account.
- Are there any considerations or limitations that we need to consider when designing and managing our environment going forward?
R: Yes I recommend this points:
Detect which Power Apps are critical and what are not. For example if you have a Power App that afects to the entire organization that will be catalogues as Critical in that case I recomend to create 3 environaments (Dev, Test, Prod).
Not share with individual users, user Azure AD security groups.
Implement DLP.
Create a service account by Tenant or by Environment. In some cases it could be interesting to create a service account for a specific Power Apps.
I hope it helps!
Have nice day 🙂
Thanks for your reply.
Additional Q Regarding the “Send an Email (V2)” connector. Based on the below screenshot, if I enter a “Send As” address, do I need to make sure that the users that run this app have send as permissions to the mailbox I enter here? If not how does this work?
Hi @MeghanaMothiki !!
When you use a Outlook connector to send an email you will need that the user that is runing this Power Apps have Outlook to be allowed to send mails. Realize that when a user runs a Power Apps they will ask for a Outlook account to continue running.
Also here we can do 2 aproach if you don't need to send that email with the user identity that is running the Power App you can use a service account! But if you need to send that email with the indentity of the user that is running the Power Apps, yes you will need a license to allow that user send emails/user outlook.
I hope that is useful for you!!
Please let me know if you have more doubts. 🙂
Dear Community Members, We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd. During this period, members will not be able to Kudo, Comment, or Reply to any posts. On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities. What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!
We are excited to announce the Summer of Solutions Challenge! This challenge is kicking off on Monday, June 17th and will run for (4) weeks. The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions in the Forums to as many questions as you can. Answers can be provided in all the communities. Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”) - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024 Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods. You must enter into each weekly Entry Period separately. How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different. Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers. At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing. Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner. A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random. Individuals will be contacted before the announcement with the opportunity to claim or deny the prize. Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners. Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event. ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE** Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber of SolutionsSuper UsersNumber of Solutions @anandm08 23 @WarrenBelz 31 @DBO_DV 10 @Amik 19 AmínAA 6 @mmbr1606 12 @rzuber 4 @happyume 7 @Giraldoj 3@ANB 6 (tie) @SpongYe 6 (tie) Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersSolutionsSuper UsersSolutions @anandm08 10@WarrenBelz 25 @DBO_DV 6@mmbr1606 14 @AmínAA 4 @Amik 12 @royg 3 @ANB 10 @AllanDeCastro 2 @SunilPashikanti 5 @Michaelfp 2 @FLMike 5 @eduardo_izzo 2 Meekou 2 @rzuber 2 @Velegandla 2 @PowerPlatform-P 2 @Micaiah 2 Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27 Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8 SunilPashikanti8
On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners. The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights. Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.
We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for. We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer. Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together. Here's to new beginnings and endless possibilities! If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport. To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages