Forum Discussion
Problem with Azure Data Factory IP-Range changing overnight
- Anonymous1 year ago
Hi marius1106 ,
Azure Data Factory's integrated runtime IP addresses change without a fixed schedule, so predicting when these changes will occur is not very simple. However, I think you can try the following and check the official documentation below.
1. If possible, consider using a Managed Virtual Network in Azure Data Factory. This can help provide more stable IP addresses for your data flows.
Here is a document I think you can read:
Azure Integration Runtime IP addresses - Azure Data Factory | Microsoft Learn
2. Utilize Azure Service Tags to simplify network security rule management. Service tags represent a group of IP address prefixes from a specific Azure service, and Microsoft manages the address prefixes encompassed by the service tag and automatically updates the service tag as addresses change.
I think you can also look at this document:
3. Since there's no guaranteed time for IP address changes, you might want to schedule your pipeline to run multiple times throughout the day to increase the chances of successful execution.
Best Regards
Yilong Zhou
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi marius1106 ,
Azure Data Factory's integrated runtime IP addresses change without a fixed schedule, so predicting when these changes will occur is not very simple. However, I think you can try the following and check the official documentation below.
1. If possible, consider using a Managed Virtual Network in Azure Data Factory. This can help provide more stable IP addresses for your data flows.
Here is a document I think you can read:
Azure Integration Runtime IP addresses - Azure Data Factory | Microsoft Learn
2. Utilize Azure Service Tags to simplify network security rule management. Service tags represent a group of IP address prefixes from a specific Azure service, and Microsoft manages the address prefixes encompassed by the service tag and automatically updates the service tag as addresses change.
I think you can also look at this document:
3. Since there's no guaranteed time for IP address changes, you might want to schedule your pipeline to run multiple times throughout the day to increase the chances of successful execution.
Best Regards
Yilong Zhou
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.