What is an Enterprise Data Catalogue (EDC)?

What is an Enterprise Data Catalogue?

An Enterprise Data Catalogue (EDC) is more than a searchable list of datasets.

A basic Data Catalogue may tell you what data exists. An Enterprise Data Catalogue adds the wider business and governance context people need to decide whether that data is useful, trustworthy and appropriate for their purpose.

It should help a Data Consumer answer questions such as:

WHAT IS IT? • WHO OWNS IT? • WHAT DOES IT MEAN? • CAN I TRUST IT? • IS IT SENSITIVE? • HOW DO I ACCESS IT?

Data Catalogue vs Enterprise Data Catalogue

Think of It as Your Organisation’s Data Shop

Traditional catalogues help people understand what is available before they choose or request something. The same idea applies to organisational data.

An Enterprise Data Catalogue provides one place where people can discover available data, understand what it is for, compare options and work out what they need to do next.

The catalogue does not need to contain the underlying business data itself. Instead, it provides the information about that data — the metadata and governance context that makes the data discoverable and understandable.

Metadata is Not the Data

This distinction is fundamental.

Microsoft Purview catalogues metadata about the data. The underlying databases, files, reports, dashboards and applications remain in their source systems.

Metadata can describe:

• What the data asset is called and where it is located
• What a Data Product is designed to support
• Who owns and stewards it
• Business definitions and glossary relationships
• Schema and technical structure
• Lineage and where the data came from
• Data Quality and Data Health information
• Classifications, sensitivity and governance context
• How a consumer can request or obtain appropriate access

Why Organisations Need an Enterprise Data Catalogue

An EDC helps address recurring Data Governance problems that become harder as an organisation grows.

1. Ownership
   Who is accountable for the data, and who can help when there is a question or problem?
2. Finding and access
   What data exists, where is it, and what process should a consumer follow to access it?
3. Time and efficiency
   How much time is lost searching across systems, asking colleagues and following unclear approval routes?
4. Data maturity
   Does the organisation have consistent ownership, metadata, quality and governance practices across its data estate?
5. Data silos
   Can people discover data held by other teams and platforms instead of only knowing about data within their immediate area?
6. Duplicate data and definitions
   Are teams recreating the same datasets or using different meanings for the same business concepts?
7. Compliance and regulatory risk
   Can the organisation identify where sensitive, personal or regulated data exists and who is responsible for it?
8. Data Quality
   Is the data accurate, complete and suitable for the intended purpose?
9. Trust in data
   Can a Data Consumer understand enough about the data to use it with confidence?

Sensitive Data Still Needs to Be Discoverable

A common concern is that highly sensitive data should not appear in a catalogue. But hiding the existence of sensitive data can make governance harder.

Cataloguing the metadata does not mean exposing the underlying sensitive records. It can instead make the organisation better able to see where sensitive data exists, who owns it, how it flows and what controls should apply.

Visibility enables governance. Governance helps reduce risk and build trust in data.

How Microsoft Purview Supports the EDC

Microsoft Purview can provide the metadata and governance capabilities that support an Enterprise Data Catalogue.

Data Map provides the technical metadata foundation by registering and scanning supported data sources and capturing information such as assets, schemas, classifications and lineage.

Unified Catalog adds the business-facing governance experience, including Data Products, business context, ownership, stewardship, glossary relationships, Data Quality context and governed discovery.

Together, these capabilities can help turn a fragmented technical data estate into a more understandable and governed experience for Data Consumers.

What Good Looks Like for a Data Consumer

A Data Consumer should be able to start with a business need rather than needing to know the name of a database or which team owns it.

A useful Enterprise Data Catalogue should help them:

• Discover relevant Data Products and assets
• Understand their meaning and intended use
• Identify accountable owners and stewards
• Assess quality, lineage, classifications and known limitations
• Understand sensitivity and handling requirements
• Request appropriate access through a clear route
• Decide whether the data is suitable for their purpose

The Objective

The goal is not simply to catalogue more technical assets.

The goal is to make organisational data easier to find, understand, govern and trust.

An effective Enterprise Data Catalogue gives Data Consumers a clearer route from a business question to governed, understandable and reusable data.