> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dqlabs.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Azure Synapse FAQ

> Common questions about the Azure Synapse connector.

## Connector Lifecycle

> **What happens if I delete a connector?**
>
> Deleting a source triggers an approval workflow based on your organization's settings. Once approved, the source and all associated metadata are permanently deleted. The deletion cannot be undone after approval.

> **What happens to existing data and alerts if a connector is paused or disconnected?**
>
> Existing metadata, quality scores, and alerts are retained while the connector is inactive. No new data is collected until the connector is re-enabled. If the connector is permanently deleted (after approval), all associated data is removed.

## Azure Synapse-Specific

> **Does Prizm change anything in Synapse?**
>
> No. The connector is read-only. Quality exceptions are written to an Iceberg table, never back to Synapse.

> **Which parts of Synapse can I connect?**
>
> Dedicated SQL pools, Serverless SQL (including external and Delta tables), and Synapse Pipelines. One Prizm source covers one workspace, and you turn on only the surfaces you want.

> **Which authentication types are supported?**
>
> Service principal with a client secret, service principal with a certificate, managed identity (when Prizm runs on Azure), and SQL authentication for Dedicated pools only. Credentials can also come from a vault.

> **What permissions does Prizm need?**
>
> On Dedicated pools: `db_datareader`, `VIEW DEFINITION`, and `VIEW DATABASE STATE`. On Serverless: a login with `VIEW ANY DATABASE`, then `db_datareader` and `VIEW DEFINITION` in each database. For pipelines: the Synapse Artifact User and Synapse Monitoring Operator roles in Synapse Studio. The Azure Reader role discovers workspaces, and Storage Blob Data Reader covers external table storage. See [Setup](/sources/synapse/setup#required-permissions).

> **Can I catalog without letting Prizm read my data?**
>
> Yes. If you leave out `db_datareader`, Prizm can still catalog, track lineage, and read usage, but it can't profile data or run quality checks.

> **Why was my Dedicated pool skipped?**
>
> The pool was paused. Prizm reports a paused pool and skips it, and never resumes it. Resume the pool and the next run picks it up.

> **Why is freshness approximate on Dedicated pools?**
>
> Dedicated pools have no native last-modified time, so Prizm compares row-count snapshots between runs to detect changes.

> **Why are my pipelines not listed even though the connection is valid?**
>
> Pipeline access uses Synapse RBAC roles, assigned in Synapse Studio, not the Azure portal. Azure Owner or Contributor doesn't include them. Assign **Synapse Artifact User** and **Synapse Monitoring Operator**.

> **Does the connector report cost?**
>
> No. Cost management isn't part of the connector, and Prizm doesn't request cost permissions.

***

> **[Troubleshooting](/help/troubleshooting)**
>
> For connection errors, permission issues, and performance problems.

> **[Glossary](/help/glossary)**
>
> For definitions of terms used in this FAQ.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.