How can I connect my Linked Service to other cloud databases through a managed integration runtime (IR)?

Question

How can I connect my Linked Service to other cloud databases through a managed integration runtime (IR)?

Anonymous

Scenario: Azure Cosmos DB NoSQL migration to Huawei Cloud DDS, with Azure Data Factory replicating the active migration data.

The Azure public cloud IP range has been enabled in the security group of the target cloud database. My tag is DataFactory.EastUS. I confirmed that I used the Integration Runtime region of the Data Factory, which is displayed as East US.
However, since the target database has only enabled the IPv4 communication protocol, my security group allows all IPv4 ranges of the corresponding region but does not allow the IPv6 ranges. I believe this does not affect connectivity, correct?
I have verified that the link URL is correctly formatted and uses the public IP address of the target database.

However, the connectivity test to the target endpoint still failed. The error message indicated that the link had timed out, which appeared to be caused by a network disconnection.

Could you please help me see what the problem is? These are screenshots of link testing, managed integration runtime, security groups of the target database, etc.

User's image

Anonymous

2025-11-13T03:55:43.81+00:00

Hi,

Thank you for reaching out to Microsoft Q&A.

Thank you for your patience and for sharing the context around your deployment scenario. I completely understand how important it is for you to provision staging slots within the same region, and I realize the current limitation in the East US region is impacting your deployment.

Currently, there’s no confirmed ETA for restoration of provisioning capabilities in East US region, but our engineering team is actively working on resolving the issue and restoring full functionality as soon as possible.

If services cannot be created there right now, it unfortunately means you would need to consider relocating your entire deployment to a region where this functionality is fully supported.
Anonymous

2025-11-13T06:26:56.2833333+00:00

Thank you very much for your reply.

I still don’t have a clear understanding of how to resolve the issue of connecting to the target database.

From my perspective, the Data Factory deployment itself seems successful, but the failure occurs during the connectivity test with the target database. If the Managed Integration Runtime (IR) is currently unavailable in East US, would switching both my Cosmos DB and Data Factory to another region solve the problem?

May I ask which region you would suggest?
Anonymous

2025-11-13T08:36:20.0733333+00:00

Hi,

Thank you for sharing the details, the Data Factory deployment can succeed even if the connectivity test fails when the Managed Integration Runtime (IR) in East US is unavailable. To resolve this, both Azure Data Factory and the target data services (such as Cosmos DB) should be deployed in the same healthy region. This ensures the Managed IR and linked services operate without cross‑region connectivity issues.

Moving both services together eliminates dependency on the impacted East US IR and restores pipeline connectivity.

Validate the target region’s health and quota in Azure Service Health before proceeding.
https://learn.microsoft.com/en-us/azure/service-health/
https://learn.microsoft.com/en-us/azure/service-health/service-health-faq

Update networking and firewall rules after migration to ensure connectivity.
Anonymous

2025-11-14T03:16:33.4366667+00:00

Hi,

I hope you had a chance to review the information shared earlier, and I hope this information has been helpful! If you still have questions, please let us know what is needed in the comments so the question can be answered.

Your answer

Anonymous

2025-11-13T03:55:43.81+00:00

Hi,

Thank you for reaching out to Microsoft Q&A.

Thank you for your patience and for sharing the context around your deployment scenario. I completely understand how important it is for you to provision staging slots within the same region, and I realize the current limitation in the East US region is impacting your deployment.

Currently, there’s no confirmed ETA for restoration of provisioning capabilities in East US region, but our engineering team is actively working on resolving the issue and restoring full functionality as soon as possible.

If services cannot be created there right now, it unfortunately means you would need to consider relocating your entire deployment to a region where this functionality is fully supported.
Anonymous

2025-11-13T06:26:56.2833333+00:00

Thank you very much for your reply.

I still don’t have a clear understanding of how to resolve the issue of connecting to the target database.

From my perspective, the Data Factory deployment itself seems successful, but the failure occurs during the connectivity test with the target database. If the Managed Integration Runtime (IR) is currently unavailable in East US, would switching both my Cosmos DB and Data Factory to another region solve the problem?

May I ask which region you would suggest?
Anonymous

2025-11-13T08:36:20.0733333+00:00

Hi,

Thank you for sharing the details, the Data Factory deployment can succeed even if the connectivity test fails when the Managed Integration Runtime (IR) in East US is unavailable. To resolve this, both Azure Data Factory and the target data services (such as Cosmos DB) should be deployed in the same healthy region. This ensures the Managed IR and linked services operate without cross‑region connectivity issues.

Moving both services together eliminates dependency on the impacted East US IR and restores pipeline connectivity.

Validate the target region’s health and quota in Azure Service Health before proceeding.
https://learn.microsoft.com/en-us/azure/service-health/
https://learn.microsoft.com/en-us/azure/service-health/service-health-faq

Update networking and firewall rules after migration to ensure connectivity.
Anonymous

2025-11-14T03:16:33.4366667+00:00

Hi,

I hope you had a chance to review the information shared earlier, and I hope this information has been helpful! If you still have questions, please let us know what is needed in the comments so the question can be answered.