Microsoft master data management in 2026: what Microsoft ships, and what it points you at

Microsoft does not sell a master data management product. That lands oddly, because Microsoft sold one for fifteen years. Master Data Services shipped inside SQL Server from 2008 R2 onwards, and Microsoft removed it in SQL Server 2025. Nothing took its place. The page on Microsoft Learn titled “Master Data Management in Microsoft Purview” is, read literally, an explanation of how to connect someone else's MDM product to Purview.

If you came here looking for a product page, that is the short version. The longer one is worth having before you walk into a meeting about it, because each piece of the stack covers a different slice of the problem and the seam between them is where the work lands on you.

The one product Microsoft did ship is gone

SQL Server 2022 is the last version that carries MDS. Mainstream support for it ends on 11 January 2028 and extended support runs to 11 January 2033, so the security patches keep coming for years. That timeline is not the one that matters. The binding constraint is the day someone decides to upgrade the instance, because MDS cannot come with it. There is no successor product and Microsoft published no migration tooling. We covered the mechanics of that in what to do before your next SQL Server upgrade.

It is worth being fair to MDS on the way out. It was free with a license you already owned, it ran on a SQL Server your DBAs already backed up, and it had a real entity model, derived hierarchies, business rules, governed versions, and an Excel add-in that data stewards genuinely used. It never had fuzzy matching or survivorship, which the enterprise vendors would tell you about at length. Most mid-market teams did not need those and were perfectly happy.

Purview governs master data. It does not create any.

Ask Microsoft where MDM lives now and you get pointed at Purview. The documentation is more honest than the pointer. Read the nine-step flow it describes and watch where each step happens: Purview registers and scans the source, and you create a data product and a glossary term. Then the partner MDM application picks up the signal, pulls the metadata, connects to the source systems, copies the data, unifies and cleanses and standardizes it, and creates the golden records. The metadata is published back into the Unified Catalog at the end.

Purview brackets the process. The mastering happens in the middle, in software you buy from someone else. Microsoft names four: CluedIn, Profisee, Reltio, and Semarchy. All four are enterprise platforms with enterprise pricing and implementations measured in quarters.

None of this is a knock on Purview. It is a catalog and a good one, and a catalog is a useful thing to own. It is simply not the tool you are looking for when what you need is a screen where a data steward creates a cost centre, gets stopped from creating a duplicate, and has the change approved by someone. That distinction is the whole subject of MDM is not a data catalog.

Fabric has a stewardship grid now, but not a model

This is the part of the picture that moved most recently, and plenty of write-ups have not caught up. PowerTable, a component of the Plan item and still in preview, is described by Microsoft as a no-code reference and master data management platform: an Excel-like grid with write-back, approval workflows, change history, and row- and column-level security. That is a real editing surface, and a year ago it did not exist.

What it does not give you is the structural half of MDS: models and entities, domain-based attributes, derived hierarchies, versions you can lock and commit. It also arrives inside an enterprise planning and budgeting product rather than as a master data tool in its own right, which shapes whose roadmap it sits on. We went through it properly in is there Master Data Services in Microsoft Fabric.

Dataverse and Power Platform: the parts, not the product

The build-it-yourself route is legitimate and plenty of teams have taken it. Dataverse tables hold the entities, a Power App gives stewards a screen, Power Automate handles validation and approval routing, and the result lands somewhere Fabric can read it. For four flat code lists this works and costs almost nothing. What you are signing for is ownership. Derived hierarchies, governed versions, per-attribute permissions, and a field-level audit trail are now yours to build, test, document, and maintain for as long as the thing lives. Projects on this route tend to go well until the second hierarchy shows up, and then they stop being a weekend.

The stack at a glance

The gap Microsoft leaves open

Put the rows together and a shape appears. Microsoft covers the enterprise end through partners and the do-it-yourself end through Power Platform. What sits between them is exactly where MDS used to sit: an organization with a few thousand cost centres, suppliers, or plant codes, a couple of data stewards, a SQL Server they trust, and no appetite for a six-figure platform or a bespoke app.

That is not an accident or an oversight. MDS was never a strategic product for Microsoft; it was a feature in a database license. Once the strategy moved to Fabric and Purview, a self-hosted stewardship UI for mid-market SQL Server shops had no obvious home, and the partner model handles the customers large enough to be worth handling. It is a coherent decision. It just leaves several thousand organizations holding a working system with no upgrade path.

Where Primentra fits

We built Primentra for that middle. It runs on your own SQL Server, keeps the MDS vocabulary your models were built on, and gives stewards a browser grid that behaves like the spreadsheet they were going to use anyway. Approvals, a field-level audit trail, and per-attribute permissions come with it rather than being a project. Because the concepts line up, migrating an MDS model is a mapping exercise instead of a redesign.

It sits beside the rest of the Microsoft stack rather than replacing any of it. Master data lives in SQL Server tables and views, so Fabric reads it through a shortcut or a pipeline like any other source, and Purview scans and catalogs it the same way it scans everything else. If you are still weighing options, the five best MDS alternatives puts us next to the enterprise platforms with pricing attached.

Frequently asked questions