Have you ever encountered a situation where your AutoResolveIntegrationRuntime in Azure Data Factory (ADF) becomes corrupted? If so, don’t worry, you’re not alone. In this article, I will share my recent experience with a corrupted AutoResolveIntegrationRuntime and how I managed to recover it. Hopefully, this will help you solve the issue as well.
The Problem
Normally, the ADF AutoResolveIntegrationRuntime should appear as a Public subtype with a Running status. However, in my case, I noticed that the AutoResolveIntegrationRuntime had been changed to “Managed Virtual Network” and the status showed “Failed to get status”. This can be seen in Figure 2 below:
I was puzzled as to how the Integration Runtime (IR) got corrupted, as I hadn’t made any code changes that could have caused this issue. The corruption of the AutoResolve IR resulted in the failure of the release pipeline, preventing me from pushing any new changes to the production environment.
Identifying the Root Cause
To investigate the root cause of the issue, I examined the DevOps code repository. It turned out that some extra code had been added to the original code, which caused the problem. You can see the added code in Figure 3 below:
The added code modified the AutoResolve IR’s subtype from ‘Public’ to ‘Managed Virtual Network’.
The Resolution
To resolve the issue, I had to delete the code that was causing the AutoResolve IR to change its subtype. After removing the code from the master branch, the AutoResolve IR changed back to ‘Public’, but the status still showed an error message. However, the release pipeline started working again, allowing me to push changes to the production environment.
To completely eliminate the error message, I had to delete the AutoResolve IR code from the Azure DevOps portal. I logged into Azure DevOps, selected the master branch, and navigated to the integrationRuntime folder. There, I found two files: one for the AutoResolve IR and another for the self-hosted IR. I deleted the AutoResolve IR file, as shown in Figure 5 below:
After deleting the file, I refreshed the ADF portal and found that the error message had disappeared completely.
Conclusion
If you ever encounter a situation where your AutoResolveIntegrationRuntime becomes corrupted in Azure Data Factory, you can follow the steps outlined in this article to recover it. By identifying the root cause and making the necessary code changes, you can restore the AutoResolve IR to its original state and ensure the smooth functioning of your release pipeline.