Why Connect ADF to Prizm?
Pipeline Catalog Prizm discovers the pipelines, activities, data flows, notebooks, and stored procedures in your data factories, along with their triggers and schedules, and keeps the catalog current as pipelines are added, changed, or removed. Run Monitoring Prizm polls ADF for new pipeline and activity runs, so status, duration, retries, and failures are tracked without waiting for someone to open the ADF monitoring pane. Failure Detection When a run fails, Prizm records the error message, error code, and the activity that failed, and raises an alert. Pipeline Metrics Success rate, failure count, retry count, execution duration, last run, and pipeline status are available per pipeline alongside the rest of your Prizm pipeline sources.How ADF Maps to Prizm
Triggers and schedules are stored as schedule information on the job. Datasets and linked services are read for context but aren’t cataloged as assets of their own.
Authentication
ADF connections authenticate with a Microsoft Entra ID (Azure AD) identity. Choose one of three authentication types:
Turning on Use Vault for a service principal or certificate connection replaces the credential fields with a Select Vault dropdown and a Key field. See Setup for the full walkthrough and the Azure role the identity needs.
Current Scope
The connector is read-only and focuses on pipeline metadata, run history, failures, and metrics. Near-real-time event delivery through Azure Event Grid, circuit breaker data quality gates, and lineage-based root cause and impact analysis are separate capabilities, and their availability depends on your Prizm release. They aren’t covered here.Next Steps
Setup
Connect Azure Data Factory to Prizm — Azure permissions, authentication, and scope.
What We Collect
The pipeline metadata, run history, and metrics Prizm extracts.
FAQ
Common questions about the Azure Data Factory connector.
Troubleshooting
Diagnose connection, permission, and performance errors.