Azure Synapse Analytics Access Pattern
Audience: System Administrators
Content Summary: This page describes the Dynamic Azure Synapse Analytics access pattern, through which Immuta applies policies directly in Azure Synapse Analytics.
For a tutorial on configuring Azure Synapse Analytics see the App Settings page.
The Dynamic Azure Synapse Analytics access pattern allows Immuta to apply policies directly in Azure Synapse Analytics dedicated SQL pools without the need for users to go through the Immuta Query Engine. Users can work within their existing Synapse Studio and have per-user policies dynamically applied at query time.
Data sources are represented by views; because they are under one schema instead of a database, their view name will be a combination of their schema and table name, separated by an underscore.
Example: With a configuration that uses
IMMUTA as the native schema in the database
dedicated_pool, the view
name for the data source
dedicated_pool.tpc.case would be
You can see the view information from the data source health check.
Syncing and Policy Enforcement
This access pattern leverages webhooks to keep the views up-to-date with the corresponding Immuta data sources. When a data source or policy is created, updated, or disabled, a webhook will be called that will create, modify, or delete the dynamic view. Note that only standard views are available because Azure Synapse Analytics dedicated SQL pools do not support secure views.
immuta_system.user_profile view uses the constraint
UPPER(immuta__userid) = UPPER(SYSTEM_USER) to ensure only
the profile of the current user is returned.
The native integration will create views from the tables contained within the database specified upon configuration.
Then, the user can configure the schema name
where all the Immuta generated views will reside. Immuta will also create the schemas
immuta_procedures to contain the tables, views, UDFs, and stored procedures that support
the native integration.
Since Azure Synapse Analytics dedicated SQL pools do not support array or hash objects, certain user access information is stored as delimited strings; those delimiters can be modified to ensure they do not conflict with possible characters in strings.
For a full tutorial on configuring Azure Synapse Analytics see the App Settings page.
Immuta does not support the following masking types in this native access pattern because of limitations with dedicated SQL pools. Any column assigned one of these masking types will be masked to NULL:
- Reversible masking
- Format Preserving Masking
The delimiters configured when enabling the native integration cannot be changed once they are set. To change the delimiters, the native 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.