Datafactory Self hosted integration runtime auto updates

When you enable auto-update for your self-hosted integration runtime (SHIR), updates are typically managed internally. The auto-update process releases a new version every three months, using a stable version from the preceding three months. This means that the version you see as the autoupdated version may not always be the latest version available. In your case, if your SHIR is still on version '5.55.9315.1', it may be due to the fact that the auto-update has not yet scheduled the update to the latest version '5.60.9438.1'.

You can check the auto-update version in the ADF portal, and if your self-hosted integration runtime is online, it will show the autoupdate version. If it is offline, it will display the latest version available. If you want to ensure you have the latest version, you can manually trigger the update from the portal.

Additionally, if you have multiple nodes, the auto-update happens in one node first while others continue working, which can also contribute to perceived delays in updates.

If you are concerned about the delay, you might want to check the auto-update settings and ensure that there are no issues preventing the update from occurring as scheduled.

References:

• Self-hosted Integration Runtime Autoupdate
• Autoupdate Version vs Latest Version

Hi

Thanks for contacting to Microsoft QA, below are the details mitigation steps to resolve your reported issue -

There isn’t a “delay” bug—SHIR auto‑update works on a staged cadence. Microsoft ships monthly builds, but auto‑update pushes only a stable build from the prior quarter. So your node on 5.55.9315.1 can correctly show “up to date” even when 5.60.9438.1 is the newest download. If you want 5.60 now, upgrade manually. [learn.microsoft.com]

Auto‑update vs. latest: ADF releases monthly; auto‑update happens roughly every three months using a stability‑vetted version from the preceding months. That’s why the portal/client can say “up to date” on 5.55 while 5.60 is available in the download center. [learn.microsoft.com], [github.com]

Concrete fix (two options)

Option A — Wait for the next auto‑update window Do nothing; your SHIR will move to the next stable ring automatically during its scheduled window. [learn.microsoft.com]

Option B — Upgrade to 5.60 immediately (recommended if you need the newest features)

1. Manual upgrade from the SHIR host (least friction):
   • Download/install the latest SHIR (5.60.9438.1) from Microsoft’s download center via the Configuration Manager (Home → Update).
   • Ensure prerequisites: .NET Framework ≥ 4.7.2, sufficient disk space, service can reach Microsoft endpoints; confirm IR credential status = Synced in ADF (Manage → Integration Runtime → Edit → Credentials). [learn.microsoft.com]
2. API‑based upgrade (for automation/at scale):
   • Use the ADF REST API “Upgrade” endpoint to push the latest version to your self‑hosted IR. Useful for scripted or multi‑node environments.
3. Tip: Single‑node SHIR experiences brief downtime during update; multi‑node setups update sequentially to avoid pipeline failures. Plan your window accordingly. [learn.microsoft.com]