Hi @szymon_dybczak ,

We confirmed that it is indeed the backbone network that is causing the issue as we fetched the logs of the sftp
Databricks --> SFTP (region outside Europe West) = Public IP NAT gateway
Databricks --> SFTP (region Europe West) = Private IP

Currently in contact with Microsoft support to overrule this backbone network. I tried to define a route table with 

Unfortunately this also not works. Any idea maybe?

Hi @Kenji_3000 ,

Thanks for info. I must admit that you guys stumble upon really interesting scenario. In my opinion, defining UDR should override this default behaviour. What could prevent it from working as expected is routing preference of public address IP associated with NAT Gateway. 
Could you check how properties of NAT Gateway public IP looks like? Probably you have configured it like below.

It seems to me that if your gateway had "Internet" routing set instead of "Microsoft", it would have worked.
But as I said, I'm more data enginneer who sometimes needs to figure out networking issue, so take my word with a pinch of salt 🙂

Configure routing preference for a public IP address | Microsoft Learn

Hi @szymon_dybczak , 

Thanks for the suggestion. I tried to attach the ip address to the NAT but it requires a NAT also to have an internet routing preference and Azure doesn't allow that. Quite a unique scenario indeed. We have created a workaround now of a seperate VM in germanywest that writes it to the SFTP server. Let's see if we can come up with a more "elegant" solution in the future!

Hi @Kenji_3000 ,

Thanks @Kenji_3000  for sharing workaround, really appreciate that. This is definitely one of the most interesting scenarios I've seen so far on community. If you come up with something else or receive some tips form MS let us know.