Safe autonomous operation under regulated, in-region data demands:

• Every high-risk action must pass a human approval to enforce separation of duties (Microsoft Power Automate governance).

• Run the agent under its own least-privilege service principal so permissions are scoped and auditable.

• Enforce a tool/connector allow-list with environment-scoped DLP policies; this gives central, code-free governance across dev/test/prod and avoids new middleware or data stores.

These three satisfy “hands-off” automation while fulfilling least-privilege, regional residency, and centrally enforced governance.

B. Violates approval requirement and separation-of-duties policy.

E. Shared queue introduces an additional data store, breaching “no new middleware/data stores”.

F. Cross-tenant persistent memory contravenes in-region data residency and minimisation.

1. Microsoft Docs – “Use approvals in Power Automate for high-risk operations”, Governance section.

2. Microsoft Docs – “Create service principals for Power Platform applications”, Least-privilege practice paragraph.

3. Microsoft Docs – “Data loss prevention (DLP) policies”, Environment-scoped allow-list capabilities, Overview.

4. Microsoft Compliance Guide – “Regional data residency for Power Platform”, Data handling rules.