Both my colleague and I are designated Power Platform Admins for our business units, yet he’s automatically assigned as co-owner on all new apps (and as System Administrator in newly created environments), while I must manually add myself each time. What configurations or governance settings could cause this discrepancy, and how can I ensure my account is granted the same automatic co-owner and System Administrator roles without manual intervention?
Why am I not auto-added as Power Platform Admin Co-Owner and SysAdmin like my colleague by default?
The environments are created by a GitHub Actions workflow running under a dedicated service account, so this cannot be the root cause. Moreover, the DPL policy framework in Power Platform does not include any provision for defining a default individual assignee. Do you know other possible solutions?
Based on my experience , if your colleague is the one who creates the environment , the roles will be automatically assigned to him since he is the environment creator.
Creator of the environment will be default 'System Admin'
Or
DLP Policy - Is there any DLP policies which assign default owner/ co-owners which is target only for him ?
🏷️ Please tag me @MS.Ragavendar if you still have any queries related to the solution or issue persists.
✅ Please click Accept as solution if my post helped you solve your issue and help others who will face the similar issue in future.
❤️ Please consider giving it a Like, If the approach was useful in other ways.
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.
33
Share
Report
All responses (
Answers (
