App could not could not connect to Azure Synapse when created via ARM template - SSL connection could not be established

Xhevahir Mehalla 160 Reputation points
2024-06-21T07:56:17.4333333+00:00

Hello.

I need your help with smth that we find a difficult to resolve.

Here's the current setup:

  1. I have created an Azure Synapse workspace using ARM templates. All is working well apart from when an App which has been build on Angular could not connect to Synapse workspace using dedicated endpoint I have created an Azure Synapse workspace using ARM templates. All is working well apart from when an App which has been build on Angular could not connect to Synapse workspace using dedicated endpoint https://sa-wkspace-fa-dev.dev.azuresynapse.net The error message is something to do with the certificate: "The SSL connection could not be established, see inner exception. The remote certificate is invalid according to the validation procedure: RemoteCertificateNameMismatch"
  2. When I create the Synapse workspace using the portal this works fine, We can connect to synapse workspace. Not sure what we missing from the script. We export the synapse workspace and create via script it does not work. Is a different name (workspace).
  3. When we need to be able to automate this hence need to figure out why it doesn't work via ARM templates.

Appreciate your help!

Thanks

Xhev

Azure Synapse Analytics
Azure Synapse Analytics
An Azure analytics service that brings together data integration, enterprise data warehousing, and big data analytics. Previously known as Azure SQL Data Warehouse.
4,613 questions
Azure App Service
Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
7,260 questions
Accepted answer
  1. Smaran Thoomu 12,090 Reputation points Microsoft Vendor
    2024-06-21T09:57:30.7166667+00:00

    Hi @Xhevahir Mehalla

    Thank you for reaching out to us with your query.

    Based on the error message you provided, indicates an issue with the SSL certificate validation process when your Angular app tries to connect to the Azure Synapse workspace using the dedicated endpoint.
    To resolve this issue, you can try the following steps:1. Double-check the ARM template section where you define the dedicated endpoint for your Synapse workspace. Ensure there are no typos or incorrect references to certificate names.

    1. Make sure the template creates the dedicated endpoint with a valid certificate. If using a self-signed certificate, you might need to install it as a trusted certificate on the machine running the Angular app.
    2. Verify that your Angular app is configured to trust the specific certificate used by the Synapse workspace's dedicated endpoint. This might involve adding the certificate to the app's trusted certificate store.
    3. Some frameworks might have options to bypass certificate validation for development purposes. Ensure such settings are not enabled in production.
    4. Carefully compare the ARM template configuration for the dedicated endpoint with the steps you follow when creating the workspace manually through the Azure portal. Look for any discrepancies in certificate settings.
    5. Ensure there are no firewall restrictions blocking communication between your Angular app and the Synapse workspace endpoint. Verify that ports necessary for HTTPS traffic are open.

    If the issue persists, please provide more details about the ARM template you are using to create the Synapse workspace.

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

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest