For years, doing data governance with Microsoft's tooling felt like assembling flat-pack furniture with the instructions for three different products open at once. Classification lived in one place, lineage in another, policy somewhere else, the glossary off in its own corner. You could do all of it — but you spent half your energy just navigating between the parts. So when Microsoft rolled out the redesigned Purview portal and folded that scattered toolkit into a single interface, my first reaction was genuine relief. My second was a caution I want to spend this post on, because it matters more than the portal.

Here's the caution, up front: a unified portal removes an excuse, not the work. It makes governance easier to start. It does nothing to make the decisions governance actually consists of. And if you mistake the second thing for the first, you'll end up with a beautiful, consolidated interface displaying an ungoverned estate very tidily.

What actually got better

Let me give the redesign its due, because the improvement is real and I don't want to be the person who sneers at a genuine step forward.

  • One front door. Classification, the data catalogue, lineage, policy, and the business glossary now sit behind a single, coherent interface instead of being strewn across separate experiences. The cognitive cost of "where do I even go to do this" drops sharply, and that cost was a real barrier — not a glamorous one, but the kind that quietly kills adoption.
  • Lineage you'll actually look at. Seeing where a dataset came from and what feeds off it — visually, in the same place you manage everything else — turns lineage from a compliance artefact into something people consult when they're about to change a pipeline and want to know what they'll break.
  • Closer ties to where the data lives. With governance surfacing nearer to the Fabric estate it's meant to govern, the gap between "the data" and "the governance of the data" narrows. That gap is where governance usually goes to die, so narrowing it is worth a lot.

None of this is cosmetic. Lowering the friction of a task genuinely changes how often people do it, and I've watched teams adopt governance practices purely because someone finally made them a two-click job instead of a scavenger hunt. Credit where it's due.

Why a portal still isn't a strategy

And yet. Every one of those improvements is about the mechanics of governance — the how and the where. Not one of them touches the substance, which is a set of human decisions no interface can make for you:

  • What actually matters here? The catalogue can hold everything. It shouldn't. Deciding which data assets are worth governing — and having the discipline to leave the rest alone — is a judgement call about your business, not a feature.
  • Who owns this? The portal has a field for a data owner. It cannot tell you who that person should be, cannot make them accept the responsibility, and cannot stop the name going stale the day they change teams.
  • What does this word mean? The glossary will faithfully store your definition of "active customer." It has no opinion on whether your sales and finance teams actually agree on that definition — and if they don't, the glossary just gives their disagreement a tidier home.

That's the pattern. Every place the portal offers a box, the real work is deciding what goes in the box, and that deciding is organisational and often political. A better UI accelerates the parts that were never the bottleneck and leaves the actual bottleneck — human agreement — exactly where it was.

A consolidated portal is a better map. It is not the journey, and it will happily give you crisp, unified directions to nowhere in particular.

How to use the redesign well

So what's the mature way to take advantage of this, if the portal genuinely helps but can't do the hard part? Use the lowered friction as a prompt to do the human work, not a substitute for it.

Concretely, the move I'd make: pick one domain that genuinely matters — the data behind the report leadership actually reads — and use the newly-unified portal to do that domain properly, end to end. Classify its sensitive fields. Trace its lineage. Name a real, willing owner on the assets themselves. Agree and record the handful of definitions that domain depends on. Because the portal now makes each of those steps low-friction, you can actually finish, and finishing one domain well teaches you more than half-governing forty.

What I'd avoid is the trap the redesign quietly invites: opening the shiny new portal, seeing all those capabilities in one place, and trying to switch them all on across the whole estate at once. The interface makes that feel achievable in a way it wasn't before. It isn't. Governance still has to be earned domain by domain, decision by decision, and the unified portal just means each of those decisions costs less to act on once you've made it.

The real verdict

I'm genuinely glad this redesign exists. For anyone who owns data governance on the Microsoft stack, it removes a category of daily friction that was doing real damage — the small, grinding cost of a fragmented toolset that made people avoid the work. That's a good day.

But I've learned to be wary of the specific relief a better tool brings, because it's so easily mistaken for progress on the underlying problem. The portal got dramatically better. Governance got exactly as hard as it always was — because governance was never a tooling problem. It's a problem of deciding what matters, who's accountable, and what your words mean, and then keeping those decisions alive as the organisation churns around them. Microsoft just built you a much nicer room to have those conversations in. You still have to have them.