Certified vs Promoted Endorsements in Microsoft Fabric: How to Use Them

In a growing Fabric estate, the same data exists in several places and every item looks equally official. So a user searching for "sales" finds five datasets and picks whichever appears first — often not the trusted one. The result is reports built on the wrong copy, numbers that disagree, and a slow erosion of trust in the platform.

Endorsements fix this cheaply. By marking which items are trustworthy, they let users — and AI agents — tell the authoritative source from an incidental copy at a glance. No new infrastructure, no migration; just a signal on the items that already exist. It is the highest return for the least effort in Fabric governance.

But the signal only works if it is applied with discipline. An endorsement everyone can grant to anything is not a signal at all, which is why understanding the two levels — promoted and certified — and using them correctly is the whole game.

Promotion is the lighter of the two endorsements. An owner or contributor of an item can promote it to say "this is ready for others to use" — a self-service signal that does not require central sign-off. It is meant to be used relatively freely by the people who build and own data.

Promotion is the right level for the large middle of your estate: datasets and reports that are legitimate and ready to share but are not the single authoritative source for a critical measure. It lets teams signal quality and readiness without a governance bottleneck, which keeps the catalog useful and current.

Because promotion is decentralised, it scales — every data owner can keep their good items promoted. The trade-off is that promotion alone cannot distinguish the truly authoritative asset from the merely good one, which is what certification is for.

Certification is the stronger endorsement, and it means something more specific: this is an authoritative, trusted asset that the organisation stands behind. It is reserved for the datasets and reports that are the single source of truth for important measures, and it is granted under a defined process by a limited, authorised group — not by any owner.

The control is the point. Certification is valuable precisely because it is scarce and governed. If anyone could certify anything, the badge would carry no more weight than promotion. By restricting who can certify and requiring the asset to meet a standard, certification stays a reliable signal that a user can trust without further checking.

This is why certification needs a small authorised group and a clear standard for what qualifies — usually the data governance function or designated data owners, applying criteria for quality, ownership and documentation. Certification handed out freely is the fastest way to make endorsements meaningless.

Endorsements degrade without a process. Certification needs a defined path: who can request it, who approves, what standard an asset must meet (clear ownership, documented measures, appropriate sensitivity, a maintenance commitment), and how it is reviewed when the asset changes. Without this, certifications accumulate, go stale, and stop being trustworthy.

Promotion needs lighter governance but still needs owners who keep their promoted items current — a promoted dataset that has quietly broken is worse than an unpromoted one. Build a periodic review into the governance posture work the OneLake catalog surfaces, so endorsements reflect current reality rather than a one-time decision.

Assign ownership of the endorsement scheme itself. Someone needs to own "what does certified mean here and who can grant it", because an endorsement scheme with no owner drifts into inconsistency, and inconsistent endorsements are as bad as none. This is modest ongoing work for a large payoff in trust.

Use the two levels for what they are: promote generously so the good, ready items are signalled by their owners, and certify tightly through a controlled process so the authoritative sources stand out clearly. That combination lets any user — and any agent — pick the right data by default instead of guessing, which is the whole point.

This matters more than ever because AI agents ground on your data. A Fabric Data Agent or Copilot reasoning over the catalog should ground on certified, endorsed sources, not the nearest available table — and endorsements are the signal that makes that possible. A well-run endorsement scheme is not just tidiness; it is what makes AI over your data trustworthy.

So treat endorsements as a foundational governance practice, cheap to start and high in payoff, with a clear owner and a light process. Get them right and the wrong-copy problem largely disappears for people and agents alike; neglect them and the badges become decoration within a quarter.