cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Union3008
Frequent Visitor

Power Platform ALM: Azure DevOps service connection permissions on Test/Prd environments?

As suggested by Microsoft, we have dedicated DEV environments for each business unit, and shared Test/Prd environments for deploying solutions to production.

 

For deploying solutions, we use Azure DevOps and Power Platform Build Tools in order to import solutions in Test/Prd using automated pipelines. As recommended, our AzDo pipelines authenticate to Power Platform using service connections with service principals and secrets.

 

The problem starts when Microsoft recommends giving the service connections System Administrator roles on the target environments. I am not sure how this is even a recommendation, as it allows a service connection to delete any solution deployed by other service connections, or even delete the whole production environment while at it.

 

To overcome this problem, we gave AzDo service connections the Environment Maker role instead, which gives them just enough permissions to create/update/delete solutions that they own/deployed. This is critical for our organisation as Business Units all have their own AzDo project, and one Business Unit should not be able to update/delete another Business Unit's solution.

 

However, when giving service connections the Environment Maker role, another problem appears when trying to import a solution that contains a Dataverse security role: A user (service connection) cannot create/import a security role that has more priviledges then itself. This means a simple security role that gives access to a dataverse table that is part of the imported solution is enough to throw an error since the Environment Maker role doesn't have access to custom entities. We considered giving service connections the System Customizer role but then it would give them access to all custom entities, and to be honest I am not sure of all other powers it could give against solutions deployed by other service connections...

 

I assume I am not the only one trying to automate deployments into shared Test/Prd environments, but I am still struggeling to find any relevant information on this specific subject. To me it seems like a major missing block that Microsoft brushes off their shoulders by recommending the use of System Administrator, but I don't see how this can be an option for any serious organisation? Anyone here tackled the problem?

 

Thanks!

3 REPLIES 3
Union3008
Frequent Visitor

For those interested, I opened a case with Microsoft and they pretty much said that in order to be able to import a solution that contains a Dataverse Role using the build tools, my only choices are :

- Give service connections System Administrator (Or System Customizer with the CreateRole/WriteRole added)

- Limite the use of service connections to a specific group of admins

 

The first option is obviously a security issue, the second option kind of goes against the purpose of Power Platform to empower users to build and deploy their own solution: it would decentralize the development to everyone but centralize all deployments towards a specific group of admin that will do this 24/7...

 

 

 

eleung83
Resolver II
Resolver II

You could expand the 2nd option by also making use of approval gates in your release pipelines in Azure devops and as well as applying security at an environment level so the users can do limited actions.

 

There are various ways you could control the security here:

1. Blocking users from being able to deploy manually to your Tst/Prod environments. They can do whatever they wish in Dev but perhaps only have read access to any other environment. This also ensures your environments always stay in sync with no random changes being applied to one environment inadvertently

2. Users could setup build and release pipelines that publish to DEV, but they wouldn't have any credentials nor access to service prinicpals to use/configure in Azure Devops, which means they wouldn't be able to setup deployments to any other environment. 

3. You could restrict users from being able to setup release pipelines and instead delegate that to a separate team, so that the users could only approve releases.

 

I have seen this kind of security applied previously where I have been able to setup releases to environments where we have sys admin access (which are only relevant for developers) but there is another person responsible for configuring the rest of the release pipeline to other environments where we have limited access, and approval gates have been setup so only certain groups of users can then approve releases before they go to a specific environment. This then puts the control over releases down to the users/approvers.

Union3008
Frequent Visitor

Yeah #1 is already done, users have read only access on Test/PRD which forces them to use a release pipeline in order to deploy.

 

We also have policies at the service connection level to make sure that releases using the PRD service connection have to come from the main branch, forcing developpers to do a pull request (which can enforce specific approvers) before releasing.

 

We will probably end up doing a mix of #2 specifically for releasing dataverse solutions: we want to let developers deploy by themselves as much as possible, but for deployments requiring the service connection to be Sys Admin (solutions with dataverse roles for example) these could be done by specific admins...

 

I just wish there was a way to let users deploy 100% by themselves without having a specific group of people to be a bottleneck in the deployment process, just like it's the case for our Azure service connections, which have access to create/update/modify/delete their own resources in azure but can't touch resources deployed by other Azure service connections. If Azure service connections had to be given Global Admin in azure in order to deploy resource groups it would be the same problem but it's not the case, to me it seems like a basic requirement in terms of ALM 😞

 

 

 

 

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

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!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

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

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

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.    

Updates to Transitions in the Power Platform Communities

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

Users online (849)