Episode Details

Everyone loves to clown on Model-Driven Apps: “Old-school!” “Looks like 2008!” “Canvas does this better!” Fine. But here’s the punchline — I’ve built secure, production-ready Model-Driven apps fast, and in this video I’ll show you exactly how. By the end, you’ll see a plain Dataverse table turned into a themed, secure app with custom forms, views, a role, and even an automation — live. Subscribe to the M365.Show newsletter at m365 dot show so you don’t miss the follow-ups. Model-Driven isn’t supposed to be sexy — it’s supposed to work. Stick around for the 5-minute mark when that “boring” blank table becomes a usable form. And before we get there, let’s address why everyone insists these apps are boring in the first place.Why Everyone Thinks Model-Driven Apps Are BoringModel-Driven Apps carry a reputation problem. The common take is that they’re just old, stiff forms with no charm, no flexibility, and about as exciting as Windows XP’s Control Panel. That reputation sticks in kickoff meetings: bring up Canvas Apps and the room perks up; bring up Model-Driven and suddenly everyone needs another coffee. A lot of that comes from people who’ve only ever seen the default, grey starter app. They peek, smirk, and walk away. But judging it from that is like opening Excel, staring at the blank grid, and deciding spreadsheets are pointless—you never even tried the formulas. The criticism usually circles the same points. The interface looks dated. It’s not as customizable out of the box. Compared to the instant drag-and-drop magic in Canvas, it doesn’t grab attention. And to be fair, if your only exposure is the raw starter template, you’d assume it’s lifeless. Microsoft’s demo culture doesn’t exactly help either: Canvas is all bright colors and custom layouts, while Model-Driven gets positioned as “the serious option nobody shows off.” The flashy one is the cousin doing TikTok dances; Model-Driven is the one who shows up on time with the project plan. I’ll give you a concrete story. On one rollout I supported, the manager was sold on Canvas. The mock-ups looked slick. It impressed at first. But the moment our Dataverse schema started evolving, things got messy. Every column tweak triggered a handful of fixes across the app—dropdowns broke, formulas needed re-pointing, visibility conditions stopped working. It wasn’t catastrophic, but it was constant patching. Meanwhile, the Model-Driven build we had sitting quietly in parallel kept pace with the schema changes because the form logic was already sitting where it belonged—in Dataverse. No scrambling, no rework, just steady updates. That “boring” Honda Civic app ran quietly while the sports car prototype was in the shop. This stability isn’t about luck. In practice, when we use Model-Driven builds, the core business logic lives directly in Dataverse rather than being stretched over connectors and side scripts. That means when the schema shifts, the platform adjusts without a lot of duct tape. I’ve seen the difference firsthand. And to avoid staying too theoretical, we’ll actually attach a security role and wire up a relationship live in this demo so you can see how it behaves, not just hear me say it. Another piece the critics miss is security. In many Canvas builds, you end up writing conditions or duplicating checks in a few flows. In contrast, Model-Driven apps tie straight into Microsoft’s role-based model. In my experience, if an auditor or finance manager needs a clean division of what they can view versus what they can edit, roles handle it without me reinventing the wheel. It doesn’t look flashy, but it scales without panic. And that’s exactly why enterprise environments lean on it. Bottom line: Model-Driven isn’t trying to win design awards. It’s designed to get you to production without constant fires. People can call it dull, but dull and stable beats pretty and fragile when the business depends on it. Sure, it may not sparkle in the first five minutes, but once you push it, you