|
| 1 | +--- |
| 2 | +title: Self-hosted integration runtime auto-update and expiration |
| 3 | +description: Learn about self-hosted integration runtime auto-update and expiration in Microsoft Purview. |
| 4 | +author: linda33wj |
| 5 | +ms.author: jingwang |
| 6 | +ms.service: purview |
| 7 | +ms.subservice: purview-data-map |
| 8 | +ms.topic: how-to |
| 9 | +ms.date: 01/31/2023 |
| 10 | +--- |
| 11 | + |
| 12 | +# Self-hosted integration runtime auto-update and expiration |
| 13 | + |
| 14 | +This article will describe how to let self-hosted integration runtime auto-update to the latest version and how Microsoft Purview manages the versions of self-hosted integration runtime. |
| 15 | + |
| 16 | +## How to check your self-hosted integration runtime version |
| 17 | + |
| 18 | +You can check the version of your self-hosted integration runtime in Microsoft Purview governance portal -> Data map -> Integration runtimes: |
| 19 | + |
| 20 | +:::image type="content" source="./media/self-hosted-integration-runtime-version/self-hosted-integration-runtime-version-portal.png" alt-text="Screenshot that shows the version in Microsoft Purview governance portal."::: |
| 21 | + |
| 22 | +You can also check the version in your self-hosted integration runtime client -> Help tab. |
| 23 | + |
| 24 | +## Self-hosted Integration Runtime auto-update |
| 25 | + |
| 26 | +Auto update is enabled by default when you install a self-hosted integration runtime. You have two options to manage the version of self-hosted integration runtime: auto-update or maintain manually. Typically, Microsoft Purview releases two new versions of self-hosted integration runtime every month, which includes new feature release, bug fix or enhancement. So we recommend users to update to newer version in order to get the latest feature and enhancement. |
| 27 | + |
| 28 | +The self-hosted integration runtime will be automatically updated to newer version. When new version is available while not yet scheduled for your instance, you can also trigger the update from the portal. |
| 29 | + |
| 30 | +:::image type="content" source="media/self-hosted-integration-runtime-version/shir-auto-update-with-new-version.png" alt-text="Screenshot of checking the self-hosted integration runtime version and trigger update."::: |
| 31 | + |
| 32 | +> [!NOTE] |
| 33 | +> If you have multiple self-hosted integration runtime nodes, there is no downtime during auto-update. The auto-update happens in one node first while others are working on tasks. When the first node finishes the update, it will take over the remain tasks when other nodes are updating. If you only have one self-hosted integration runtime node, then it has some downtime during the auto-update. |
| 34 | +
|
| 35 | +## Auto-update version vs latest version |
| 36 | + |
| 37 | +To ensure the stability of self-hosted integration runtime, although we release two versions, we'll only push one version every month. So sometimes you'll find that the auto-update version is the previous version of the actual latest version. If you want to get the latest version, you can go to [download center](https://www.microsoft.com/download/details.aspx?id=39717) and do so manually. Additionally, **auto-update** to a new version is managed by the service, and you can't change it. |
| 38 | + |
| 39 | +The self-hosted integration runtime **Version** tab in Microsoft Purview governance portal shows the newer version if current version is old. When your self-hosted integration runtime is online, this version is the auto-update version and will automatically update your self-hosted integration runtime in the scheduled time. But if your self-hosted integration runtime is offline, the page only shows the newer version. |
| 40 | + |
| 41 | +If you have multiple nodes, and for some reasons that some of them aren't auto-updated successfully. Then these nodes roll back to the version, which was the same across all nodes before auto-update. |
| 42 | + |
| 43 | +## Self-hosted Integration Runtime expiration |
| 44 | + |
| 45 | +Each version of self-hosted integration runtime will be expired in one year. The expiring message is shown in Microsoft Purview governance portal and the self-hosted integration runtime client **90 days** before expiration. |
| 46 | + |
| 47 | +## Next steps |
| 48 | + |
| 49 | +- [Create and manage a self-hosted integration runtime](manage-integration-runtimes.md) |
0 commit comments