If you’ve used Microsoft Fabric for analytics but never thought of it as a place to build and host actual applications — that’s exactly what changed my mind this week.

Using the Rayfin framework and Claude Code, I went from an empty folder to a live, authenticated, database-backed app in a single sitting. Auth, a real database with per-user security, and a public URL — all running inside Fabric.

Here’s the full walkthrough. 👇

What we actually built

A working To-Do app — but a real one, not a toy:

  • 🔐 Microsoft sign-in (Fabric brokered auth)

  • 🗄️ A real database with row-level security — every user only sees their own tasks

  • ⚡ Task priorities (High / Medium / Low) added end-to-end, from the data model to the UI

  • 🚀 One-command deploy to a live, shareable URL

The interesting part isn’t the app — it’s how little friction there was between idea and deployed product.

📄 Reference links:

The part that surprised me

The whole thing is declarative. You describe your data as a class — Todo, with fields and a security policy — and Rayfin turns that into a real database table with a check constraint and per-user access enforced server-side. When I added the priority feature, I touched three files and re-ran one deploy command. That’s it.

That’s a genuinely different feeling from wiring up a backend, a database, an auth provider, and a host separately.

What’s next

Part 2 is already in the works — using Semantic Model to work on DEMAND & FORECASTING write-back feature, and a few more features that turn this from a demo into something you’d actually use. Each part builds on the last.

Subscribe to follow the series, and if you want me to cover a specific Fabric App scenario, just reply — I read every response.

💬 Building something on Fabric? Hit reply and tell me what you’re working on.
🔔 New parts drop regularly — subscribe so you don’t miss Part 2.