Custom DNS domain mapping for Synapse Analytics serverless endpoint

Question

How to set a Custom DNS domain mapping for Synapse Analytics serverless endpoint

I am currently connecting from Power BI using the serverless SQL endpoint: xxx-test-01-ondemand.sql.azuresynapse.net. I need to map this domain to a custom domain like db01.xxxxx.com.

Is it possible to achieve this? The intention is to be able to change the backend whenever required without needing to update the connection string in Power BI.

Answer 1

As of now, Azure Synapse Analytics serverless SQL endpoints do not natively support custom DNS domain mapping directly in the platform settings. However, you can achieve similar functionality by using one of the following approaches:

1. Azure Front Door with Custom Domains

• Azure Front Door provides the ability to map custom domains to backend services like Synapse Analytics endpoints. By setting up a custom domain in Front Door, you can point your custom domain (e.g., db01.xxxxx.com) to the serverless SQL endpoint.
• Steps:
  1. Create an Azure Front Door instance.
  2. Configure your Synapse Analytics serverless endpoint (xxx-test-01-ondemand.sql.azuresynapse.net) as a backend for Front Door.
  3. Map your custom domain (e.g., db01.xxxxx.com) in Front Door's configuration.
  4. Ensure SSL termination and routing rules are set up correctly to forward traffic to the Synapse endpoint.
  5. Update your DNS settings for your custom domain to point to the Azure Front Door endpoint.

2. Azure Application Gateway

• Similar to Front Door, Azure Application Gateway allows you to create a custom domain and route traffic to specific backends like your Synapse serverless endpoint.
  • This can be a more feature-rich solution if you need advanced routing or security features such as Web Application Firewall (WAF).

3. DNS A or CNAME Record with Proxy

• If you have a proxy setup or a load balancer, you could create a DNS CNAME or A record for your custom domain pointing to a reverse proxy. The proxy can route the traffic to the Synapse endpoint.
  • This approach gives you flexibility over the backend without changing Power BI connection strings, but you'll need to manage the proxy.

Considerations:

• Ensure your SSL certificates are correctly configured for the custom domain to prevent security issues.
• Any custom domain routing must preserve the connection type and security context, especially if you are using SQL authentication or managed identities.

This method will allow you to maintain a consistent domain (db01.xxxxx.com) and change the backend Synapse endpoint whenever required, avoiding updates in Power BI connection strings.