Azure Function unable to connect to Azure SQL Database

Question

Hi All,

I am having an issue connecting to an Azure database from an Azure Function. Please see screen grab below of the function (I will be updating it to use AD soon!).

The weird thing is, is that it has worked in the past. This is to save data from an IoT hub into the database. It worked when I was using LORIOT as the LoRaWAN provider, however I have switched to The Things Network (TTN) and so have had to edit the Azure function as TTN provides payload formatter, where as LORIOT did not. So I could remove the decoder from the Azure function. As you can see from the screen grab below, the data from the IoT-Hub is being received and logged. I honestly did not expect saving to the DB to be an issue, but as you can see I am getting the error shown below which shows that it is failing when trying to connect:

I have checked the credentials (as mentioned - they are unchanged from when it was working) and I have checked that the DB has status = Online and have checked that my client IPv4 address has been added to the DB firewall.

Does anyway have any idea as to the issue?

Answer 1

Could you please add the following to the connection string?

;Encrypt=yes;TrustServerCertificate=no;Connection Timeout=30;'  

Make sure you allow Azure Services to access your Azure SQL Database. Make sure you have below setting enabled on Azure SQL firewall.

Answer 2

Thank you for your response Alberto. I had already added the client IP address to the firewall rules.

I have added to the connection string that which you suggested, but done it like this:

However I believe I am getting the same error:
]3

Answer 3

Hi @Alberto Morillo I have had this option enabled since the start of setting this up. As mentioned, this DB has worked with the existing Azure Function and the save function within the init.py file was unchanged.

Going to be looking into this more today.

Answer 4

So the infrastructure team got involved and added my client IP address to the firewall and now it seems to work. The error that I was seeing when deployed to Azure was an error on the code that was quickly sorted. This is weird as the Infrastructure team swears blind that my client IP was not added previously so we do not know why it worked in the passed. Either way, it is all working as expected now so all good. @Alberto Morillo ; thanks for your time on this!