Merge pull request #228408 from zeinab-mk/patch-36

Update catalog-private-link-name-resolution

Author: prmerger-automator[bot]

articles/purview/catalog-private-link-name-resolution.md

@@ -6,7 +6,7 @@ ms.author: viseshag
 ms.service: purview
 ms.subservice: purview-data-catalog
 ms.topic: how-to
-ms.date: 12/09/2022
+ms.date: 02/23/2023
 # Customer intent: As a Microsoft Purview admin, I want to set up private endpoints for my Microsoft Purview account, for secure access.
 ---
 
@@ -175,7 +175,7 @@ If you do not use DNS forwarders and instead you manage A records directly in yo
 | `Contoso-Purview.proxy.purview.azure.com` | A | \<account private endpoint IP address of Microsoft Purview\> |
 | `Contoso-Purview.guardian.purview.azure.com` | A | \<account private endpoint IP address of Microsoft Purview\> |
 | `gateway.purview.azure.com` | A | \<account private endpoint IP address of Microsoft Purview\> |
-| `insight.prod.ext.web.purview.azure.com` | A | \<account private endpoint IP address of Microsoft Purview> |
+| `insight.prod.ext.web.purview.azure.com` | A | \<portal private endpoint IP address of Microsoft Purview\> |
 | `manifest.prod.ext.web.purview.azure.com` | A | \<portal private endpoint IP address of Microsoft Purview\> |
 | `cdn.prod.ext.web.purview.azure.com` | A | \<portal private endpoint IP address of Microsoft Purview\> |
 | `hub.prod.ext.web.purview.azure.com` | A | \<portal private endpoint IP address of Microsoft Purview\> |