Azure Synapse Analytics Pre-Configuration Details
Last updated
Was this helpful?
Last updated
Was this helpful?
This page describes the Azure Synapse integration, configuration options, and features. See the for a tutorial on enabling the integration and these features through the App Settings page.
Project Workspaces
Query Audit
A running Dedicated SQL pool
The Azure Synapse Analytics integration supports the username and password authentication method to configure the integration and create data sources.
Immuta cannot ingest tags from Synapse, but you can connect any of these to work with your integration.
Impersonation allows users to query data as another Immuta user in Synapse. To enable user impersonation, see the page.
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:
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.
A user can to a single Immuta tenant.
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 .
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 .
Regex: The built in string replace function does not support full regex. See the .