Why Connect Azure Synapse to Prizm?
Catalog & Context Prizm discovers the databases, schemas, tables, views, and columns in your Dedicated and Serverless SQL pools, along with distribution, index, and key details on Dedicated pools. Data Quality Structural, business, lookup, behavioral, and conditional quality checks run on your own Synapse compute, and failing records are written to an Iceberg table rather than back to Synapse. Observability Volume, freshness, and schema changes are tracked for every cataloged table, alongside query performance for your pools. Pipelines Prizm catalogs Synapse pipelines, activities, triggers, and data flows, and monitors run status, duration, and failures. Lineage & Criticality Prizm derives table-level lineage from pipeline definitions, view definitions, foreign keys, external tables, and CTAS/CETAS statements, and scores each table’s criticality.Compute Surfaces
The connection form lets you choose which surfaces Prizm covers. Each has its own prerequisites, so grant access only for the ones you select.Authentication
Turn on Use Vault to retrieve credentials from a vault instead of entering them. See Setup for the permissions each type needs.
Current Scope
The connector is read-only. Some items are limited today:- Cost management (DWU, bytes scanned, and similar) isn’t part of the connector, and Prizm doesn’t request cost permissions.
- A paused Dedicated pool is reported as paused and skipped. Prizm never resumes it.
- Lineage is table-level. Column-level lineage and deep notebook or Spark code parsing aren’t covered.
- Dedicated pool freshness is approximate, because Dedicated pools have no native last-modified time. See What We Collect.
Next Steps
Setup
Grant permissions and connect your Synapse workspace.
What We Collect
The metadata, signals, and lineage Prizm extracts.
FAQ
Common questions about the Synapse connector.
Troubleshooting
Diagnose connection, permission, and performance errors.