Your MDS Excel Add-in Stopped Working. Here’s What Happened — and What to Use Instead.

The MDS Excel add-in stops working for several unrelated reasons, and they look almost identical from the steward's desk. The three common ones: Excel disabled the add-in after a crash, its LoadBehavior registry value was reset, or ActiveX controls are blocked and the data never finishes loading. Each has a different fix, and each fix is temporary, because MDS is removed from SQL Server 2025 entirely. The durable answer is a browser-based grid that needs no plugin at all.

Before you change anything, work out which of two situations you are in, because they have nothing to do with each other. Either the Master Data tab is missing from the ribbon, or the tab is there and looks entirely normal but the rows never arrive. The first is the add-in failing to load. The second is the add-in loading fine and its data path failing. People lose days to this distinction, because both get reported to IT as “the MDS add-in stopped working”.

If this happened to your team, you are in a large crowd. The add-in has been failing on people since the Excel 2013 era, and the reports pile up on the Microsoft forums with the same title and half a dozen different causes underneath. Below are the three that account for most of them, how to tell which one you have, and why fixing it buys you months rather than years.

The three causes worth checking

The tab is missing: Excel disabled the add-in after a crash

Excel disables COM add-ins that crash on it, and it does so quietly. Look under File → Options → Add-ins → Disabled Items and re-enable it there. If it lands back in that list after every restart, the add-in is crashing during load and you are looking at a repair or a reinstall. This is the oldest failure mode of the three; people were reporting it on Excel 2013 and SQL Server 2012, years before ActiveX had anything to do with it.

The tab is missing: LoadBehavior was reset

The add-in's registration under HKLM\SOFTWARE\Microsoft\Office\Excel\AddIns carries a LoadBehavior value, which should be 3. A crash, an Office repair, or a policy can leave it at 0, and then the add-in simply never loads. Set it back to 3. On a machine mixing 32-bit and 64-bit Office components, check under Wow6432Node as well.

The tab is there but no rows arrive: ActiveX

Microsoft notes on the add-in's product page that you must enable ActiveX controls in Excel, “otherwise the data from the MDS database might not complete the load”. The add-in itself is a VSTO add-in and loads through a different mechanism, so the ribbon tab appears either way. It is the fetching and publishing of records that is at stake. Since Office build 2504, released April 2025, ActiveX is off by default, which is why this cause became far more common than it used to be. You can check the state in File → Options → Trust Center → Trust Center Settings → ActiveX Settings.

Worth knowing before you blame ActiveX: Microsoft added that note to the documentation in December 2023, sixteen months before the build 2504 change, so it describes an older quirk of the add-in rather than a consequence of that update. Its wording is careful too — “might not complete the load”, not “will fail”. We have a machine here on Semi-Annual Enterprise Channel, running build 2606 with ActiveX off by default, where the add-in still loads and publishes without complaint. So treat ActiveX as one documented cause to rule out, not as the explanation. If your tab is missing entirely, it is not this one at all.

The registry workaround is duct tape

Say ActiveX does turn out to be your cause. Forums are full of the fix: set DisableAllActiveX to 0 under HKCU\Software\Microsoft\Office\Common\Security, or push it via Group Policy. Your rows come back. Problem solved. Except for three things.

First, you're fighting Microsoft's direction. They disabled ActiveX for security reasons, and they're not going to reverse that. The next Office update might break your override again. Your security team will keep flagging the registry exception. And the longer you maintain this workaround, the less time you have to actually migrate before MDS itself disappears.

Second, MDS itself is deprecated. Even if you get the add-in working today, MDS is gone in SQL Server 2025. The product has no roadmap, no new features, and an explicit end-of-life. Re-enabling the add-in keeps a dying product alive for a few more months — our guide to Microsoft MDS end of life covers the dates and what to do before your next upgrade.

Third — and this is the one nobody talks about — the MDS Excel add-in was never good. It was the least bad option for getting non-technical users into MDS without the Silverlight web UI, which was worse. But it had real limitations that teams simply learned to live with.

What the add-in couldn't do (even when it worked)

The MDS Excel add-in gave your data stewards a spreadsheet-like view of entity data. That sounds fine until you think about what a master data editing interface actually needs.

What a replacement actually needs to do

The MDS Excel add-in was popular for one reason: data stewards didn't want to learn a new tool. Excel was familiar. Filtering, sorting, copy-pasting — they already knew how. Any replacement that forces them into a radically different workflow will face the same adoption problem MDS's Silverlight UI had.

The answer isn't “Excel in the cloud” or another add-in. It's a browser-based grid that feels like a spreadsheet but behaves like a proper data management tool. Click a cell, type, done. No “Publish” button. No version conflicts. No ActiveX.

The grid needs to support the things Excel couldn't: domain dropdowns that filter based on parent values (so you don't show 200 departments when only 12 belong to the selected branch), per-row audit trails visible on click, and an approval workflow that doesn't require users to understand what a changeset is.

And it needs to run on SQL Server. Not beside it. Not in Azure with a sync connector. On the same database your team already manages. The whole point of MDS was that master data lived in your SQL Server instance. That shouldn't change just because the UI does.

How Primentra replaces the MDS Excel add-in

Primentra is a browser-based master data management tool that runs on your SQL Server. There's no Excel add-in, no ActiveX, no COM registration, and nothing for Microsoft to disable in a future update.

Data stewards open a URL, see their entities in a grid, and start editing. Click a cell, type the new value — it saves automatically. Filter, sort, paste from clipboard, add rows, delete rows. The keyboard shortcuts are the same ones they already know from Excel: Tab to move right, Enter to move down, Ctrl+C/V to copy and paste. The learning curve is measured in minutes, not weeks.

The stuff the Excel add-in couldn't do is where it gets interesting. Every edit is logged with who changed it, when, and what the old value was — the kind of per-field audit trail no spreadsheet can keep. Domain dropdowns actually filter based on parent values, so your data stewards see 12 relevant departments instead of all 200. And the approval workflow is straightforward: submit changes, someone approves or rejects them, done. No changesets, no staging tables to babysit. We wrote more about the cascading dropdown filters in a separate post.

If you're migrating from MDS, the migration wizard brings your models, entities, and attributes over. Your data stays in SQL Server. Your DBAs can still query the tables directly. Nothing moves to the cloud unless you want it to.

Frequently asked questions