[WIP] Make 'Automatically delete environment after use' option mandatory

[Copilot]

Thanks for assigning this issue to me. I'm starting to work on it and will keep this PR's description up to date as I form a plan and make progress.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[CoE Starter Kit - Feature]: Making the 'Automatically Delete Environment After Use' Option Mandatory in the Admin - Env Request App?</issue_title>
<issue_description>### Is your feature request related to a problem? Please describe.

No response

Describe the solution you'd like

Hello,

When a user wants to create a lab environment, they go through the "maker - environment request" application and often they do not select the "automatically delete environment after use" option. It turns out that most of the time, they conduct tests for a few days, and then the environment remains unused. I end up with environments that are no longer needed, and I have to delete them manually.

Is it possible to make this field mandatory, for example, by using the 'Admin- Environment Request' app to have an option that makes this field mandatory?

If someone needs more days, they could receive an email inviting them to extend the validity of the environment.

Also, is it possible to have an alert when an environment is considered inactive? I don't seem to have seen this option in the COE tools.

Thank you very much.

Describe alternatives you've considered

No response

Additional context?

No response

AB#1736</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.

• Fixes [CoE Starter Kit - Feature]: Making the 'Automatically Delete Environment After Use' Option Mandatory in the Admin - Env Request App? #7259

---

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