DatriseAI-first ETL

Intruder to Azure Synapse Integration

AI-first ETL from Intruder into Azure Synapse. Governed entities, incremental sync, typed landing tables.

How Datrise loads Intruder into Azure Synapse

Datrise syncs Intruder's scans, issues, targets, severities, occurrences, and remediation statuses into Azure Synapse as a typed table per source entity. Flexible or custom fields land in NVARCHAR(MAX) JSON columns, and timestamps such as created, updated, and status changes are typed as datetime2.

Sync is incremental: Datrise uses COPY into staging, then a MERGE on stable id, so re-runs update only what changed. Hash distribution on the join id with date partitioning on facts. Synapse dedicated pools reward good hash-distribution choices, so Datrise distributes on entity ids to avoid data-movement-heavy joins.

Ideal for Azure analytics estates feeding Power BI.

Endpoints

Intruder: Continuous vulnerability scanning for internet assets.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How Intruder entities map to Azure Synapse

Intruder entityAzure Synapse objectNotes
scansintruder_scansid PK · custom fields → NVARCHAR(MAX) JSON columns
issuesintruder_issuesid PK · linked to intruder_scans
targetsintruder_targetsid PK · linked to intruder_scans
severitiesintruder_severitiesid PK · linked to intruder_scans

FAQ

How does Datrise handle Intruder's custom fields in Azure Synapse?

Flexible values are stored as NVARCHAR(MAX) JSON columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Azure Synapse types.

How does the Intruder to Azure Synapse sync stay up to date?

It runs incrementally — Datrise uses COPY into staging, then a MERGE on stable id.

Related pipelines

Early access

Connect Intruder to Azure Synapse the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.