Skip to content

Commit 4597277

Browse files
committed
Fix format and tweak wording
1 parent 3493415 commit 4597277

File tree

2 files changed

+17
-17
lines changed

2 files changed

+17
-17
lines changed

articles/purview/self-hosted-integration-runtime-version.md

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Self-hosted integration runtime auto-update and expire notification
3-
description: Learn about self-hosted integration runtime auto-update and expire notification
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.
44
author: linda33wj
55
ms.author: jingwang
66
ms.service: purview
@@ -9,23 +9,23 @@ ms.topic: how-to
99
ms.date: 01/31/2023
1010
---
1111

12-
# Self-hosted integration runtime auto-update and expire notification
12+
# Self-hosted integration runtime auto-update and expiration
1313

1414
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.
1515

1616
## How to check your self-hosted integration runtime version
1717

18-
You can check the version of your self-hosted integration runtime in Microsoft Purview Governance portal -> Data map -> Integration runtimes:
18+
You can check the version of your self-hosted integration runtime in Microsoft Purview governance portal -> Data map -> Integration runtimes:
1919

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.":::
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.":::
2121

2222
You can also check the version in your self-hosted integration runtime client -> Help tab.
2323

24-
## Self-hosted Integration Runtime Auto-update
24+
## Self-hosted Integration Runtime auto-update
2525

26-
Auto update is enabled by default when you install a self-hosted integration runtime in your local machine or an Azure VM, 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.
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.
2727

28-
The self-hosted integration runtime will be automatically update to newer version. When new version is available while not yet scheduled for your instance, you can also trigger the update from the portal.
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.
2929

3030
:::image type="content" source="media/create-self-hosted-integration-runtime/shir-auto-update-with-new-version.png" alt-text="Screenshot of checking the self-hosted integration runtime version and trigger update.":::
3131

@@ -34,15 +34,15 @@ The self-hosted integration runtime will be automatically update to newer versio
3434
3535
## Auto-update version vs latest version
3636

37-
To ensure the stability of self-hosted integration runtime, although we release two versions, we will only push one version every month. So sometimes you will 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 cannot change it.
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.
3838

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.
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.
4040

41-
If you have multiple nodes, and for some reasons that some of them are not auto-updated successfully. Then these nodes roll back to the version which was the same across all nodes before auto-update.
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.
4242

43-
## Self-hosted Integration Runtime Expire Notification
43+
## Self-hosted Integration Runtime expiration
4444

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.
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.
4646

4747
## Next steps
4848

articles/purview/toc.yml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -155,10 +155,10 @@ items:
155155
displayName: Create and manage credentials
156156
- name: Manage integration runtimes
157157
items:
158-
name: Create and manage a self-hosted integration runtime
159-
href: manage-integration-runtimes.md
160-
name: Self-hosted integration runtime auto-update and expire notification
161-
href: self-hosted-integration-runtime-auto-update.md
158+
- name: Create and manage a self-hosted integration runtime
159+
href: manage-integration-runtimes.md
160+
- name: Self-hosted integration runtime auto-update and expiration
161+
href: self-hosted-integration-runtime-version.md
162162
- name: Manage assets with Metamodel
163163
href: how-to-metamodel.md
164164
- name: Create Service Principal

0 commit comments

Comments
 (0)