- Scoped app-user connection reference (B): This enforces least privilege by ensuring actions run under a specific, controlled identity (like a service principal) rather than a developer's or a shared account. Connection references allow this to be managed across dev/test/prod.

- Managed solution promotion gates (D): This is a fundamental Application Lifecycle Management (ALM) practice. Using managed solutions with approval gates for promotion ensures changes are reviewed, tested, and deployed in a controlled, auditable manner, supporting separation of duties.

- Schema validation and parameter allowlist (E): This is a critical security control to prevent prompt injection and abuse. By strictly validating the structure and content of parameters passed to an action, you limit the AI's ability to be manipulated into performing unintended operations.

A. Per-maker shared connection across environments: This violates least privilege and separation of duties, as a maker's broad permissions could be exploited. It is an ALM anti-pattern.

C. Hardcode secrets in action parameters: This is a severe security vulnerability. Secrets must be stored securely (e.g., Azure Key Vault) and accessed via secure mechanisms like environment variables.

F. Unrestricted HTTP actions for maximum integration coverage: This creates a massive security risk by allowing the AI to potentially call any endpoint. Actions must be narrowly scoped to specific, required operations.

1. Microsoft Power Platform ALM Guide, "Use connection references in solutions," Microsoft Learn. This document explains how connection references abstract connection details, enabling different principals (e.g., service principals for app users) per environment.

2. Microsoft Power Platform ALM Guide, "Solution concepts," Microsoft Learn, Section: "Managed solutions." This guide details how managed solutions are used for deploying to test and production environments, forming the basis for promotion gates.

3. Microsoft AI, "Building responsible AI solutions with Copilot Studio," Microsoft Learn, Section: "Security." This documentation emphasizes the need to "validate and sanitize inputs" for actions to prevent misuse, which directly corresponds to schema validation and allow-listing.