Logic App Error (Error all of a sudden ocurred after a year of successful run-time): "Cannot open server 'x.x.x.x' requested by the login. Client with IP address 'x.x.x.x' is not allowed to access the server?"

Question

Logic App Error (Error all of a sudden ocurred after a year of successful run-time): "Cannot open server 'x.x.x.x' requested by the login. Client with IP address 'x.x.x.x' is not allowed to access the server?"

ED 41

I encountered an error in Microsoft Azure Logic Apps Connectors, which says "Cannot open server 'x.x.x.x' requested by the login. Client with IP address '13.77.55.161' is not allowed to access the server". This error suddenly occurred after a year of successful run-time. What could be the possible reasons for this error? Any updates or modifications to the Logic App Connectors that may have caused this error?

Accepted answer

0 additional answers

Your answer

Answer 1

MayankBargali-MSFT 70,941 Moderator

@ED Thanks for reaching out and apology for the inconvenience due to this issue. As per the IP address 13.77.55.161 belongs to Australia Southeast region and is listed as the outbound IP addresses as documented here.

This 13.77.55.160 - 13.77.55.191 range was added and On 6/17/2020 we have emailed the subscription owners and administrators about upcoming IP address changes for Azure Logic Apps as documented here.

It looks like the IP address was not updated or added when the notification was sent to the subscription owners and administrators. You can refer to this document and validate if all the IP address are added for Australia Southeast region.

Alternative I will suggest you to leverage the service tags wherever possible rather than outbound IP address if you are communicating to Azure resources so you should not face this type of issue. In case if you are connecting to on premise resources then your admin and subscription owner should review the notification emails and you can always validate the updated list from here.

Let me know if you have any queries or concerns.

ED 41 Reputation points

2023-06-12T20:53:26.2166667+00:00

Thanks @MayankBargali-MSFT for that. I see that those IP addresses were added but I can't see that something was deleted though. If I am correct, this was the IP address that we were using 13.70.136.174 which didn't work anymore last Mar 2023. I can still see that IP as a connector. We use this for our SQL Server. Anything else that changed?

Noted on the service tags. We will probably use this to our upcoming projects. At the moment, we just want an answer to the issue that we encountered.
MayankBargali-MSFT 70,941 Reputation points Moderator

2023-06-13T04:50:25.1433333+00:00

@ED Any of the Outbound IP addresses can be used to make to outbound call from the connector as listed here. It is not that only 13.70.136.174 IP will be used that will make the call to your SQL database. The request can come from any of the IPs to your SQL server.

As per your initial error I am sure that 13.77.55.161 was added at your SQL end. May be someone from your team have updated the IP address when they observe the issue post March 2023.

In case if you have the audit logs enabled for your Azure SQL Database then you can review them to validate when the IP address was added.
ED 41 Reputation points

2023-06-13T20:38:43.46+00:00

Hi @MayankBargali-MSFT , We've added the IP 13.77.55.161 last Mar 2023 because we were getting the "Cannot open server '13.77.55.161' requested by the login. Client with IP address '13.77.55.161' is not allowed to access the server?" error. The IP 13.70.136.174 is still there in the firewall settings during that time so if you are saying that ANY Outbound IP addresses can be used, we should not have encountered that error at all. The expectation is that it should still work because we have a valid Outbound IP Address, right? Am I missing something?
MayankBargali-MSFT 70,941 Reputation points Moderator

2023-06-14T07:40:19.3066667+00:00

@ED Let me explain it again. When you have restricted network and if your logic app workflow communicates with any services that are part of restricted network then you need to make sure that all the IPs that are listed in this document for your particular region should be whitelisted at your end. In your case as it was Azure SQL resource created on Australia Southeast region so you should whitelist all the IPs for the Australia Southeast region.

In case if there are any IP changes in future (addition/deletion) then you need to make sure that you are updating it at the firewall rule in your Azure SQL server end. In case if any IP are missed that are not whitelisted then you will get the error as you have shared in your initial question.

The IP 13.70.136.174 is still there in the firewall settings during that time so if you are saying that ANY Outbound IP addresses can be used, we should not have encountered that error at all.

It is not that only 13.70.136.174 IP will be used that will make the call to your SQL database. The request can come from any of the IPs of connector (you need to whitelist all IP's) from Australia Southeast region to your SQL server.

Hope the above clears things now. Let me know if you have any queries or concerns.
ED 41 Reputation points

2023-06-14T20:09:30.5466667+00:00

Hi @MayankBargali-MSFT , thanks for clarifying that I need to add ALL not just ONE. My assumption is that adding just one should work. You've been helpful. Thanks again.
MayankBargali-MSFT 70,941 Reputation points Moderator

2023-06-15T06:33:08.7833333+00:00

@ED Thanks for your kind words. Feel free to 'Accept Answer' so it can help other community members facing the similar issue.

Feel free to reach out to us in Microsoft QnA if you need any assistance in future.

Share via

Logic App Error (Error all of a sudden ocurred after a year of successful run-time): "Cannot open server 'x.x.x.x' requested by the login. Client with IP address 'x.x.x.x' is not allowed to access the server?"

0 additional answers

Your answer