Azure Synapse Pre-Configuration Details
Audience: System Administrators, Data Owners, and Data Users
Content Summary: This page describes the Azure Synapse integration, configuration options, and features.
See the Azure Synapse integration page for a tutorial on enabling the integration and these features through the App Settings page.
Feature Availability
| Project Workspaces | Tag Ingestion | User Impersonation | Native Query Audit | Multiple Integrations |
|---|---|---|---|---|
❌ | ❌ | ✅ | ❌ | ✅ |
Prerequisite
A running Dedicated SQL pool
Authentication Method
The Azure Synapse Analytics integration supports the following authentication method to install the integration and create data sources:
Username and Password: Users can authenticate with their Azure Synapse Analytics username and password.
Tag Ingestion
Immuta cannot ingest tags from Synapse, but you can connect any of these supported external catalogs to work with your integration.
User Impersonation
Impersonation allows users to query data as another Immuta user in Synapse. To enable user impersonation, see the User Impersonation page.
Multiple Integrations
A user can configure multiple integrations of Synapse to a single Immuta instance.
Limitations
Immuta does not support the following masking types in this integration because of limitations with Dedicated SQL pools (linked below). Any column assigned one of these masking types will be masked to NULL:
Reversible Masking: Synapse UDFs currently only support SQL, but Immuta needs to execute code (such as JavaScript or Python) to support this masking feature. See the Synapse Documentation for details.
Format Preserving Masking: Synapse UDFs currently only support SQL, but Immuta needs to execute code (such as JavaScript or Python) to support this masking feature. See the Synapse Documentation for details.
Regex: The built in string replace function does not support full regex. See the Synapse Documentation for details.
The delimiters configured when enabling the integration cannot be changed once they are set. To change the delimiters, the integration has to be disabled and re-enabled.
If the generated view name is more than 128 characters, then the view name is shortened to 128 characters. This could cause collisions between view names if the shortened version is the same for two different data sources.
For proper updates, the Dedicated SQL pools have to be running when changes are made to users or data sources in Immuta.
Last updated