Creating, Scheduling and Monitoring Data Map Scans

After a source is registered, Microsoft Purview can scan it to capture technical metadata, extract supported schema information and apply classifications.

Create the scan

Configure the source-specific connection, credential, integration runtime, scope and scan rule set required by the connector.

Choose the trigger

Scans can be run once or scheduled. The appropriate frequency should reflect how quickly the source changes and how current the catalogue needs to be.

Monitor operations

• Review scan status and scan history.
• Confirm the expected assets were ingested.
• Investigate failed or partial scans.
• Review authentication, network and source permissions when scans fail.
• Rerun or adjust scope when necessary.

Scanning is an operational process rather than a one-off implementation task. The responsible technical team should make sure scans continue to represent the real data estate over time.