Screenshot shows AutoResolveIR, but may be intending SHIR

[mdrakiburrahman]

The screenshot is associated with using a Self-Hosted IR to perform scans against Private Endpoint protected resources, with MSI Auth not being supported:

But seems to have AutoResolveIR and MSI Auth selected.

Updating to an SHIR and non-MSI auth may clear confusions, e.g:

Thanks!

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: ed20ef90-f4d1-b0c2-2fbc-09893b44f482
• Version Independent ID: dde8050f-3d53-aa72-ac6b-2523adbca356
• Content: Use private endpoints for secure access to Purview - Azure Purview
• Content Source: articles/purview/catalog-private-link.md
• Service: purview
• Sub-service: purview-data-catalog
• GitHub Login: @viseshag
• Microsoft Alias: viseshag

[CHEEKATLAPRADEEP-MSFT]

@mdrakiburrahman From the above screenshot shows as support MSI credential method when you scan your Azure sources using a Azure Integration Runtime.

The document says "We currently do not support MSI credential method when you scan your Azure sources using a self-hosted IR. You must use one of the other supported credential method for that Azure source".

[mdrakiburrahman]

@CHEEKATLAPRADEEP-MSFT thank you for reaffirming what the documentation says - we are aligned.

My point was, the screenshot above (that you shared) is showing the Azure-AutoResolveIntegrationRuntime (which is wrong) - the screenshot should be showing a Self-Hosted IR (as you have bolded) instead.

This screenshot can cause confusions, and should perhaps be updated with a Self-Hosted IR instead.

[CHEEKATLAPRADEEP-MSFT]

@mdrakiburrahman Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

@viseshag Could you please update the screenshot which should point to Self-Hosted IR?

[zeinab-mk]

please-close pr:157884

[mdrakiburrahman]

Thanks @zeinab-mk