What is the mechanism to implement SSL when connecting from a third party application or IPaas platforms to Azure Synapse database either in serverless sql pool or ded

Hi @Amit Chakraborty

Welcome to Microsoft Q&A platform and thanks for posting your question here.

To set up SSL/TLS encryption between an iPaaS platform and Azure Synapse Analytics, you need to make sure the connection is secure.

First, check that your iPaaS platform supports SSL/TLS encryption. Then, create an Azure Synapse Analytics workspace with either a serverless or dedicated SQL pool. Get the SSL/TLS certificate from the Azure portal by going to your Synapse workspace, clicking on the “Overview” tab, and copying the “ODBC” connection string, which includes the SSL/TLS certificate information. In your iPaaS platform, create a new connection to Azure Synapse Analytics, entering the server name, database name, username, and password. Enable SSL/TLS encryption and use the SSL/TLS certificate you obtained. Adjust any other SSL/TLS settings as needed.

Serverless vs. Dedicated SQL Pool Configuration

When connecting to a serverless SQL pool, include the Encrypt=True parameter in the connection string. The serverless SQL pool uses a default SSL/TLS certificate that Azure Synapse Analytics automatically generates, so you don’t need to provide a custom certificate. For dedicated SQL pools, also include the Encrypt=True parameter in the connection string. You can use either a custom SSL/TLS certificate or the default certificate generated by Azure Synapse Analytics. If you choose to use a custom certificate, upload it to the Azure Synapse Analytics workspace and configure the dedicated SQL pool to use it.

Differences Between Serverless and Dedicated SQL Pools

Serverless SQL Pool

Usage: Best for on-demand querying of data stored in Azure Data Lake without needing to set up resources in advance.

Configuration: No need to manage compute resources. Just connect using the serverless SQL endpoint.

Cost: Pay-per-query model, which can be cost-effective for infrequent queries.

Dedicated SQL Pool

Usage: Ideal for high-performance, large-scale data warehousing with provisioned resources.

Configuration: Requires managing compute resources and scaling based on workload.

Cost: Fixed cost based on the provisioned resources, which can be more predictable for consistent workloads.

Reference:
https://video2.skills-academy.com/en-us/azure/synapse-analytics/guidance/security-white-paper-data-protection

I hope this information helps you. Let me know if you have any further questions or concerns.