Auto Resolve Integration Runtime is starting in US region even though Source and Sink are in Australia region. This has increased the bill drastically. How to correct it?

Question

We have create a Azure Synapse Pipeline which is connecting to source Business Central hosted in Australia and ingesting data into sink Data Lake Storage which is also hosted in Australia region.

But Auto Resolve Integration Runtime is starting in US Region. How to get this bill corrected as the invoice is high?

Answer 1

Hi @DataLake Admin
 

When you use AutoResolveIntegrationRuntime, Azure tries to pick a compute location close to the data store. It’s not guaranteed to match your workspace region—it follows internal placement rules and sometimes defaults to another region (like the US) if certain connectors or capacity constraints apply. For SaaS sources like Business Central, which are globally routed, AutoResolve can easily choose a different region.

How to fix it going forward

If you want to keep costs down and avoid cross-region charges, don’t rely on AutoResolve. Instead:

Create a dedicated Integration Runtime in Australia

  - In Synapse Studio, go to Manage → Integration runtimes → + New → Azure, and set the region to Australia East or Australia Southeast (whichever matches your Data Lake).
  
     - Publish the IR.
     

CLI example:

PowerShell

Set-AzDataFactoryV2IntegrationRuntime `

-DataFactoryName "YourFactory" `

-ResourceGroupName "YourRG" `

-Name "IR-AustraliaEast" `

-Type Managed `

 

Update all linked services for every source, sink, and staging account, set Connect via to the new IR. This ensures the pipeline uses the correct region for all activities.

Example JSON snippet:

JSON

"connectVia": {

"referenceName": "IR-AustraliaEast",

"type": "IntegrationRuntimeReference"

}

Check staging settings If you use PolyBase or temporary staging, make sure the staging storage account is also in Australia and linked to the same IR.

Optional: Self-hosted IR If you need full control or private networking, deploy a Self-hosted IR on a VM in Australia and route both source and sink through it.

Verify the change

Run a test pipeline and check the Activity run details. Look for effectiveIntegrationRuntime—it should show your new IR and the Australia region.

Why your bill spiked

Cross-region data movement adds bandwidth charges per GB. When compute runs in the US and your data is in Australia, you pay for that transfer plus extra runtime costs. Keeping everything in the same region eliminates those charges.

Double-check Business Central

Confirm your Business Central environment is actually hosted in Australia. You can verify this in the Business Central Admin Center.

About the invoice

Microsoft usually doesn’t retroactively adjust charges for configuration issues, but you can open a billing support request in the Azure portal. Include:

• Subscription ID and invoice number
• Activity run IDs showing the US region
• A short explanation of what happened and what you’ve done to fix it

They may offer a courtesy credit if AutoResolve behaved unexpectedly.

Quick checklist

• Create IR in Australia
• Update all linked services to use it
• Republish and test
• Confirm BC region
• Contact billing support if needed

References

• https://learn.microsoft.com/azure/data-factory/concepts-integration-runtime
• https://learn.microsoft.com/azure/data-factory/create-azure-integration-runtime