My first experience: Building a Fabric App

My first experience: Building a Fabric App

Data Factory

by Erwin | Jun 7, 2026

My first experience: Building a Fabric App on top of my FMD Framework

 

At Microsoft Build 2026, Microsoft introduced Rayfin a major step forward in how we build applications on Microsoft Fabric.

If you’ve been working in the Fabric ecosystem, this is big.

Rayfin is an open‑source SDK + CLI that lets you define and deploy a complete, governed application backend directly on Microsoft Fabric.

No more stitching together databases, APIs, authentication, and governance yourself.

Instead:

You define your backend in code → Rayfin provisions everything → Fabric runs it with enterprise-grade governance by default.

So when Rayfin was introduces I couldn’t resist trying it out immediately.

So I did what I always do…

I plugged it into something real.

I built a simple web configuration portal on top of my Fabric Metadata-Driven (FMD) Framework to manage metadata not through notebooks or pipelines, but through a clean UI.

What I built (in a few hours)

I created a lightweight metadata management app:

  • A web interface to fill metadata through a portal
  • A light master data app using static tables
  • But with the flexibility to:
    • Add new tables
    • Add new columns
    • Extend the model yourself

Basically:

A dynamic metadata-driven admin UI on top of Fabric

Was it production-ready?
No, just a mockup.

Was it powerful?

Absolutely.Fabric web app

 What surprised me most

The speed.

Normally, building something like this requires:

  • Backend APIs
  • Database configuration
  • Authentication setup
  • Access policies
  • Deployment pipelines

With Rayfin?

None of that was manual anymore

I just:

  1. Defined the data model
  2. Added some logic
  3. Ran the deployment

And Fabric handled the rest:

  • Database
  • APIs
  • Auth
  • Governance

This aligns exactly with what Rayfin is designed to do:

Define your backend in code and deploy it directly to Fabric as a governed app.

What else did I try

I build a master data management web app mockup, just as a try.

The master data management web app combines predefined tables with full flexibility to extend the model yourself. Core entities like products, categories, suppliers, and customers are available out of the box, providing a solid starting point for managing standard master data. At the same time, the app introduces a powerful capability: users can create custom tables and add new columns dynamically, effectively evolving the data model without needing to redeploy or change backend code.

Fabric web app master data

 

Just try outs, but amazing fast. I will explore the Fabric app the coming weeks/months much more.

The essential Rayfin docs (bookmark this)

If you want to go hands-on, these are the core docs you’ll actually use:
Get Started — Create your first Fabric App

Create your first Fabric apps project

Deploy to Microsoft Fabric

Deploy a Fabric App to Fabric

Read & Write Data with GraphQL

Read and write data with GraphQL in Fabric Apps

Configure Authentication

fabric_webb_app_master data Configure Fabric SSO authentication for your Fabric app

Understand the Project Structure

Fabric Apps project structure

Rayfin CLI Reference

Rayfin CLI reference

Connect to a Semantic Model (Data App Template)

 

 

Feel free to leave a comment

Creating Notebook Connections in Microsoft Fabric Just Became a Lot Easier (and Automatable!)

Creating Notebook Connections in Microsoft Fabric Just Became a Lot Easier (and Automatable!)

Data Factory

by Erwin | Mar 3, 2026

For a long time, creating a Notebook connection in Microsoft Fabric was surprisingly limited.

If you wanted a Notebook to run under a Workspace Identity or Service Principal, you only could configure this directly in the DataPipeline UI. In fact, the Connections pane didn’t even allow creating Notebook connections at all.

Instead, the only workaround was:

  1. Create a Data Pipeline
  2. Add a Notebook activity
  3. Create the connection from the pipeline activity dialog

Not only was this clunky, it also meant:

  • ❌ No way to create Notebook connections via REST API
  • ❌ No way to create Notebook connections via the Fabric CLI
  • ❌ Impossible to automate
  • ❌ Notebooks always ran in the context of the current user
  • ❌ You couldn’t use a Service Principal or Workspace Identity to access external services (like Azure Key Vault)

But that’s now history.

New: Create Notebook Connections Directly in the Connection Pane

Microsoft Fabric has rolled out support for creating Notebook connections directly from the Connection Pane.

You can now:

✔ Go to the Connections pane
✔ Create a new Notebook connection instantly

No pipeline workaround.
No hidden dialogs.
No friction.

Fabric Notebook Connection

Now Also Available via REST API and Fabric CLI

Even better: Notebook connections are now fully API‑enabled.

You can now create Notebook connections programmatically, enabling:

  • CI/CD
  • Environment provisioning
  • Automated workspace setup
  • Secure, identity‑based compute execution

Here’s an example using the fabric-cli:

fab create .connections/CON_FMD_NOTEBOOKS.Connection 
  -P connectionDetails.type=Notebook 
  -P connectionDetails.creationMethod=Notebook.Actions 
  -P credentialDetails.type=WorkspaceIdentity
This creates a Notebook connection that executes the Notebook using the workspace identity, ideal for secure and automated workloads.

Why This Matters

This change unlocks several important scenarios:

1. Run Notebooks using a Service Principal or Workspace Identity

Previously, Notebooks always ran in the context of the interactive user, which meant:

  • No headless automation
  • No scheduled jobs under a service principal
  • No secure, non-human execution

Now, a Notebook can run using:

  • ✔ Workspace Identity
  • ✔ Service Principal (with credentials in Key Vault)

Prerequisite:

Sign in to the Fabric admin portal. You need to be a Fabric admin to see the tenant settings page. 

Select the switch for the type of admin APIs you want to enable: Developer settings:

  • Service principals can create workspaces, connections, and deployment pipelines

In case you need to use a security group add the security group to above settings Add Workspace identity(after deployment) or Service Principal to the security groups

2. Access Azure Key Vault Securely

Because the Notebook now runs under an identity and not the user who executes the activity, you can:

  • Get secrets from Azure Key Vault
  • Access Azure Storage
  • Access SQL / Fabric data sources
  • Interact with other Azure services

This was not possible before unless you manually authenticated as yourself.

Final Thoughts

This seemingly small change removes a major blocker in Fabric’s engineering story.
By enabling Notebook connection creation in:

  • the Connections pane,
  • the REST API, and
  • the Fabric CLI,

Microsoft Fabric is now far more automation‑friendly and enterprise‑ready.

Running Notebooks using a Service Principal or Workspace Identity unlocks secure patterns that were previously impossible.

If you're building production pipelines, automated deployments, or secure identity-aware workloads, this is a huge step forward.

Feel free to leave a comment