arrow-left

All pages
gitbookPowered by GitBook
1 of 1

Loading...

Azure Synapse Analytics Pre-Configuration Details

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.

hashtag
Feature availability

Project Workspaces

Query Audit

hashtag
Prerequisite

  • A running dedicated SQL pool

hashtag
Authentication methods

The Azure Synapse Analytics integration supports the following authentication methods to configure the integration and create data sources:

  • Username and password: Immuta supports SQL authentication with username and password for Azure Synapse Analytics. See the for details.

  • OAuth authentication with Microsoft Entra ID: You can use this authentication method to register data sources or configure the Azure Synapse Analytics integration using the . To use this authentication method, OAuth must be set up via . See the for details about using OAuth authentication with Microsoft Entra ID.

hashtag
Tag ingestion

Immuta cannot ingest tags from Synapse, but you can connect any of these to work with your integration.

hashtag
User impersonation

Impersonation allows users to query data as another Immuta user in Azure Synapse Analytics. To enable user impersonation, see the .

hashtag
Multiple integrations

A user can to a single Immuta tenant.

hashtag
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 .

    • 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 .

  • 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.

  • ❌

    ❌

    ✅

    ❌

    ✅

    SQL Authentication in Azure Synapse Analytics documentationarrow-up-right
    manual setup method
    Microsoft Entra ID app registration with a client secretarrow-up-right
    Microsoft Entra documentationarrow-up-right
    supported external catalogs
    Configure Azure Synapse Analytics integration guide
    configure multiple integrations of Synapse
    Synapse Documentation for detailsarrow-up-right
    Synapse Documentation for detailsarrow-up-right
    Tag Ingestion
    User Impersonation
    Synapse Documentation for detailsarrow-up-right
    Multiple Integrations