ADF Azure Hosted Integration Runtime IP Whitelist to access Synapse SQL Pool

Question

I am attempting to connect my ADF with a synapse pool, both resources sit in different subscriptions. My ADFis using an azure hosted IR in UK South region.
I have whitelisted the UK SOUTH ADF IR IP ranges as per below from this doc
https://learn.microsoft.com/en-gb/azure/data-factory/azure-integration-runtime-ip-addresses?WT.mc_id=Portal-Microsoft_Azure_Support
:

however when i attempt to connect to the Synapse pool in adf i am still getting network related error message:

Cannot connect to SQL Database. Please contact SQL server team for further support. Server: 'server.syn01.sql.azuresynapse.net', Database: 'pool01', User: ''. Check the linked service configuration is correct, and make sure the SQL Database firewall allows the integration runtime to access.
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server), SqlErrorNumber=53,Class=20,State=0,
The network path was not found
Activity ID: de33a3ee-99f5-4056-9945-816cb7582ef3.

----------

"Allow Azure services and resources to access this workspace" has been checked

Answer 1

Hello @WZIAFP ,

Welcome to the MS Q&A platform.

Please correct me If my understanding is wrong. Your ADF with synapse linked service connection is failing when using an Azure hosted IR in UK south region even though you have whitelisted the UK South Data factory IP addresses.

I am assuming your data factory, 'synapse pool' and Azure IR are in the same region which is South UK region.

Fix: Please create an Azure IR in a different region other than the ADF region and whitelist the IP addresses of the data factory (of that new region) to resolve the issue.

Ex: Datafactory is in East US, Synapse is in East US then if you create the Azure IR in East US then you will see the connection issue.

In this case, creating Azure IR other than East US (ex: Canada east), will work.

A similar issue has been discussed here by TechBorhtersIT

I hope this helps. Please let me know if you have any further questions.

------------------------------

• Please don't forget to click on or upvote button whenever the information provided helps you. Original posters help the community find answers faster by identifying the correct answer. Here is how
• Want a reminder to come back and check responses? Here is how to subscribe to a notification
• If you are interested in joining the VM program and help shape the future of Q&A: Here is how you can be part of Q&A Volunteer Moderators