Data Governance... who, how, why?

This https://www.linkedin.com/feed/update/urn:li:activity:7412818351070027776 will provide you with an overview of Microsoft Purview Solutions. Purivew is not just one tool! 

Data Governance is typically owned by a central data or business-led function (such as a Data Office), with permissions and responsibilities clearly defined through role-based access so that policy setting, stewardship, and oversight are shared across business, IT, security, and compliance rather than sitting with a single technical team.

Its a multidisciplinary team.

There are a few personas within the Data Governance Purview Unified Catalogue.

• Data Consumers are individuals or teams who access and use data for reporting, analytics, operations, or decision-making, and are responsible for using that data!
• Data Owners are responsible for specific data products and, in most cases, also own the corresponding Microsoft Purview governance domains and Data Stewards (Purview defined, not DAMA)
• Data Architects and Data Governance professionals should be involved in defining and overseeing access and permissions, with all access enforced through RBAC (Role-Based Access Control) to ensure consistency, security, and compliance across the organisation.
• Finally, Data Custodians typically operate at the data map level, where they manage data map domains (usually up to five) and collections, register data sources, and oversee the scanning of Microsoft Purview data assets such as databases, tables, or files that sit within the defined data products.

Do not scan everything indiscriminately like it’s Pokémon; Microsoft Purview is not a data vacuum cleaner.

Scanning data assets without clear ownership simply creates a well-presented, beautiful chaos in your enterprise data catalogue within the unified Purview catalogue. - Get your Gov domains and ownership sorted first and ensure everybody understands what an EDC does