In my organization we have a Development tenant in Azure, which we use for a testing environment to get our hands dirty before deploying anything in the production environment. In this tenant there is a dev-ADF (Azure Data Factory) which pulls data from on-prem servers using a SHIR server. This SHIR server could not connect to dev-Azure ADF.
Solution
When we checked the status of this on-prem Self-hosted integration runtime (IR) in dev-ADF, it was showing the Status as ‘Unavailable’ and when we click on more information it was showing that, ‘The current version is expired…’ and we must manually upgrade it.
Check the status of the SHIR on Azure portal
First, login to the Azure portal and click on the ‘Data Factories’ logo or you can check in your ‘Resource groups’ for the ADF.
The list of ADFs will appear under the ‘Data Factories’ tab:
Then click on the name of your ADF it will take you to ‘Azure Data Factory Studio’ launch page.
Click on the ‘Launch studio’.
It will open the Data Factory in new tab:
Click on the ‘Manage’ icon on the left side menu bar:
Then click on ‘Integration runtimes’ in General tab, you will get the list of all the Integration runtimes:
In this list you can check the status of your Self-hosted integration runtime:
Which is currently showing ‘Unavailable’ and in the last column ‘Version’, you can check the current version and a note, if there is new version available.
To get more information click on the Self-hosted integration runtime, it will slide a ‘Edit integration runtime’ page from the right side. Under ‘Auto update’ tab you will see the more information about the current version status and available version details:
As per the above information, the current version of SHIR has expired and we must upgrade integration runtime manually.
Check the status of the SHIR on On-prem SHIR Server
To identify the on-prem SHIR Server, click on the ‘Nodes’ tab in ‘Edit integration runtime’, here you can check the on-prem SHIR server name:
Now, login to the on-prem SHIR server and from ‘Start’ menu, click on ‘Microsoft Integration Runtime’.
In the ‘Microsoft Integration Runtime Configuration Manager’, you will see the warning in the red text as ‘The integration Runtime node has expired. Please update your node to the latest version from the portal’.
Upgrade On-prem SHIR Server manually:
The status of our SHIR server on Azure portal and in the on-prem, we must upgrade it manually. To upgrade the integration runtime, go to the download page:
Microsoft Integration Runtime Download Page
And click on the ‘Download’ button –
Select the latest version of integration runtime. For me, the latest version is ‘IntegrationRuntime_5.66.9620.1.msi’… and click on ‘Download’ button:
Go to the download location-
And right click on the downloaded **.msi file and click on ‘Install’.
The latest version of Self-hosted integration runtime will start and select location of the installation and click on ‘Install’-
Once the installation is completed, you will see the completed installation page, click on ‘Finish’
Now, you can go back to the ‘Microsoft Integration Runtime Configuration Manager’ and see that, ‘Self-hosted node is connected to the cloud server’ with the green checkmark.
Click on the ‘Update’ tab, you can see the last updated date on it.
On the Azure portal, in integration runtime, the status of your IR will be ‘Running’ with the green checkmark.
Frequently asked questions:
Why does an outdated SHIR fail to connect to Azure Data Factory?
An outdated SHIR may use older components, authentication mechanisms, security protocols, or communication libraries that are no longer fully compatible with Azure Data Factory. As Azure services evolve, older SHIR versions can eventually lose the ability to authenticate or communicate correctly with the ADF service.
How can I check the installed SHIR version?
You can check the installed SHIR version from the Microsoft Integration Runtime Configuration Manager on the server. Open the Configuration Manager and look at theinformation displayed on the main page. You can then compare the installed version with the latest available SHIR release from Microsoft.
How do I update Self-Hosted Integration Runtime?
SHIR can generally be updated through the Microsoft Integration Runtime Configuration Manager by checking for a newer version and installing the available update.
How can I determine whether the problem is caused by SHIR or the network?
Start by checking the SHIR logs and Windows Event Viewer for connectivity and authentication errors. Errors such as “Cannot connect to the cloud service,” “Failed to get service token,” or DNS/name-resolution failures can indicate communication problems between SHIR and Azure. You should also test DNS resolution and outbound HTTPS connectivity from the SHIR server to the required Azure endpoints. If network connectivity is working but an older SHIR version consistently fails to authenticate or communicate, upgrading SHIR should be one of the first troubleshooting steps.
Do I need to reinstall SHIR when upgrading to a newer version?
Normally, you do not need to completely reinstall SHIR just because the installed version is outdated. The existing SHIR installation can generally be upgraded to a newer version while retaining its configuration. However, always verify the authentication key, node configuration, service status, and connectivity after the upgrade, particularly when SHIR is configured as a multi-node or highly available environment.
What should I check after upgrading SHIR?
After upgrading, confirm that the SHIR service is running and that the node appears Online in Azure Data Factory. Test connectivity to the linked services and run a small pipeline to verify end-to-end communication. Also review the SHIR logs and Windows Event Viewer for authentication, DNS, firewall, TLS, or other connectivity errors.
Conclusion:
Normally, Microsoft releases new versions of self-hosted integration runtime every month with new released features, bug fixes, and enhancements. For stability, Microsoft pushes an auto-update every three months with a stable version.
Here, in our case: the self-hosted integration runtime server couldn’t connect to the Azure portal due to DNS issue hence the IR was outdated on the server and was showing unavailable on the portal. We resolved the DNS issue and then manually upgraded the SHIR.
Next Steps:
Read more:
How to Download and Restore SQL Server 2025 AdventureWorks Database? (Step-by-Step Guide)