VS Logic Apps: SQl conenction using Gateway not deployable

Raminder Chima 41

Hi,
I am using VS2019 to develop Logic Apps. I need to connect to On-Premise SQL server for SQL Task. I am using Gateway to configure the connection.
Whenever I deploy the Logic App to Azure, the connection does not work. I have to delete and recreate it. I have tried specifying connection details during deployment manually as well as using parameter file.

Currently, due to this issue, I am forced to design Logic Apps in Azure designer which is less then ideal.

Thanks for the help in advance.

Pramod Valavala 20,511 Reputation points Microsoft Employee

2021-03-01T15:56:05.327+00:00

@Raminder Chima Could you share details on the error that you see post deployment? Also, could you confirm the API Connection is deployed along with the Logic App?

Another option could be to simply re-authorize the API Connection which is just required once as you could just redeploy the Logic App alone the next time around.
Raminder Chima 41 Reputation points

2021-03-01T16:06:55.05+00:00

I can see that SQL connection get created in Azure through VS and is active when logic app is designed. It's only when logic app is deployed, the connection bit goes wrong. This does not happen with Azure database connection. I think, when Logic App is getting deployed, specifying connection details during deployment, may create an issue.
Can't Re-Authorize as the connection instance in Azure becomes unusable. So, I have to manually recreate the connection in azure and modify Logic App to use new instance.
Pramod Valavala 20,511 Reputation points Microsoft Employee

2021-03-01T16:22:03.513+00:00

@Raminder Chima Yes. I believe the deploy does try replacing all resources part of the template. You could ensure the parameters are set correctly locally as well to ensure deployments are clean OR you could just comment out the API Connection locally while developing.
Raminder Chima 41 Reputation points

2021-03-07T09:17:16.747+00:00

Yes, It is a deployment from VS using template and parameter file.
If a SQL task is included, during deployment, the connection details need to be specified, which are exactly similar to design time connection details.
Issue is that on the Azure instance, the created connection during design time is getting modified, resulting invalidity. I have to remove and recreate the connection manually.
Earlier, I have created a separate Logic App for connection only for each database, which I create in azure and then I can use it in other Logic app. Though it is a good idea but ideally it creates unnecessarily extra hop.
Azure connection works fine from VS 2019, it's only on-premise connection using gateway.

Accepted answer

Pramod Valavala 20,511 Reputation points Microsoft Employee

2021-03-09T17:46:07.483+00:00
@Raminder Chima I've tried this out and looks like the ARM Template generated doesn't have the gateway and authType set for the API Connection resources.

As described in this blog, adding a value like this under parameterValues should do the trick

"authType": "basic", "gateway": { "id": "/subscriptions/{{subscriptionId}}/resourceGroups/{{reosurceGroupName}}/providers/Microsoft.Web/connectionGateways/{{On-Premise DatagatewayName}}" }
Please sign in to rate this answer.
Raminder Chima 41 Reputation points

2021-03-13T13:36:41.21+00:00

Hi,
A quick query. How do we use this with Devops where the resourcegroup or subscription or gateway may vary?
defining resourcegroupname, Subscription and gatewayname in parameter file does not work during release pipeline config as it is not considered as part of template.

Thanks in advance.

Regards,

Pramod Valavala 20,511 Reputation points Microsoft Employee

2021-03-15T09:34:16.603+00:00

Instead of a parameter file, these values should be passed from the release pipeline through variables.

Raminder Chima 41 Reputation points

2021-03-15T11:11:34.14+00:00

Yes, I managed with few hiccups initially.
Sign in to comment

VS Logic Apps: SQl conenction using Gateway not deployable

0 additional answers