All resources
Template or tool

Power Platform App Request and Governance Checklist

Word intake form and governance checklist for Power Apps, Power Automate, Copilot Studio and Power Pages requests: tiering, environments, data policies, security, licensing and support.

Free

Free Word template. Word intake form and governance checklist for Power Apps, Power Automate, Copilot Studio and Power Pages requests: tiering, environments, data policies, security, licensing and support. Download it, add your project details and use it today: no sign-up for software, no paywall.

Low-code adoption grows fastest when makers know the rules and the rules fit the risk. This template gives your Power Platform Center of Excellence a single intake and review form. Requesters describe the problem, users, data and connectors. Reviewers then classify the solution into one of four tiers and work through practical checklists for environments and ALM, data policies and connectors, security and compliance, licensing and capacity, and support and lifecycle. A decision section records conditions and approvals, and a reviewer quick reference shows when to approve fast, slow down or redirect. Built for CoE leads, platform admins, solution architects and business makers.

What's inside

  • Power Platform App Request and Governance Checklist
  • Part A: Request (completed by the requester)
  • A1. Requester and ownership
  • A2. Business problem and outcome
  • A3. What will be built
  • A4. Users and reach
  • A5. Data and connectors
  • A6. Criticality
  • Part B: Classification (completed with the platform team)
  • Part C: Environment and application lifecycle
  • Part D: Data policies and connectors
  • Part E: Security and compliance
  • Guidance notes and placeholders so you can fill it in quickly

How to use it

  1. Publish Part A as the intake form for anyone who wants to build or share a Power Platform solution beyond personal use.
  2. Hold a short review with the requester and use Part B to assign a tier. Apply only the governance that tier needs.
  3. For tier 3 and 4 solutions, complete every checklist in Parts C to G. For tier 1 and 2, complete the items your CoE marks as mandatory.
  4. Check connectors against the data policies that apply to the target environment before build starts, not at deployment.
  5. Confirm licensing with your license owner using the current Microsoft licensing guide; do not rely on assumptions from earlier projects.
  6. Record the decision, conditions and review date in Part H, and link the request ID to the solution's record in your CoE inventory.
  7. Re-run the checklist when the solution changes tier, adds a connector, or opens access to external users.

Who it's for

Solution architects, integration leads and consultants connecting Dynamics 365 with POS, EDI, WMS, CRM and the Power Platform.

Let's connect

I'm Pranshu Shubham, a Microsoft Dynamics 365 F&O Solution Architect and PMP-certified program lead with 8+ years of ERP and AI transformation across the USA, Europe and APAC. I created this resource from real project experience, and I'd love to hear how you use it.