Power Apps vs Fabric Apps: A Rebuild-or-Stay Decision Rule

Co-authored by

Motaz Ben Saoud, Managing Director & Partner

Power Apps vs Fabric Apps: Which One Should Your Apps Run On?

Quick answer: Keep production Power Apps where they are. Rebuild an app as a Fabric App only when its data already lives in Fabric, it needs no offline or native mobile use, a TypeScript team will own it, and you can accept a preview product with no ALM. Run both when Power Apps captures the data and a Fabric App analyses it.

A typical Power Apps estate in the UAE or Saudi Arabia is a mix: canvas apps for field and approval work, model-driven apps over Dataverse, a few apps over SQL Server, Power Automate flows behind them, and a Power Apps visual inside a Power BI report or two. Since Fabric Apps went to public preview in June 2026, IT and procurement hear two questions. Developers ask whether they can write these apps in code. Finance asks whether moving them to Fabric removes the Power Apps Premium line from the renewal.

This post answers both by comparing Power Apps vs Fabric Apps app by app on data access, write-back, offline, licensing, ALM, governance and preview status, and a rule for when to stay, rebuild or run both. Every fact was checked against Microsoft's own pages on 18 October 2026.

For background, see what Microsoft Fabric Apps actually are, Fabric Apps vs a custom web app, and Power BI or a custom app if half the "app" is really a report.

What Is Each Platform Built For?

Quick answer: Power Apps is a generally available low-code platform for makers, built on Dataverse and more than 1,500 connectors, with a code-first option called code apps. Fabric Apps is a preview backend platform for TypeScript developers whose apps live inside Microsoft Fabric and read Fabric data.

Power Apps has three app types that matter here. Canvas apps are built screen by screen in a low-code studio. Model-driven apps are generated from Dataverse tables, forms and business rules. Code apps, generally available since 5 February 2026, let developers build React or Vue apps in Visual Studio Code and host them on Power Platform with "access to Power Platform data sources and 1,500+ connectors, callable directly from JavaScript", per the code apps overview (updated 23 September 2026).

So "our developers want to write code" is not, on its own, a reason to leave Power Platform. Code apps give them code while keeping DLP, sharing limits, Conditional Access and the existing licences.

Fabric Apps is described on its FAQ (updated 15 September 2026) as "a backend platform that helps TypeScript developers build and deploy data-driven applications faster." You define data models with TypeScript decorators, and Fabric generates the database schema, a GraphQL API and a typed client. The frontend can be any framework that makes HTTP requests. Microsoft lists the intended uses as internal tools and dashboards, data exploration, rapid prototypes, and AI and agent applications. There is no low-code designer: asked whether Fabric Apps works without TypeScript, the FAQ answers "No."

The two overlap less than their names suggest. Power Apps captures and processes operational data. Fabric Apps puts a developer-built application on top of data that already sits in Fabric.

Power Apps vs Fabric Apps Compared Line by Line

Quick answer: Power Apps leads on maturity, offline, mobile, connectors, ALM and governance. Fabric Apps leads on direct, delegated access to Fabric warehouses, SQL databases and semantic models, and on capacity-based rather than per-seat cost.

	Power Apps	Fabric Apps
Status	Generally available, including code apps since February 2026	Preview. The Learn overview still opens with "This feature is in preview."
Who builds	Makers in a low-code studio; developers through code apps	TypeScript developers only
Data access	Dataverse plus more than 1,500 connectors. SQL Server is a premium connector	An app-owned SQL database, plus connectors to the lakehouse SQL endpoint, warehouse, SQL database in Fabric and semantic models
Existing databases	Connect through a connector	The app database can't use an existing schema. Existing Fabric items are reached through connectors
Write-back	Dataverse and most connectors. Fabric virtual tables are read-only	App database, warehouse and SQL database in Fabric. Lakehouse and semantic model are read-only
Offline and mobile	Native mobile player. Dataverse canvas apps run offline-first	Web app only. No offline mode or native player is documented
Sign-in	Microsoft Entra, B2B guests. External sites go to Power Pages	Entra SSO only once deployed. Anonymous access is a separate preview, off by default
User licensing	Premium at $20 per user per month, or pay-as-you-go at $10 per active user per app per month	Fabric capacity units. A Pro and PPU allowance is announced but not yet documented
ALM	Solutions, pipelines and Git integration	"Application lifecycle management (ALM) isn't supported at this time"
Governance	DLP data policies, Managed Environments, environment groups, tenant isolation	Tenant switch, item permissions and source security. No private links or outbound access protection yet
Back-end logic	Power Automate, Dataverse plug-ins and business rules	Server-side TypeScript functions (preview), up to 240 seconds per run

Offline is the row that settles the most apps. Power Apps can run a Dataverse canvas app offline-first, up to a device-dependent 3 million rows, and model-driven apps have their own mobile offline mode. Fabric Apps are "standard web applications", per the data app template page, and no Fabric Apps page mentions offline use. An app used in a warehouse or on a site visit with patchy coverage stays on Power Apps.

On data access, Fabric Apps connectors use delegated authentication, so each request runs with the signed-in user's own access to the source item. ALM is the row procurement should weigh most, and the next section covers it.

How Do ALM, Governance and Preview Status Compare?

Quick answer: Power Apps has mature ALM and admin controls: solutions, pipelines, Managed Environments and DLP. Fabric Apps has no supported ALM, no private links, no outbound access protection and no published GA date, so it is not ready to carry an app your operations depend on.

Power Platform ALM and governance

Power Apps move between environments as solutions. Pipelines in Power Platform (updated 29 September 2026) deploy from development to test to production, and "all other environments used in pipelines must be enabled as managed environments," which need premium licences for active users. Dataverse Git integration links development environments to Azure DevOps or GitHub, though code apps don't support it.

On governance, data policies (updated 14 October 2026) control which connectors can be combined and suspend apps that break the rules. Managed Environments add sharing limits, IP firewall, customer-managed keys and environment groups. Tenant isolation blocks cross-tenant connections.

What Fabric Apps has today

The Fabric Apps FAQ lists its own limits:

"Application lifecycle management (ALM) isn't supported at this time."
"Multiple environments management isn't available out of the box." Separate dev, test and production means separate workspaces you deploy to by hand.
"Workspace outbound access protection isn't supported at this time."
"Tenant-level and workspace-level private links aren't supported at this time."
Every entity needs a single UUID id primary key, with no composite keys and no many-to-many relationships.
Once deployed, sign-in is Microsoft Entra SSO only. Custom identity providers aren't supported.

The troubleshooting page adds one that hurts production apps: renaming a column, changing its type or removing it is unsupported and "can break the app and its deployment to Fabric." Power Apps makers change Dataverse columns routinely. A Fabric App team has to plan schema changes as additive.

On governance, a tenant administrator has to switch the Fabric Apps workload on, and access runs through item permissions (Run and interact, Edit, Reshare) plus permissions on each connected data item. Microsoft Purview DLP covers Fabric lakehouses, warehouses, databases and semantic models, but no Fabric Apps page says Purview DLP or sensitivity labels apply to the app item itself, and none describes an equivalent of Power Platform's connector-level data policies.

Preview status

As of 18 October 2026, every Fabric Apps page on Learn still carries the preview label, and the server-side functions, connectors, PostgreSQL support and secret storage announced at FabCon Europe in September are listed as preview on What's new in Fabric. Microsoft's 28 September 2026 Azure blog post refers to "the initial launch in June 2026" without giving a GA date. Some third-party posts say Fabric Apps is generally available. No Microsoft page says so.

How Does Licensing Differ for the Same App?

Quick answer: Power Apps charges per user: Premium at $20 per user per month covers unlimited apps, or $10 per active user per app per month on pay-as-you-go. Fabric Apps consumes Fabric capacity units, and Microsoft has announced Pro and PPU access up to 1 GB per app without documenting the terms on Learn yet.

This section is short on purpose. The full Fabric cost model belongs in the Power BI Pro, PPU and Fabric licensing decision tree and Fabric capacity sizing.

Power Apps, as of 18 October 2026:

Power Apps Premium is $20 per user per month, paid yearly, or $12 with a 2,000-seat minimum, per the pricing page. It covers unlimited apps for that user.
The pay-as-you-go meter is $10 per active user per app per month, where "an active user is someone who opens an app at least once in the given month."
The per app plan is closed to new customers: "Effective January 2, 2026, the Power Apps per app SKU is no longer available for purchase by new customers," per Microsoft's licensing notice. Existing Enterprise Agreement customers can renew, and CSP customers are not affected.
Enforcement tightens next year. The Power Apps licensing FAQ (updated 8 October 2026) says that from February 2027, apps in Managed Environments, model-driven apps and apps used outside a Dynamics 365 context "require users to have an appropriate premium license."

Fabric Apps:

The pricing page says "your workspace must have Fabric capacity assigned." The SQL database, GraphQL API, user data functions and OneLake static content consume capacity units, the GraphQL API at "ten CUs per hour of request and response processing time." Hosting, authentication and deployment carry no separate charge "at this time".
Microsoft's 28 September 2026 Azure blog post says Pro and PPU customers "at no additional cost, will also have access to Fabric Apps and Fabric Database capabilities," up to 1 GB per app, through an "Apps in Power BI" preview "in the coming weeks". As of 18 October 2026 no Learn page documents those terms, the limits beyond 1 GB, or whether a viewer needs Pro.

One point matters for procurement before any rebuild. Power Apps Premium is a per-user licence covering every app that user runs. Moving one app to Fabric saves nothing for a user who still runs another premium app, such as any model-driven app. The saving only appears when a group of users stops using premium Power Apps entirely, or when the moved app was billed per active user on pay-as-you-go. Run that check against the licensing reports in the Power Platform admin center before you put a saving in the business case.

Where Do Power Apps on OneLake and Translytical Task Flows Fit?

Quick answer: They are the middle ground, and they settle many rebuild requests without a rebuild. Power Apps can read Fabric data through read-only virtual tables, and translytical task flows let Power BI report users write to Fabric SQL databases and warehouses from inside the report.

Before scoping a Fabric App, check whether the request is one of these:

"The app needs to show Fabric data." Dataverse virtual tables sourced from a Fabric lakehouse or warehouse let a Power App read it in place. Learn states (updated 9 April 2026) that these "are read-only", so the app keeps writing its own records to Dataverse.
"Users need to correct numbers they see in a report." Translytical task flows (updated 11 August 2026) let report users add, edit or delete records in Fabric SQL databases, warehouses and lakehouse files through user data functions. They reached GA in the March 2026 Power BI update. Microsoft recommends a SQL database as the target for most write-back.
"We already have a Power App inside the report." The Power Apps visual passes report context into a canvas app, but Learn says it "can't filter the data or send any data back to the report," and it passes at most 1,000 records. If that limit is the complaint, a task flow is usually the fix, not a new platform.

The Fabric Apps overview post covers these options in more depth. For this decision, both are generally available today, so a rebuild is rarely the only way to get Fabric data into an app.

The Decision Rule: Stay, Rebuild, or Run Both

Quick answer: Stay when an app needs offline, native mobile, Dataverse logic, non-Fabric connectors or production-grade ALM. Rebuild only when every question below points that way. Run both when Power Apps captures operational data and a Fabric App analyses it.

Walk each app in the portfolio through these questions in order. The first "stay" answer ends the review for that app.

Does it run offline or in the Power Apps mobile player? Stay. Fabric Apps documents neither.
Is it production-critical, regulated or under an internal SLA? Stay until Fabric Apps is generally available and has ALM. Re-check every quarter.
Does it rely on Dataverse business rules, model-driven forms, Power Automate approvals, or connectors to SharePoint, Dynamics 365, SAP or other non-Fabric systems? Stay. Fabric Apps connectors reach Fabric items only, so each of those pieces becomes custom code in a server-side function.
Is the request really write-back from a report? Use a translytical task flow, not either app platform.
Is the data already in a Fabric warehouse, SQL database or semantic model, with mostly read and light edit screens? If yes, it is a rebuild candidate.
Will a TypeScript team own it for its full life? If no, stay. Without that team, the app has no owner.
Does it run in a region where Fabric Apps is offered? Confirm before scoping. See the next section.

Stay on Power Apps when

Field, inspection or approval apps used on phones, especially offline.
Model-driven apps that are the system of record for a process.
Apps whose main value is a Power Automate flow or a connector to a non-Fabric system.
Apps built and maintained by business makers who don't write TypeScript.

Rebuild as a Fabric App when

The app is an analytics-heavy internal tool over Fabric data: a forecast override screen, a reference-data editor, a reconciliation view over a warehouse.
Its users already sit inside your Entra tenant and work on desktops.
A developer team owns it and accepts preview terms: no ALM, manual workspace promotion, additive schema changes only.
Nothing about it is regulated or operationally critical yet.

Run both when

The cleanest split is by job. Power Apps keeps data capture, where offline, mobile and Dataverse matter. Link to Microsoft Fabric creates a Fabric lakehouse and SQL endpoint over the Dataverse tables, and a Fabric App reads them through its lakehouse connector alongside warehouse data the Power App never sees. Budget for the link's extra Dataverse database storage, which Microsoft notes on the same page. Field teams keep the app they know. Analysts and managers get a code-first view that joins it to everything else in Fabric. Neither app has to do the other's job.

Does Fabric Apps Run in UAE and Saudi Regions?

Quick answer: UAE North is not listed as excluding Fabric Apps, and UAE Central is a Power BI-only region. Saudi Arabia has no Fabric region today. Microsoft has announced its Saudi Arabia East region for November 2026 but has not said Fabric will run there. Confirm both before you plan a rebuild that has residency requirements.

Microsoft's Fabric region availability page (updated 25 September 2026) lists exceptions per region. UAE North has no Fabric Apps exclusion, which means "not excluded" rather than a stated guarantee. Saudi Arabia has no row, so an entity with in-Kingdom residency requirements has no documented Fabric Apps option today.

That may change. On 31 August 2026 Microsoft announced that its "Saudi Arabia East datacenter region will be available to customers in November 2026." The announcement refers only to "supported Microsoft cloud and AI services" and does not name Fabric, Power BI or Power Platform. Until the region appears on the Fabric region page, treat Fabric Apps in Saudi Arabia as unconfirmed.

Power Platform lists the United Arab Emirates as a data center geography. A Saudi geography for Power Platform could not be confirmed on Learn as of 18 October 2026, so a Saudi entity should get both platforms' residency position from its Microsoft account team before scoping either. The wider question is covered in Power BI data residency in the UAE and Saudi Arabia.

What Does Rebuilding a Power App as a Fabric App Involve?

Quick answer: A full rewrite. Learn has no conversion path from a canvas or model-driven app to a Fabric App, so formulas, data model, flows, security and deployment are all rebuilt in TypeScript, and the old app runs in parallel until users move.

The work, in the order it should happen:

Inventory the app. List its screens, Power Fx formulas, connectors, flows, Dataverse security roles and the users and licences it touches, then run it through the decision rule again. Many candidates turn out to be "stay" here.
Re-model the data. Fabric Apps "manages the database schema based on your TypeScript data models" and can't adopt an existing schema. Each table becomes an entity with a single UUID id, and many-to-many relationships become join entities. Data that stays in a Fabric warehouse or SQL database is reached through a connector.
Move the data. Export from Dataverse or SQL Server into the app database, or land it in Fabric and connect to it. Choice columns, lookups and owner fields each need an explicit mapping.
Rebuild the logic. Power Fx becomes TypeScript. Flows become server-side functions, which are in preview, run for up to 240 seconds and use the item owner's permissions, not the user's, for external connections.
Rebuild security. Dataverse security roles become @role declarations and row policies, plus row-level security on the connected source. External users need their own decision; Power BI Embedded licensing and RLS covers the analytics side.
Build your own release process. Without ALM, set up Git, separate test and production workspaces, and a scripted rayfin up deployment.
Run in parallel, then retire. Keep the Power App live until the Fabric App passes user testing, then remove Premium licences only for users with no other premium app.

A Fabric App scaffold deploys in minutes. The data mapping, logic and release process are where the time goes.

Beyond The Analytics reviews Power Apps portfolios against Fabric for UAE and Saudi enterprises, sorting each app into stay, rebuild or run both and costing the licence effect before anything is rewritten.

Frequently Asked Questions

Q: Will Fabric Apps replace Power Apps?

Microsoft has not said so, and nothing in its documentation positions Fabric Apps as a replacement. Fabric Apps is a preview backend platform for TypeScript developers building over Fabric data. Power Apps remains Microsoft's generally available low-code platform and added its own code-first option, code apps, in February 2026. Plan for both to exist.

Q: Are Power Apps code apps the same as Fabric Apps?

No. Both are code-first, but code apps are generally available and run on Power Platform with Dataverse, 1,500+ connectors, DLP and Power Apps Premium licensing. Fabric Apps run in a Fabric workspace, read Fabric data through connectors, consume Fabric capacity and are in preview. A team that wants code but needs Power Platform governance should start with code apps.

Q: Can a Fabric App work offline or on mobile?

A Fabric App is a standard web application, so it opens in a mobile browser. No Fabric Apps documentation describes offline use or a native mobile app as of 18 October 2026. Power Apps supports offline-first canvas apps over Dataverse and model-driven mobile offline, so offline field apps should stay on Power Apps.

Q: Can I convert a canvas app to a Fabric App?

Not automatically. Learn documents no conversion path. A move means rewriting Power Fx as TypeScript, re-modelling tables as Fabric Apps entities with single UUID keys, moving the data, rebuilding flows as functions and rebuilding security as role policies.

Q: Do Power BI Pro users get Fabric Apps at no extra cost?

Microsoft announced on 28 September 2026 that Pro and Premium Per User customers will get Fabric Apps and Fabric Database capabilities at no additional cost, up to 1 GB per app, through an "Apps in Power BI" preview. As of 18 October 2026 Learn still requires Fabric capacity for Fabric Apps and does not document the Pro terms or viewer licensing.

Q: Can Power Apps write back to Microsoft Fabric?

Not through Fabric-sourced Dataverse virtual tables, which Learn states are read-only. For write-back from Power BI reports into Fabric SQL databases, warehouses or lakehouse files, Microsoft's supported route is translytical task flows, generally available since March 2026.

Q: Is Fabric Apps generally available?

No. As of 18 October 2026, the Fabric Apps overview on Microsoft Learn still says "This feature is in preview," and the functions and connectors added in September 2026 are also preview. Microsoft has published no GA date, and Fabric Apps has no supported ALM yet.