Episode Details

If you've ever felt lost tracking down who accessed which dataset in Microsoft 365, get ready: Fabric governance might look familiar, but there are some surprises you need to see. Is your M365 compliance experience enough to tame this new platform—or are there catches nobody told you about?Stick around. I'm going to show you exactly where Fabric borrows from M365, and where it changes the rules—sometimes when you least expect it.Why Fabric Governance Catches Admins Off GuardIf you’re coming from Microsoft 365, it’s easy to assume Fabric will just slot in under your usual admin workflow. You launch the admin center and start poking around, expecting the settings menu to lead you where you need to go. That’s where Fabric throws its first curveball. The environment looks close enough to feel comfortable—at least on the surface. The icons line up, the workspaces have familiar names, and you will see labels that remind you of Teams or SharePoint. But try moving through the standard setup and your muscle memory instantly trips over the differences. Permissions aren’t hiding in their normal place, and when you do find them, the options read a little differently. That sense of “I’ve been here before” fades out as soon as you start looking for an old-school bridge, like a straightforward inheritance pattern or one-click audit configuration.Think about the admin who’s spent years fine-tuning access in SharePoint. They walk into Fabric with a certain confidence—menus in Microsoft should follow a type of logic, right? The expectation is: all those tricks for handling nested permissions, inheritance, even the group-based controls for managing access, should translate. But Fabric breaks from that rhythm. You’re looking for a way to adjust permissions on a library or a list, but Fabric wants you thinking about domains, workspaces, and specific items instead. Instead of a predictable stack of settings, you get overlapping pages, new terminology, and extra layers that don’t quite line up with what you’d expect. Even the simple act of assigning a role comes with extra caveats about what “Admin,” “Contributor,” or “Member” really means for a workspace versus a data item.That’s where the friction starts. The marketing for Fabric sold it as an extension of what you already know, so you start by running your go-to playbook. You copy over your M365 permission structures, thinking, “that should cover us.” And right away, the cracks appear. Simple questions—like “if I label this dataset as Confidential, will it actually limit who can export or share it?”—aren’t answered where you’d expect. Suddenly, you’re off to the documentation. And it isn’t just you. We’ve all seen admins—seasoned ones—getting stumped by why their access controls don’t stick or why their compliance monitor isn’t catching everything.There’s definitely a learning curve. The language is similar enough to lure you into old habits, but key words have shifted. Menus overlap so you’re jumping between multiple screens trying to figure out which setting overrides the other. And some controls are split between the Fabric portal and the broader M365 admin center, or worse, they look joined but behave differently behind the scenes. You get this odd mashup—like déjà vu, but with enough details out of place to slow you down at every step. It isn’t just an annoyance for people who like things tidy; it means mistakes slip through the cracks. Auditing isn’t as obvious. Permission inheritance doesn’t always kick in. Meanwhile, you’re getting pinged by the business when someone accidentally lets an unauthorized user peek at a sensitive dataset.Speaking of that, here’s the kind of scenario that happens more often than folks like to admit: a business analyst goes to share a dataset they’ve marked as “internal.” In M365, their previous experience taught them that sensitivity labels would cascade, restricting sharing outside the company. So they assume Fabric is doing the same thing in the background. E