The core control gap is the lack of a formal, traceable approval before deploying to the production environment. Adding a production approval gate within the release pipeline directly solves this. This gate can be configured to require a specific user or group (the release manager) to approve the deployment, creating an auditable record that meets the five-year traceability requirement. This change is made within the pipeline configuration, not the app code, and ensures changes are formally signed off on before impacting the live environment, aligning with best practices for release management.

A. Scoping the approval gate to dev is incorrect; approvals are most critical before a production release, not a development deployment.

B. Enabling auto-promotion is the opposite of the requirement. It removes human oversight, whereas the business needs a mandatory, auditable approval step.

D. Enabling tenant audit logs is a reactive measure. While useful for auditing, it does not prevent an unapproved deployment; the approval gate is the required preventative control.

1. Microsoft Azure DevOps Documentation. (2023). Release approvals and gates overview. "Use approvals and gates to control your deployment pipeline... You can manually approve or reject a deployment to a stage." Section: "Approvals".

2. Microsoft Learn. (2023). Set up pipelines. In Power Platform ALM documentation. "To control which releases are deployed to which stage and when, you can configure approvals... This creates an audit trail of who approved the deployment." Section: "Configure approvals".

3. Microsoft Power Platform Well-Architected Framework. (2023). ALM and DevOps. "Release management should include approval gates to ensure that changes are reviewed and authorized before being deployed to production." Section: "Release Management".