I'm trying to get my data flow pipeline to connect to a Snowflake instance, but it's failing because the Azure Integration Runtime (AIR) locked to a specific region is using IP addresses that aren't listed in the allowed range for that region. I've checked the Microsoft documentation stating that all AIRs in the same region share the same IP address ranges. However, my AIR seems to be pulling random IPs. If this is expected behavior and the only way to ensure a static IP is through a VNET, I feel that Microsoft needs to update their documentation since it contradicts my experience. Has anyone had similar issues or can provide insight?
2 Answers
You should check out the Azure IP Addresses documentation; Microsoft provides a JSON file showing all egress IPs for each service by region. If you need dependable traffic through a VNet, consider using a self-hosted integration runtime instead.
Have you thought about creating a brand new Azure integration runtime? You can still have it managed for you while selecting the specific region—this should ensure that the IPs align with what’s expected.
I appreciate the suggestion, but I’ve already set up a dedicated AIR in the correct region, so that's not the issue.
I get that, but I’ve already gone through that documentation and whitelisted all the IP blocks for my specific region. The AIR is still using IPs that aren’t in those blocks.