Skip to content

Commit 6640a0d

Browse files
committed
Tweak wording
1 parent 285e126 commit 6640a0d

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/data-factory/how-to-access-secured-purview-account.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,9 +23,9 @@ Microsoft Purview provides different options of [firewall settings](/purview/cat
2323
| Disabled for ingestion only | Supported | Supported | Supported, ***ingestion*** private endpoints are required |
2424
| Disabled from all networks | Unsupported | Supported, ***account*** and ***ingestion*** private endpoints are required | Supported, ***account*** and ***ingestion*** private endpoints are required |
2525

26-
You can use [Azure private endpoints](../private-link/private-endpoint-overview.md) for your Microsoft Purview accounts to allow secure access from a virtual network (VNet) to the catalog over a Private Link. Microsoft Purview provides different types of private points for various access need: *account* private endpoint, *portal* private endpoint, and *ingestion* private endpoints. Learn more from [Microsoft Purview private endpoints conceptual overview](../purview/catalog-private-link.md#conceptual-overview).
26+
You can use [Azure private endpoints](../private-link/private-endpoint-overview.md) for your Microsoft Purview accounts to allow secure access from a virtual network (VNet) to the catalog over a Private Link. Microsoft Purview provides different types of private endpoints for various access need: *account* private endpoint, *portal* private endpoint, and *ingestion* private endpoints. Learn more from [Microsoft Purview private endpoints conceptual overview](../purview/catalog-private-link.md#conceptual-overview).
2727

28-
When private endpoints are needed, make sure you follow below instruction to set them up so Data Factory can successfully connect to Microsoft Purview. If the integration runtime cannot connect to Purview, you will see lineage status as failed on the activity run monitoring, and may experience slight longer activity execution duration because the integration runtime tries to establish the connection and wait until the default timeout is hit.
28+
When private endpoints are needed, make sure you follow below instruction to set them up so Data Factory can successfully connect to Microsoft Purview. If the integration runtime cannot connect to Purview, you will see lineage status as failed or timed out on the activity run monitoring, and the activity execution duration might be slight longer (up to 2-minute which is the default timeout setting).
2929

3030
| Scenario | Required Microsoft Purview private endpoints |
3131
| ------------------------------------------------------------ | ------------------------------------------------------------ |

0 commit comments

Comments
 (0)