Skip to content

Commit 9cb02e0

Browse files
Merge pull request #215562 from ssabat/master
Clarified auto-update paragraph
2 parents fec6c17 + ba5f00e commit 9cb02e0

File tree

2 files changed

+16
-3
lines changed

2 files changed

+16
-3
lines changed

articles/data-factory/security-and-access-control-troubleshoot-guide.md

Lines changed: 14 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.service: data-factory
77
ms.subservice: integration-runtime
88
ms.custom: synapse
99
ms.topic: troubleshooting
10-
ms.date: 08/18/2022
10+
ms.date: 11/04/2022
1111
ms.author: lle
1212
---
1313

@@ -56,6 +56,19 @@ The problem is usually caused by one of the following factors:
5656

5757
If none of the preceding methods works, contact Microsoft for help.
5858

59+
### Deleted or rejected private end point still shows Aprroved in ADF
60+
61+
#### Symptoms
62+
63+
You created managed private endpoint from ADF and obtained an approved private endpoint. But, after deleting or rejecting the private endpoint later, the managed private endpoint in ADF still persists to exist and shows “Approved”.
64+
65+
#### Cause
66+
67+
Currently, ADF stops pulling private end point status after the it is approved. Hence the status shown in ADF is stale.
68+
69+
##### Resolution
70+
71+
You should delete the managed private end point in ADF once existing private endpoints are rejected/deleted from source/sink datasets.
5972

6073
### Invalid or empty authentication key issue after public network access is disabled
6174

articles/data-factory/self-hosted-integration-runtime-auto-update.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.topic: conceptual
77
author: lrtoyou1223
88
ms.author: lle
99
ms.custom: seo-lt-2019
10-
ms.date: 08/18/2022
10+
ms.date: 10/23/2022
1111
---
1212

1313
# Self-hosted integration runtime auto-update and expire notification
@@ -40,7 +40,7 @@ You can use this [PowerShell command](/powershell/module/az.datafactory/get-azda
4040
> 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, then it has some downtime during the auto-update.
4141
4242
## Auto-update version vs latest version
43-
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). Additionally, auto-update to a version is managed one. You cannot change it. If you want to upgrade to latest version, you have to do it manually.
43+
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 internally. You cannot change it.
4444

4545
The self-hosted integration runtime **Auto update** page in ADF portal shows the newer version if current version is old. When your self-hosted integration runtime is online, this version is 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 latest version.
4646

0 commit comments

Comments
 (0)