Forum Discussion

sashakorniakUK's avatar
sashakorniakUK
Brass Contributor
Dec 30, 2025

Request for Advice on Managing Shared Glossary Terms in Microsoft Purview

Hi everyone,

I'm looking for guidance from others who are working with Microsoft Purview (Unified Catalog), especially around glossary and governance domain design.

 

Scenario; I have multiple governance domains, all within the same Purview tenant. We have some core business concepts from the conceptual data models for example, a term like “PARTY”  that are needed in every governance domain.

However, based on Microsoft’s documentation:

  • Glossary terms can only be created inside a specific governance domain, not at a tenant‑wide or global level.
  • The Enterprise Glossary is only a consolidated view, not a place to create global terms or maintain a single shared version. It simply displays all terms from all domains in one list.
  • If the same term is needed across domains, Purview requires separate term objects in each domain.
  • Consistency must therefore be managed manually (by re‑creating the term in each domain) or by importing/exporting via CSV or automation (API/PyApacheAtlas)?

This leads to questions about maintainability; especially when we want one consistent definition across all domains.

What I'm hoping to understand from others:

  • How are you handling shared enterprise concepts – enterprise and conceptual data models that need to appear in multiple governance domains?
  • Are you duplicating terms in each domain and synchronising them manually or via automation?
  • Have you adopted a “central domain” for hosting enterprise‑standard terms and then linking or referencing them in other domains?
  • Is there any better pattern you’ve found to avoid fragmentation and to ensure consistent definitions across domains?

Any advice, lessons learned, or examples of how you’ve structured glossary governance in Purview would be really helpful.

this is be a primary ORKS - Establish a unified method to consistently link individual entities (e.g., PARTY) to their associated PII‑classified column‑level data assets in Microsoft Purview, ensuring sensitive data is accurately identified, governed, and monitored across all domains. – I.e CDE to Glossary terms

 

Thanks in advance!

No RepliesBe the first to reply

Resources