Cosmos DB copy in ADF comes from two regions instead of one region

Salomon Henriquez 106 Reputation points Microsoft Employee
2024-06-25T22:30:57.58+00:00

I have one ADF instance in West US region and I have a Cosmos DB in East US.

When running a copy activity in ADF from Cosmos to Azure SQL, I see the copy comes from East US and West US regions. The copy should come just from East US.
Could this beavior be caused beuase of the location of the ADF?

Azure Cosmos DB
Azure Cosmos DB
An Azure NoSQL database service for app development.
1,518 questions
Azure Data Factory
Azure Data Factory
An Azure service for ingesting, preparing, and transforming data at scale.
10,012 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Harishga 5,590 Reputation points Microsoft Vendor
    2024-06-26T04:52:25.71+00:00

    Hi @Salomon Henriquez
    Welcome to Microsoft Q&A platform and thanks for posting your question here.

    When you run a copy activity in Azure Data Factory from Cosmos DB to Azure SQL, you expect the data to move only within the East US region. However, if you’re seeing the activity also in the West US region, it’s likely because of how the Integration Runtime is set up. The IR is what moves the data, and it can use resources from different regions.

    If your IR isn’t specifically set to use the East US, it automatically uses resources from both the East and West US. This can happen even if your data stores are in just one region. Also, your network setup, like your Azure Virtual Network, can change the path of the data movement. Plus, if you’re using a self-hosted IR, it needs to be able to reach both the source (Cosmos DB) and the destination (Azure SQL).

    To fix this, you should check your IR settings in ADF. Make sure it’s set to use resources mostly in the East US. This way, you can avoid moving data across regions.

    I hope this information helps you. Let me know if you have any further questions or concerns.

    0 comments