Explanation
When Integration Runtimes are configured with the default "Auto Resolve" region setting, Azure may automatically provision them in a region different from the data sources or sinks. For example, an environment deployed in West Europe may run pipelines in US East. This causes unnecessary cross-region data transfer, increasing networking costs and pipeline latency. The inefficiency often goes unnoticed because data transfer costs are billed separately from pipeline compute charges.
Relevant Billing Model
ADF billing includes charges for pipeline activity runs, data movement, and Integration Runtime compute. Data transferred between Azure regions incurs additional network egress costs, which can exceed compute costs when workloads are large or frequent.
Detection
- Review Integration Runtime configurations and confirm their assigned regions
- Identify data movements that cross Azure region boundaries (e.g., West Europe to US East)
- Correlate pipeline-level data movement costs with Integration Runtime region assignments
- Assess whether "Auto Resolve" settings are active in environments that have regionally constrained data sources
Remediation
- Explicitly configure Integration Runtimes to run in the same region as the data sources and targets
- Avoid the "Auto Resolve" setting unless cross-region data processing is intentional
- Establish governance to enforce region alignment across ADF environments
- Regularly review Data Factory cost breakdowns to ensure network charges align with expected data movement patterns