M365Con 2027 – free online conference · 11–22 Jan 2027 · 120 sessions m365con.net

Blog · Mirko Peters

Microsoft Fabric Apps: What They Are and How to Use Them

By ·

Fabric Apps (preview) lets developers build data-driven apps on Microsoft Fabric with TypeScript. This guide covers what the feature is, the admin switch, how to create and deploy an app, permissions and current limits.

Fabric Apps is a Microsoft Fabric feature, currently in preview, for building data-driven applications. Developers write data models in TypeScript, and Fabric generates the database schema, GraphQL APIs, sign-in and hosting. It is aimed at developers, not at report authors, and it is separate from Power BI apps.

Key points

  • Fabric Apps is a preview feature built on the Rayfin SDK. Developers define data models in TypeScript and Fabric generates the database, GraphQL API, authentication and hosting.
  • A tenant admin must first enable Fabric Apps (preview) under Tenant settings in the Fabric admin portal, for the whole organization or for specific security groups.
  • The workspace needs Fabric capacity assigned. Fabric Apps services consume capacity units from it.
  • After deployment, sign-in is Fabric SSO through Microsoft Entra ID only. Email and password work only for local development.
  • Microsoft lists limits such as no many-to-many relations, no composite keys, no ALM and no private link support, so check them before you commit to a design.

What Fabric Apps does

Microsoft Learn describes Fabric Apps as built on the Rayfin SDK. You decorate TypeScript classes, for example with @entity(), @text() or @uuid(). From that model Fabric produces:

  • database tables, with a SQL database in Fabric as the managed store
  • a GraphQL endpoint at /api/graphql on the app backend URL
  • row-level authorization rules through @role decorators
  • type-safe client methods
  • static hosting for the frontend

When you deploy with rayfin up, Fabric creates child items under the app: a SQL database in Fabric, Authentication and Static Content. Each app has one backend endpoint of the form https://<your-app>-app.rayfin.windows.net/, with the paths /api/graphql for data and /auth for authentication.

Other documented capabilities include typed connectors to a lakehouse, warehouse, SQL database in Fabric or semantic model, and typed file storage with access policies.

Where it fits

Microsoft names these as good fits: rapid prototyping, internal tools and dashboards, data exploration with Fabric connectors, and AI or agent apps that need persistent state. It names these as possibly poor fits: apps that need complex multi-step transactions or stored procedures, and apps that need custom authentication providers.

Step 1: Enable the tenant setting

This is an admin task, and it must happen before users can create the item.

  1. Sign in to the Fabric admin portal.
  2. Open Tenant settings.
  3. Under Fabric Apps (preview), set the toggle to Enabled.
  4. Choose the entire organization or specific security groups.
  5. Select Apply.

Changes may take a few minutes to propagate.

Step 2: Prepare the workspace

The workspace must have Fabric capacity assigned. Choose a capacity when you create the workspace. To create an app you need Contributor or Admin permissions in it. For local work, install Node.js 20 or later.

Step 3: Create the app item

  1. In the left navigation, select Workspaces and open your workspace.
  2. Select New item, search for App, and select it.
  3. Enter a name and select Create.

The portal then shows a command to download a project locally. It has this shape:

npm create @microsoft/rayfin@latest -- "<appitemname>" --template todoapp --workspace <workspacename>

Step 4: Develop and deploy

Edit the project, or work with GitHub Copilot, then test against the Fabric backend with npm run dev. Deploy with npx rayfin up. To deploy to another workspace, add --workspace <workspacename>. Confirm the backend with npx rayfin up status.

The FAQ's example comment says a static-content-only deployment with npx rayfin up staticapp deploy takes 30 to 60 seconds after the initial deployment. The pages read give no time for the first deployment. A static-only deployment cannot create the initial remote app, so run npx rayfin up once first. To roll back, check out the earlier git commit and run npx rayfin up again.

What you see in the Fabric portal

After rayfin up, the app item shows child items that Fabric created from your rayfin.yml configuration:

  • SQL database in Fabric: the managed database with the schema from your decorators. It is read-only in the portal, so change the schema through code.
  • Authentication: Fabric-brokered sign-in through Microsoft Entra ID. You can view the authenticated users in the SQL database.
  • Static Content: the built frontend assets, served from a hosting URL and updated on each deploy. The overview says static hosting can require Fabric item access or allow anonymous access.

Authentication and permissions

Learn lists Fabric SSO for deployed apps and email and password for local development. Email and password sign-in does not work after deployment, and deploying requires Fabric authentication to be enabled.

Item permissions are separate from workspace roles:

| Permission | Allows | |---|---| | Run and interact | Open and use the app and call its backend APIs. All workspace members get it by default. | | Edit (Write) | Deploy, change schema, update settings, manage child services | | Reshare | Grant others access. Requires the admin role on the workspace. |

A Fabric administrator can temporarily block other users from loading an app, while the owner can still open it.

Security stays partly with you. Microsoft says to keep secrets out of code and frontend assets, and that your code decides what signed-in users see and do.

Limits to check first

The FAQ lists these current limitations:

  • no many-to-many relationships and no composite primary keys (every entity needs a single UUID field named id)
  • no custom authentication providers
  • no multi-environment management out of the box
  • no workspace outbound access protection
  • no tenant-level or workspace-level private links
  • no application lifecycle management (ALM)
  • count() is not available on the fluent GraphQL client

Data models are written in TypeScript with decorators.

Typical problems

Microsoft names a missing production build as the most common cause of build errors, so run npm run build first. For capacity or permission errors, confirm the workspace has capacity and that you can create or change items in it. For schema errors, review changes since the last successful deployment. The troubleshooting page says the app code is the source of truth. Do not change the remote schema through the Fabric portal or SQL tools, because removing or altering an existing column can break the app and its deployment. Make schema changes in code and apply them with npx rayfin up db apply.

Related

Sources

FAQ

Are Fabric Apps generally available?

No. Microsoft Learn marks Fabric Apps as a preview feature and says it is not available in all regions yet. The pages read for this article do not describe a general availability date.

Who can create a Fabric app?

According to Microsoft Learn, you need Contributor or Admin permissions in a Fabric workspace that has Fabric capacity, and a tenant admin must have enabled the Fabric Apps (preview) tenant setting. Node.js 20 or later is required for local development.

Which sign-in methods do deployed Fabric Apps support?

Microsoft Learn says deployed apps use Fabric SSO, which is Microsoft Entra single sign-on, exclusively. Email and password sign-in is available for local development only, and you cannot deploy without authentication enabled.

Can a Fabric app use an existing database?

No. The Microsoft Learn FAQ says Fabric Apps manages the schema from your TypeScript models and cannot point at a database with a predefined schema. To reach an existing lakehouse, warehouse or SQL database in Fabric, you add a connector.

Do the Microsoft pages explain pricing for Fabric Apps?

They do not. The pages read give no pricing. The overview only states that the workspace needs Fabric capacity and that Fabric Apps services consume capacity units from it, and the FAQ says performance depends on your Fabric capacity.

Entities in this article

Topics of this article:

Microsoft Fabric Apps – Analytics and BI tool by Microsoft Microsoft Fabric – Analytics and BI tool by Microsoft Fabric capacity – Concept Fabric tenant settings – Concept

Related articles

More articles on Microsoft Fabric:

RSS