Microsoft Purview · Data Map Collections

Data Curator

Manage assets, create classifications, build glossary terms, and curate data catalog metadata for improved discoverability and understanding.

Scope: Collections where assigned as Data Curator (with inheritance to subcollections)

Permissions

  • Create, read, modify, move, and delete data assets in collections
  • Configure custom classifications and classification rules
  • Create and manage business glossary terms and relationships
  • Apply annotations, descriptions, and metadata to assets
  • Curate and certify data assets for quality assurance
  • View Data Estate Insights and analytics
  • Manage asset lineage and relationships
  • Apply sensitivity labels and classifications to assets
  • Create and edit asset schemas and column-level metadata
  • Manage asset ownership and expert contacts

Common use cases

  • Building business glossary with standardized terminology and definitions
  • Classifying data assets with PII, financial, or confidential tags
  • Enriching asset metadata with business context and descriptions
  • Certifying trusted data assets for analytical use
  • Creating data lineage documentation for impact analysis
  • Managing data quality annotations and trusted data sources
  • Coordinating with data owners to capture institutional knowledge
  • Implementing data governance policies through metadata enrichment

Best practices

  • Coordinate with business stakeholders to capture accurate business context
  • Establish consistent glossary term naming and definition standards
  • Document classification rationale and apply classifications consistently
  • Certify assets only after thorough quality validation
  • Maintain active communication with data owners and subject matter experts
  • Use hierarchical glossary structure for related terms
  • Apply both technical and business metadata to assets
  • Regular review and updates of asset metadata as data evolves
  • Leverage AI-powered classification suggestions but validate manually
  • Coordinate with Information Protection Admins on sensitivity label usage

Security considerations

  • Can modify and delete assets in assigned collections
  • Classification changes can affect DLP policies and access controls
  • Incorrect metadata can mislead data consumers and analysts
  • Sensitivity label application affects information protection enforcement
  • Asset deletion is permanent and may impact downstream dependencies
  • Changes are logged in audit history for accountability

Official Microsoft Learn documentation →

Open the interactive RBACMap →