Power Apps Generative Pages GA for Model-Driven Apps

Introduction: why this matters

Model-driven apps are a backbone for many line-of-business solutions built on Dataverse, but creating highly tailored UI/UX traditionally requires time-consuming custom development or complex component design. With Generative Pages now generally available (GA) in the U.S., Power Apps introduces a faster path to building rich, responsive, custom pages—generated from prompts, integrated with your data, and managed like any other solution asset.

What’s new with Generative Pages (GA)

AI-generated React pages for model-driven apps

Generative Pages lets makers describe what they need in natural language, and an agent generates a fully functional React page that fits into an existing model-driven app.

Deep data integration

• Native Dataverse connectivity so the generated UI can work directly with your tables and relationships.
• Virtual entities support, enabling scenarios that surface external data (for example, SharePoint or Dynamics 365 Finance and Operations) without adding undue complexity.

UI consistency and modern controls

• Uses Fluent UI controls and aligns by default to the modern theme used in your app, helping reduce “custom page looks different” friction.

Transparency and control for makers and devs

• After each iteration, you can review what code changed, improving trust and auditability.
• You can take over and edit the code manually when requirements exceed what prompting can express.

ALM-ready

• Pages are solution-aware, making it easier to move them across environments and include them in your standard application lifecycle management processes.

Production support and model quality

• GA includes production support in U.S. environments.
• Powered by GPT-5, positioned for improved code generation quality and performance.

Impact on IT admins and end users

For IT teams, Generative Pages can accelerate delivery—but it also introduces new governance considerations:

• Faster iteration means more frequent changes; ensure your change management and testing practices can keep up.
• ALM alignment improves because pages are solution assets, but admins should verify pipelines, environment strategies, and source control practices for these generated components.
• Data access and compliance still depend on Dataverse security roles, DLP policies, and connector governance—especially when leveraging virtual entities for external systems.

End users benefit from quicker delivery of task-focused experiences and more polished, responsive pages that match the app’s look and feel.

Action items / next steps

1. Confirm availability: GA is currently stated for U.S. environments—review your tenant/environment region strategy if you operate globally.
2. Update governance: Reassess Power Platform policies (DLP, environment access, maker permissions) to account for AI-generated UI artifacts.
3. Standardize ALM: Add Generative Pages to your solution packaging, deployment pipelines, and test plans.
4. Enable safe adoption: Start with a pilot app, define prompting and review guidelines (including code review expectations), and train makers on security and data boundaries.
5. Provision a dev sandbox: Use a Developer Plan or non-production environment to evaluate performance, UX, and maintainability before scaling.