Discovery
Scans databases, schemas, tables, and columns using read-only `SELECT` access.
Ketch and Azure SQL Database
Find where personal data lives inside a managed SQL database, and fulfill deletion requests against it directly, using the same user lifecycle practices already in place.
About Azure SQL Database
Azure SQL Database runs relational workloads on Microsoft's managed platform, holding structured data across whatever tables and views an application has built up over time. Knowing exactly which of those tables and columns hold personal data, and being able to act on that directly, is the difference between a privacy program that can prove compliance and one that's guessing.
Ketch connects to Azure SQL Database through a Ketch Transponder to support both.
Capabilities
How Ketch works with Azure SQL Database
The Ketch Azure SQL Database integration covers Discovery and Rights Orchestration for both Right to Access and Right to Delete.
Rights Orchestration
Requires `UPDATE` and `DELETE` access granted on top of that, scoped to specific tables and columns. Ketch recommends managing the connected user through the organization's normal Azure SQL Database user lifecycle practices, rather than a special-case process outside standard administration.
With Ketch, teams can
- Discover which Azure SQL Database tables hold personal data using read-only access
- Grant rights-execution privileges separately from Discovery, deciding independently whether and when to authorize direct deletion and update
- Manage the Ketch user through standard Azure SQL Database administration practices
The gap
The problem this integration solves
A managed relational database still needs its personal data actually located and acted on, not just assumed to be somewhere in a known set of tables:
01. Manually reviewing table schemas to confirm where personal data lives doesn't scale and goes stale as schemas change
02. Fulfilling a deletion request against a database has historically meant a manually written query, slow and hard to prove complete
03. Granting broad write access to any tool touching production data is a real risk independent of the privacy use case
Ketch resolves this by separating discovery from execution as two distinct privilege grants, so an organization gets accurate visibility immediately and decides separately whether to authorize direct execution.
Why Ketch
Why teams choose Ketch for Azure SQL Database privacy compliance
Permissioning infrastructure that governs Azure SQL Database the same way it governs every other system in your stack — not a one-off connector bolted onto a banner.
Fits standard Azure administration
The Ketch user can be managed through normal Azure SQL Database user lifecycle practices.
Backed by enforcement precedent
Regulators increasingly expect businesses to prove technical enforcement, not just describe it on paper, the same underlying expectation that applies to knowing what personal data a database holds.
Questions about the Azure SQL Database integration
Related reading
Expert insights for teams connecting Azure SQL Database
Integrations
Pre-built APIs with 1,000+ systems, apps, and models
Ketch ships connectors and SDKs so consent, rights, and policy flow into your CDPs, warehouses, ad platforms, and AI stack — without a custom data pipeline.
See Azure SQL Database permissioning running end to end
Book a demo to walk through rights, consent, and preference orchestration on your stack — or start free and connect Azure SQL Database yourself.
Get Started Free
Get started in less than 5 min