Power Apps Plans from Existing Solutions with Copilot

Introduction: why this matters

As Power Apps solutions mature, they often outlive the original maker, documentation gets stale, and change requests pile up. For IT admins and platform teams, understanding an existing solution’s intent (business problem), structure (data model), and implementation (apps/flows) can become a manual and error-prone exercise—especially during onboarding, audits, or modernization work. The new “Create a plan from your solution” capability aims to turn that reverse-engineering work into a repeatable, AI-assisted process.

What’s new: create a Plan from an existing solution

Power Apps Plans can now be generated from a solution you’ve already built. Using Copilot, Power Apps analyzes the selected solution and produces an editable plan that includes:

• Business problem and objectives (what the solution is intended to achieve)
• User roles and user stories (who uses it and how)
• Data model overview (tables and relationships at a high level)
• Technology stack summary (apps, flows, and other components)

The output is a comprehensive starting point you can refine—useful for documenting the current state and planning improvements.

How it works (and prerequisites)

From the Power Apps maker portal:

1. Go to Solutions.
2. Select the solution.
3. Choose Create plan from solution.
4. (Optional) Provide extra context in the prompt box—e.g., intended enhancements, business context, or known pain points.

Important prerequisites/behavior to note:

• The solution must include at least one app and one table.
• Copilot generates the plan and saves it:
  • In the same solution if it’s unmanaged
  • In a new unmanaged solution if the original is managed

After the plan is created, you can edit and expand it, add requirements, and potentially generate additional apps, tables, and flows within the same planning experience.

Impact for IT administrators and teams

This feature is especially relevant for:

• Operational continuity: Faster ramp-up when new makers/admins inherit a solution.
• Audit and governance readiness: A structured blueprint can reduce time spent gathering “what does this do?” evidence.
• Lifecycle and change management: Clearer visibility into dependencies across apps, flows, and data when scoping enhancements.
• Risk reduction: Less reliance on tribal knowledge and fewer mistakes from manual analysis.

Action items / next steps

• Pilot on a real-world solution: Choose a medium-complexity solution and generate a plan to validate accuracy and usefulness.
• Standardize documentation workflows: Consider using generated plans as a baseline artifact during handoffs, reviews, or before major updates.
• Check managed vs. unmanaged strategy: Since managed solutions generate plans into a new unmanaged solution, align this with your ALM process.
• Start here: Open https://make.powerapps.com, navigate to your solution, and run Create plan from solution. Review Microsoft Learn guidance for deeper implementation details.