1. Introduction
Microsoft Power Apps has always sat at the intersection of accessibility and capability — a platform that promised enterprise-grade results without enterprise-grade coding requirements. But 2025 and early 2026 brought a seismic shift. Two distinct, code-centric development paradigms landed in rapid succession: Generative Pages and Code Apps.
Both break from the traditional drag-and-drop, PowerFx-formula world of Canvas Apps. Both generate or host real React code. Yet they serve fundamentally different audiences, different architectural purposes, and carry different limitations.
If you are an architect, a Power Platform maker, or an enterprise developer trying to figure out which tool belongs in your next project, this article is your definitive guide. We will cover what each feature is, how it works under the hood, its real-world limitations, licensing implications, and a practical decision framework for when to choose one over the other.
Everything makers, architects, and developers need to know — including when to use which, limitations, licensing, and ALM.
2. PowerApps Generative Pages
2.1 What Are Generative Pages?
Generative Pages is an AI-driven experience built into the Model-Driven App designer in Power Apps. Announced at Microsoft Build 2025 and made generally available in the United States in November 2025, it allows makers of any skill level to describe a page in natural language and receive a fully functional, React-and-TypeScript-based page in return — no manual coding required.
Think of it as a reimagined Custom Page, but instead of dropping components onto a canvas and wiring them with PowerFx, you type something like:
"Build a page showing Account records as a gallery of cards using a modern look and feel. Include name, entity image on the top, and website, email, and phone number. Make the gallery scrollable using data from the Account table."
The AI agent — powered by GPT-5 — processes that prompt, evaluates the schema of the Dataverse tables you have linked, and generates a complete React/TypeScript component, including frontend layout, data binding, and basic business logic. The result sits natively inside your Model-Driven App, adheres to your app's existing Fluent UI theme, and is fully solution-aware for ALM movement across environments.
2.2 How It Works — Technical Architecture
Under the hood, Generative Pages generates standard React and TypeScript code. There is no proprietary abstraction layer, no PowerFx, and no visual designer canvas. The generated code is transparent — after every iteration of the conversational agent, you can inspect exactly which lines changed. You can also download the generated .tsx file, refine it in VS Code, and re-upload via the Power Platform CLI.
The Conversational Workflow
-
Open a Model-Driven App in the App Designer at
make.powerapps.com - Select Add a page → Describe a page
- Enter a natural language prompt (US English only)
- Link up to six Dataverse tables via Add data → Add table
- Upload an optional wireframe sketch or mockup image to guide the visual output
- Review the live preview alongside the full source code
- Refine iteratively: "Switch to dark mode," "Add a filter bar by region," "Make this mobile-responsive"
- Publish the page into the app when satisfied
The pages connect to Dataverse natively and support full CRUD operations against any linked table. They also support virtual entities, meaning you can point a Generative Page at external data sources like SharePoint lists or Dynamics 365 Finance and Operations tables without complicating your data model.
2.3 Key Features
Natural language generation with GPT-5 — Since August 2025, Generative Pages uses GPT-5, delivering significantly improved code quality, faster generation times, fewer rendering errors, and a model selector to switch between GPT-4.1 and GPT-5.
Full code transparency — Every Generative Page exposes its source code. You can read it, review it, and edit it externally via the Power Platform CLI.
Image-guided generation — Attach a napkin sketch, a Figma mockup, or a wireframe. The agent uses the visual reference to guide layout decisions, dramatically reducing refinement iterations.
Solution-aware and ALM-friendly — Pages are packaged as solution components, exportable and deployable across dev/test/prod environments.
Fluent UI alignment — Generated pages automatically inherit the Fluent UI theme configured for your Model-Driven App.
Virtual entity support — Connect to external data through Dataverse virtual entities — SharePoint, D365 Finance and Operations, and more.
Context-aware input (May 2026) — Pages now accept context as input, so a page can open pre-loaded with the record a user was working on — enabling launch from command bars, grid row actions, and sub-grid navigation.
Mobile support (May 2026) — Generative Pages now render correctly in the Power Apps mobile app (offline mode not yet supported).
2.4 Limitations of Generative Pages
⚠️ Important: These are real-world production constraints that must be accounted for during architecture and delivery planning.
Dataverse-only data connectivity — Pages can connect only to Dataverse tables. External data must be surfaced through virtual entities. Direct SQL, REST APIs, or SharePoint in raw form are not supported.
Geographic availability — The browser-based maker experience is available only in environments in the United States, Great Britain, Australia, and Singapore. The CLI-based approach is global but requires developer tooling.
US English only for prompting — The prompting interface supports only US English. Localization of the generated page UI is possible via resource files, but authoring itself is English-only.
No collaboration — Only one maker can work on a Generative Page at a time. Concurrent editing causes conflicts — teams must coordinate manually.
Third-party npm packages not supported — All dependencies must be bundled into a single
.tsxfile. You cannot import external npm packages at runtime.No guaranteed production readiness — Microsoft explicitly states the generated code is not guaranteed to be production-ready or compliant with your organization's standards. You must review and validate before publishing.
Model-Driven Apps only — Generative Pages cannot be used in Canvas Apps. If your scenario does not involve an MDA backed by Dataverse, this feature is out of scope.
Side pane / form tab embedding not yet supported — As of May 2026, Generative Pages cannot be opened in side panes or embedded as tabs/sections within form designers.
No offline support — Mobile rendering works, but offline capability is not yet available.
3. PowerApps Code Apps
3.1 What Are Code Apps?
Code Apps — officially Power Apps code apps — allow professional developers to build full web applications using any modern JavaScript framework (React, Vue, Angular, or vanilla JS), develop locally in their preferred IDE, and then deploy those applications to Power Platform's managed hosting infrastructure with a single CLI command.
In short: Code Apps bring Power Platform's enterprise governance layer to apps that have zero Power Apps markup, zero PowerFx, and zero model-driven structure. Your app is a standard web app. Power Platform simply hosts it, secures it, and connects it to the ecosystem.
Announced at Microsoft Ignite 2024 and made generally available in February 2026, they represent Microsoft's answer to the pro-developer community that has long wanted to use Power Platform connectors and governance without adopting low-code abstractions.
💬 "Build apps your way — drag and drop, generative AI, or custom code." — Microsoft Power Platform CVP
3.2 How It Works — Technical Architecture
Code Apps separate the development experience completely from the Power Apps maker portal. Developers work in their local IDE, initialise a project using the official starter templates from the GitHub repository (microsoft/PowerAppsCodeApps), and use the @microsoft/power-apps npm client library to connect their frontend code to Power Platform connectors.
Getting Started
The recommended starter template (pre-configured with React, Vite, Tailwind CSS, TanStack Query, and React Router) scaffolds a production-ready project in minutes:
npx degit microsoft/PowerAppsCodeApps/templates/starter my-app
cd my-app
npm install
npm run dev
During development, you iterate locally in your browser, writing real React components with full access to your preferred toolchain — TypeScript, ESLint, Prettier, unit testing frameworks, Storybook, or anything else in your normal workflow.
When ready to deploy, a single command pushes the built app to Power Platform:
pac code push
Power Platform's managed host takes care of the rest: Microsoft Entra authentication, DLP policy enforcement, Conditional Access, sharing limits, and health monitoring — all without any code changes by the developer.
3.3 Key Features
Full framework freedom — React, Vue, Angular, Svelte, or plain HTML/CSS/JS — Code Apps place no restrictions on frontend frameworks.
Local development with your full toolchain — VS Code, GitHub Copilot, ESLint, unit tests, component libraries — everything works normally. Power Platform is the deployment target, not the development environment.
Access to 1,400+ connectors from JavaScript — The
@microsoft/power-appsclient library exposes connectors as simple JavaScript calls — Salesforce, SAP, SharePoint, SQL Server, custom APIs.Zero-config enterprise security — Microsoft Entra authentication is automatic. DLP policy enforcement, Conditional Access, tenant isolation, and admin consent suppression work without any developer code changes.
ALM and deployment tooling — Code Apps are versioned and deployable through Power Platform ALM pipelines. Admin center health monitoring and diagnostics are available out of the box.
AI-accelerated development — Because Code Apps are standard web code, developers can use GitHub Copilot, Claude Code, Cursor, or any other AI coding assistant natively.
Community templates and samples — The official GitHub repository contains starter templates, sample applications, and end-to-end examples. The community actively contributes.
External user (B2B) support — Code Apps support Azure B2B collaboration, allowing external users in partner tenants to access the app.
3.4 Limitations of Code Apps
⚠️ Important: These are significant architectural constraints. Validate each one against your project requirements before committing to Code Apps.
No Power Apps mobile app support — Not supported in the Power Apps mobile app or Power Apps for Windows. Users must access via web browser — a hard constraint for mobile-first field scenarios.
Admin opt-in required — Must be explicitly enabled by a Power Platform admin in the admin center per environment.
Power Apps Premium license for all end-users — Every user who runs a Code App requires Power Apps Premium ($20/user/month). There is no lighter licensing tier.
No SharePoint forms integration — Code Apps cannot replace SharePoint list forms — a common Canvas App use case.
No Power BI data integration — The
PowerBIIntegrationfunction is not supported (though Code Apps can be embedded in Power BI reports via the Power Apps Visual).No Git integration with Power Platform — Code Apps do not support Power Platform's native Git integration. Teams must manage source control externally (GitHub, Azure DevOps).
No SAS IP restriction support — Storage Shared Access Signature IP restriction is not yet supported.
Code-first only — no visual designer — There is no drag-and-drop editor or property panels at
make.powerapps.com. Requires developers who can write React or Vue.CLI tooling dependency — Development requires Node.js, npm, the Power Platform CLI, and a code editor. The barrier to entry for non-developers is high.
4. Head-to-Head Comparison
The table below summarises the critical differences across 20 dimensions to support architecture decisions.
| Dimension | Generative Pages | Code Apps |
|---|---|---|
| Primary Persona | Makers, citizen developers, functional consultants | Professional web developers, pro-dev teams |
| Development Environment | Browser (make.powerapps.com) or PAC CLI | Local IDE (VS Code, WebStorm, etc.) |
| App Type | Pages inside Model-Driven Apps only | Standalone web apps (browser) |
| Frameworks | React / TypeScript (AI-generated) | React, Vue, Angular, Svelte, plain JS |
| Data Sources | Dataverse only (+ virtual entities) | All 1,400+ Power Platform connectors |
| No-Code Entry Point | ✅ Yes — natural language prompts | ❌ No — requires coding knowledge |
| Code Transparency | Full (viewable & downloadable) | Full (your code, your repo) |
| Manual Code Editing | Yes, via CLI after download | Yes, natively in your IDE |
| Mobile App Support | ✅ Yes (as of May 2026) | ❌ No |
| Offline Support | ❌ No | ❌ No |
| PowerFx | Not used | Not used |
| Solution-Aware ALM | ✅ Yes (native) | ⚠️ Partial (no Power Platform Git integration) |
| 3rd-Party npm Packages | ❌ No (single-file constraint) | ✅ Yes (full npm ecosystem) |
| Licensing (End Users) | Power Apps Premium required | Power Apps Premium required |
| AI Code Generation | ✅ Yes — GPT-5 generates the code | ❌ No — you write code, assisted by ext. AI tools |
| Collaboration (Multi-Maker) | ❌ No | ✅ Yes (standard Git workflows) |
| Regional Availability | US, UK, AU, SG (browser); Global (CLI) | Global |
| Admin Enablement Required | ❌ No | ✅ Yes (per-environment toggle) |
| SharePoint Forms | Not supported | Not supported |
| External (B2B) Users | Inherits MDA restrictions | ✅ Yes, via Azure B2B |
5. When to Use What — Decision Framework
5.1 Choose Generative Pages When...
You are extending an existing Model-Driven App or Dynamics 365 deployment — Generative Pages slot directly into the MDA sitemap and inherit your app's theme, security model, and solution structure. Ideal for D365 Sales, Customer Service, or Field Service customisations.
You need to move fast on a prototype or MVP — The conversational generation workflow compresses hours of React scaffolding into minutes. For proof-of-concepts, hackathons, or fast stakeholder iterations, Generative Pages is unmatched.
Your data lives exclusively in Dataverse — If your scenario only needs Dataverse tables — including virtual entities pointing to SharePoint or D365 F&O — Generative Pages covers the data layer fully.
Your maker is not a developer — Business analysts, functional consultants, and citizen developers can operate Generative Pages effectively with zero coding knowledge.
You want UI that breaks free from standard MDA forms — Card galleries, kanban boards, interactive dashboards, and timeline visualisations that are impossible in the native form designer.
You have a design reference — Uploading a wireframe or mockup alongside a prompt produces dramatically better first-generation results.
5.2 Choose Code Apps When...
You need to connect to non-Dataverse data sources directly — SQL Server, Salesforce, SAP, or any REST service — Code Apps give access to all 1,400+ connectors.
You are building a standalone web application — Code Apps are their own deployable artifact at a standalone URL. No requirement for a Model-Driven App host.
You have professional web developers on your team — They stay in their native toolchain — VS Code, npm, GitHub — without learning PowerFx or Canvas app mechanics.
You need npm-ecosystem components — Recharts, TanStack Table, rich text editors, drag-and-drop libraries, PDF viewers — any npm package is available.
You have strict code quality standards — Enforce lint checks, write unit tests, use peer code review workflows. Full control from the first line.
You need to support external (B2B) users — Azure B2B collaboration allows partner tenant access.
You are modernising a legacy application — For full application rewrites — not just a page within an MDA — Code Apps offer the complete flexibility needed.
5.3 The Hybrid Pattern: Use Both
These two features are complementary, not mutually exclusive. A common architecture for complex Model-Driven App deployments combines both:
- Use Generative Pages for rich, Dataverse-focused pages embedded in the MDA sitemap — dashboards, record galleries, custom forms that need a modern look.
- Use Code Apps as standalone companion apps that pull data from multiple external sources, linked to from within the MDA using deep links.
This hybrid pattern lets you put the right tool at the right boundary. The MDA retains its security model and sitemap structure; Generative Pages enhance the internal experience; Code Apps handle cross-system integrations and external-facing portals.
6. Licensing Summary
Both Generative Pages and Code Apps require Power Apps Premium licensing for end users in production — at $20/user/month (or $12/user/month at 2,000+ seat volumes). Makers do not require additional AI credits to author Generative Pages; the AI generation experience is included.
6.1 Key Licensing Traps to Avoid
Generative Pages trap — Since they live inside Model-Driven Apps backed by Dataverse, every user needs a Power Apps Premium or equivalent Dynamics 365 license. There is no 'light' licensing for Dataverse access.
Code Apps trap — Every end-user needs Power Apps Premium, even if the app only calls standard connectors. Unlike Canvas Apps, where some Microsoft 365 licenses cover standard connector access, Code Apps always require Premium.
Per-app licensing clarification — The Power Apps per-app license has ended for new EA/MPSA customers as of February 2026. It remains available for CSP customers. Organizations planning deployments at scale should evaluate the per-user Premium plan as the standard licensing model.
7. ALM and Governance
7.1 Generative Pages ALM
Generative Pages are packaged as solution components. You can export them in managed or unmanaged solutions, deploy through standard Power Platform deployment pipelines, and use environment variables to parameterise behaviour across dev/test/prod.
The browser-based authoring experience lacks native Git integration. Teams that want source-controlled page code should download the .tsx file, commit it to a repo, and use the PAC CLI for CI/CD deployment.
7.2 Code Apps ALM
Code Apps are built and versioned in external source control (GitHub, Azure DevOps). Deployment to Power Platform uses the PAC CLI. There is no Power Platform Git integration for Code Apps, and make.powerapps.com offers no authoring surface.
From an IT governance perspective, the platform still provides app quarantine, DLP enforcement, health monitoring, and Conditional Access — the governance layer is intact, but the development lifecycle is managed externally.
8. Conclusion
Generative Pages and Code Apps represent two different bets Microsoft is making on the future of enterprise application development. Generative Pages lowers the ceiling for complexity and raises the floor for visual quality — any maker with a clear description and a Dataverse table can now build a React-powered page in minutes. Code Apps remove the ceiling entirely, inviting professional developers into the Power Platform ecosystem without asking them to surrender their toolchain or trade React for PowerFx.
The right choice depends on three questions:
| Question | Answer → Tool |
|---|---|
| Who is building? | Makers / consultants → Generative Pages. Pro developers → Code Apps. |
| Where does the app live? | Inside a Model-Driven App → Generative Pages. Standalone / multi-system → Code Apps. |
| Where is the data? | Dataverse-only → Generative Pages. Cross-system connectors → Code Apps. |
For organisations running Dynamics 365 or established Model-Driven App solutions, Generative Pages will accelerate delivery of bespoke experiences that previously required custom PCF components or full-stack development. For organisations building net-new applications — or modernising legacy tools — Code Apps bring Power Platform's enterprise security and connectivity to teams that speak React, Vue, and TypeScript as their first language.
The era of 'one size fits all' in Power Apps is over. In its place, Microsoft has built a platform where the low-code maker, the AI-assisted citizen developer, and the professional web developer can each work in a paradigm that respects their skills. The architect's job is to match the right paradigm to the right problem.
Updated: May 2026 | Based on official Microsoft documentation and Power Platform Blog announcements and Microsoft Learn references through May 2026
Always verify current availability at learn.microsoft.com/en-us/power-apps
📌 Note: Feature parity, regional availability, and licensing details are subject to change
Top comments (0)