Skip to content

Commit 3cbc72d

Browse files
authored
Merge pull request #202771 from whhender/shir-update
Adding table for navigation
2 parents 5374140 + 55f65c6 commit 3cbc72d

File tree

1 file changed

+24
-11
lines changed

1 file changed

+24
-11
lines changed

articles/purview/manage-integration-runtimes.md

Lines changed: 24 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,20 @@ The integration runtime (IR) is the compute infrastructure that Microsoft Purvie
1515

1616
A self-hosted integration runtime (SHIR) can be used to scan data source in an on-premises network or a virtual network. The installation of a self-hosted integration runtime needs an on-premises machine or a virtual machine inside a private network.
1717

18-
This article describes how to create and manage a self-hosted integration runtime.
18+
This article covers both set up of a self-hosted integration runtime, and troubleshooting and management.
19+
20+
21+
|Topic | Section|
22+
|----|----|
23+
|Set up a new self-hosted integration runtime|[Machine requirements](#prerequisites)|
24+
||[Source-specific machine requirements are listed under prerequisites in each source article](azure-purview-connector-overview.md)|
25+
||[Set up guide](#setting-up-a-self-hosted-integration-runtime)|
26+
|Networking|[Networking requirements](#networking-requirements)|
27+
||[Proxy servers](#proxy-server-considerations)|
28+
||[Private endpoints](catalog-private-link.md)|
29+
||[Troubleshoot proxy and firewall](#possible-symptoms-for-issues-related-to-the-firewall-and-proxy-server)|
30+
||[Troubleshoot connectivity](troubleshoot-connections.md)|
31+
|Management|[General](#manage-a-self-hosted-integration-runtime)|
1932

2033
> [!NOTE]
2134
> The Microsoft Purview Integration Runtime cannot be shared with an Azure Synapse Analytics or Azure Data Factory Integration Runtime on the same machine. It needs to be installed on a separated machine.
@@ -41,7 +54,7 @@ Installation of the self-hosted integration runtime on a domain controller isn't
4154
4255
- Self-hosted integration runtime requires a 64-bit Operating System with .NET Framework 4.7.2 or above. See [.NET Framework System Requirements](/dotnet/framework/get-started/system-requirements) for details.
4356

44-
- Ensure Visual C++ Redistributable for Visual Studio 2015 or higher is installed on the self-hosted integration runtime machine. If you don't have this update installed, [you can download it here](https://docs.microsoft.com/cpp/windows/latest-supported-vc-redist#visual-studio-2015-2017-2019-and-2022).
57+
- Ensure Visual C++ Redistributable for Visual Studio 2015 or higher is installed on the self-hosted integration runtime machine. If you don't have this update installed, [you can download it here](/windows/latest-supported-vc-redist#visual-studio-2015-2017-2019-and-2022).
4558

4659
- The recommended minimum configuration for the self-hosted integration runtime machine is a 2-GHz processor with 4 cores, 8 GB of RAM, and 80 GB of available hard drive space. For the details of system requirements, see [Download](https://www.microsoft.com/download/details.aspx?id=39717).
4760
- If the host machine hibernates, the self-hosted integration runtime doesn't respond to data requests. Configure an appropriate power plan on the computer before you install the self-hosted integration runtime. If the machine is configured to hibernate, the self-hosted integration runtime installer prompts with a message.
@@ -103,23 +116,23 @@ You can edit a self-hosted integration runtime by navigating to **Integration ru
103116

104117
You can delete a self-hosted integration runtime by navigating to **Integration runtimes** in the Management center, selecting the IR and then selecting **Delete**. Once an IR is deleted, any ongoing scans relying on it will fail.
105118

106-
## Service account for Self-hosted integration runtime
119+
### Notification area icons and notifications
107120

108-
The default sign in service account of self-hosted integration runtime is **NT SERVICE\DIAHostService**. You can see it in **Services -> Integration Runtime Service -> Properties -> Log on**.
121+
If you move your cursor over the icon or message in the notification area, you can see details about the state of the self-hosted integration runtime.
109122

110-
:::image type="content" source="../data-factory/media/create-self-hosted-integration-runtime/shir-service-account.png" alt-text="Service account for self-hosted integration runtime":::
123+
:::image type="content" source="../data-factory/media/create-self-hosted-integration-runtime/system-tray-notifications.png" alt-text="Notifications in the notification area":::||
111124

112-
Make sure the account has the permission of Log on as a service. Otherwise self-hosted integration runtime can't start successfully. You can check the permission in **Local Security Policy -> Security Settings -> Local Policies -> User Rights Assignment -> Log on as a service**
125+
### Service account for Self-hosted integration runtime
113126

114-
:::image type="content" source="../data-factory/media/create-self-hosted-integration-runtime/shir-service-account-permission.png" alt-text="Screenshot of Local Security Policy - User Rights Assignment":::
127+
The default sign-in service account of self-hosted integration runtime is **NT SERVICE\DIAHostService**. You can see it in **Services -> Integration Runtime Service -> Properties -> Log on**.
115128

116-
:::image type="content" source="../data-factory/media/create-self-hosted-integration-runtime/shir-service-account-permission-2.png" alt-text="Screenshot of Log on as a service user rights assignment":::
129+
:::image type="content" source="../data-factory/media/create-self-hosted-integration-runtime/shir-service-account.png" alt-text="Service account for self-hosted integration runtime":::
117130

118-
## Notification area icons and notifications
131+
Make sure the account has the permission of Log-on as a service. Otherwise self-hosted integration runtime can't start successfully. You can check the permission in **Local Security Policy -> Security Settings -> Local Policies -> User Rights Assignment -> Log on as a service**
119132

120-
If you move your cursor over the icon or message in the notification area, you can see details about the state of the self-hosted integration runtime.
133+
:::image type="content" source="../data-factory/media/create-self-hosted-integration-runtime/shir-service-account-permission.png" alt-text="Screenshot of Local Security Policy - User Rights Assignment":::
121134

122-
:::image type="content" source="../data-factory/media/create-self-hosted-integration-runtime/system-tray-notifications.png" alt-text="Notifications in the notification area":::
135+
:::image type="content" source="../data-factory/media/create-self-hosted-integration-runtime/shir-service-account-permission-2.png" alt-text="Screenshot of Log on as a service user rights assignment":::
123136

124137
## Networking requirements
125138

0 commit comments

Comments
 (0)