Skip to content

Conversation

Copy link

Copilot AI commented Dec 17, 2025

  • Understand the enhancement request
  • Analyze the repository structure and current admin_App entity
  • Provide feasibility assessment
  • Propose implementation approach (if feasible)
  • Deliver step-by-step implementation plan
  • Note issue consolidation status
Original prompt

This section details on the original issue you should resolve

<issue_title>[CoE Starter Kit - SUGGESTION] - New field in Admin View [Tab Goverance] - Environment Owner (v creator) for decision making.</issue_title>
<issue_description>### Does this question already exist in our backlog?

  • I have checked and confirm this is a new question.

What is your question?

Hello @Jenefer-Monroe , good morning!

image

I would like to make a suggestion for PowerApps Apps—a new field called initially 'Business Owner.'

This field would serve to identify who is the owner and responsible for approving or denying access permissions to the app.

In a tenant where there are dozens of shared environments, the environment owner is not necessarily the app owner. There are scenarios where the service account is the owner in all production environments, but each app in that environment has a specific owner.

To enhance identification using governance, it would be very beneficial to have this field where we could indicate who is responsible.

This field could be the type where you search for the user (not the maker, because often it will be a regular user, coordinator, or manager who is not part of the development), and we could select one, two, or more. We may have an app with multiple responsible individuals managing it.

I hope this is a good suggestion; here, this information is greatly missed as we have a standard environment where the service account is the owner of the environment, but we don't know who is responsible for each app, forcing us to keep track of this information in a spreadsheet.

Obrigado sempre pela atenção

What solution are you experiencing the issue with?

Governance

What solution version are you using?

4.16

What app or flow are you having the issue with?

No response

What method are you using to get inventory and telemetry?

Cloud flows

AB#1760</issue_description>

<agent_instructions>Analyze the enhancement request described in the ticket. Provide a comprehensive evaluation that includes:
1.Understanding & Summary
⦁ Summarize the enhancement request in clear, concise terms.
⦁ Identify the core problem the enhancement aims to solve.
2.Feasibility Assessment
⦁ Determine whether the requested enhancement is technically feasible.
⦁ If not feasible, explain the blockers or limitations.
3.Proposed Implementation Approach (only if feasible)
⦁ Outline the required code, architectural, or configuration changes.
⦁ Identify all affected files, components, or modules.
⦁ Describe potential risks, dependencies, or compatibility considerations.
4.Step‑by‑Step Implementation Plan
⦁ Provide a detailed, sequential explanation of what changes should be made.
⦁ Include reasoning behind each step to ensure clarity for reviewers and maintainers.
Deliver the analysis in a structured format using headings, bullet points, and code blocks when necessary.
</agent_instructions>

Comments on the Issue (you are @copilot in this section)

@mohamrizwa This issue is being closed as its scope is now included in a newly created consolidated enhancement request for centralized management of orphaned components (Apps, Flows, Connection References) in the CoE Starter Kit. New Issue Reference: https://github.com//issues/10331 Thank you for your contributions

Custom agent used: CoE Custom Agent
Specialized agent for triaging and fixing issues in the CoE Starter Kit. Always consult the official CoE docs and the team’s SharePoint notes first, then mine prior GitHub issues and the CoE Common Responses playbook.


💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[CoE Starter Kit - SUGGESTION] - New field in Admin View [Tab Goverance] - Environment Owner (v creator) for decision making.

2 participants