Skip to main content
← BACK TO WRITING

Power Apps Code Apps Went GA. Here's What Changed.

2025.11.08·6 MIN READ·POWER APPS · REACT · TYPESCRIPT · LOW-CODE · MICROSOFT · ENTERPRISE
↓ Jump to section

When the preview shipped in late 2025, Power Apps Code Apps were a quiet but interesting bet: let professional web developers build React + TypeScript SPAs that plug straight into the Power Platform's authentication, connector catalogue, and governance stack. Keep the modern-web developer experience. Inherit Microsoft Entra ID, DLP, Conditional Access, and 1,500+ connectors for free.

Code Apps went generally available on 2026-02-05. Six months of preview surfaced enough to make the shape of the product clear, and a few things have meaningfully changed since the early write-ups.

What it actually is

You build a single-page app. React, Vue, Blazor WebAssembly. Microsoft's GA messaging now covers all three; anything that ships a static SPA bundle works. You wire in a small client library that lets your code authenticate against the user's Power Platform session and call Dataverse tables, SharePoint lists, SQL Server, Office 365, or any of the other connectors the platform has already governed.

What you don't build is infrastructure. You don't stand up an auth server. You don't write a backend to proxy your API keys. You don't fight your IT department for DLP sign-off on a new app. The app runs inside the platform's identity perimeter, and the platform's existing policies apply automatically.

That trade is the whole product. You give up: full hosting control (it's hosted by the platform), a custom auth flow, the ability to ship outside the Power Apps surface. You get: the existing enterprise-approved path for line-of-business tools, with a real frontend stack instead of Canvas expressions.

What changed at GA

Governance graduated. The managed-platform features that were promises in preview (tenant isolation, App Quarantine, health metrics in the admin centre, Azure B2B) are now actually enforced. Admin toggles that said "preview" have been flipped. For an enterprise actually considering deploying this, that's the gate that matters.

The CLI is mid-migration. This is the tripwire if you're reading older tutorials. The preview's CLI was pac code, part of the broader Power Platform CLI. The new path is an npm-based CLI that ships inside the @microsoft/power-apps client library starting at v1.0.4:

# old (still works; scheduled for deprecation)
pac code init --displayName "My App"
pac code push

# new (the forward path)
npx power-apps init
npx power-apps push

pac code commands are labelled "deprecated in a future release." The timing isn't announced, but every tutorial written against the new npm CLI is a better bet than a tutorial written against pac code. Commands available on the npm side: init, run, push, find-dataverse-api.

Licensing is unchanged but real. End users who run a Code App need a Power Apps Premium license. This was true in preview and is true at GA. It's worth surfacing up front because it's invisible until you try to share the app with a user who doesn't have one.

Docs moved. If you bookmarked learn.microsoft.com/en-us/power-apps/maker/code-apps/ from a preview-era post, the current path is .../power-apps/developer/code-apps/. The old URLs redirect but the docs live under /developer/ now, which also reflects the target audience.

What you still can't do

Mobile. Six months after GA, the Power Apps mobile app still doesn't run Code Apps. The team's most recent public guidance ("mobile support is unlikely to arrive before July 2026") is roughly "summer 2026 for online mobile, no commitment on offline." If your app needs to run on a phone inside the Power Apps native shell, Code Apps is not your answer yet.

Offline. Canvas has offline support; Code Apps don't. The team is still soliciting feedback on whether day-one offline is required. Treat offline as out of scope for any Code App you ship in 2026.

A handful of capability gaps. Power Platform Git integration doesn't cover Code Apps. SharePoint forms don't. $expand on Dataverse calls doesn't. Late-bound retrieveDataAsync with a dynamic table name doesn't. SharePoint lists with special characters in names don't. None of these are showstoppers for most line-of-business apps, but each one ends at least one productive afternoon if you discover it mid-implementation.

SAS IP restriction and the full PowerBIIntegration object are also still absent. If your app needs to embed PowerBI in the way Canvas does, you're writing the embed yourself.

The pro-dev niche just got crowded

The more interesting development since GA is the space around Code Apps. Microsoft has shipped two adjacent features that overlap the same "bring your own IDE and agent" pitch:

  • Generative pages for Model-Driven Apps went GA on 2026-04-02. Makers drive model-driven pages directly from GitHub Copilot, Claude Code, or other coding agents hooked into Dataverse. That's Microsoft's "let AI author the UI inside the platform" story.
  • The Canvas Apps MCP Authoring Plugin (March to April 2026) lets coding agents edit Canvas YAML. Same bring-your-own-IDE pitch, but for the Canvas stack.

Neither replaces Code Apps. But together they make the pro-dev positioning less unique than it was at preview. Where Code Apps used to be "the only sanctioned path for a real frontend stack inside the Power Platform," they're now one of three, and the choice between them is more nuanced:

  • Code Apps when you want full control of the UI layer and your engineering culture is modern web.
  • Generative pages when the UI needs to live inside the model-driven experience and you want AI as a co-author.
  • Canvas + MCP plugin when Canvas was already the right fit and you want agent-assisted editing.

For what it's worth, the 2026 Release Wave 1 plan positions Code Apps firmly as a pro-dev complement to Canvas, not a replacement. There's one release-plan investment (a connector-discovery CLI, preview May 2026 / GA July 2026) and that's it. Microsoft isn't betting Code Apps will be the default; they're betting it'll be the right tool for a specific segment.

Who should pick it up now

If you're a React or Vue developer whose company already uses Power Platform, or who's been told they have to, Code Apps is the least painful way to build a real frontend inside the governance perimeter. The DX is close enough to regular SPA development that you don't feel like you're writing to a platform, except when you hit the capability gaps listed above. The GA milestone means the governance story is complete and the preview caveats are gone.

If you're a Canvas developer whose app has outgrown Power Fx, Code Apps let you rewrite the UI without leaving the platform. You'll re-use the same connectors, the same auth, the same sharing model. You'll just express the UI in React instead of formulas.

If you don't already have a reason to be inside the Power Platform, Code Apps won't give you one. The value is the governance and connector story, and if you don't need those, a regular SPA + your own backend is still the right answer.

The migration tripwire to watch for is the CLI. Anything you read that opens with pac code was written in preview; anything that opens with npx power-apps is current. That's the fastest way to date the tutorial you're following.

Microsoft Learn: Power Apps Code Apps overview. GA announcement, 2026-02-05.