Share via

Error (3803) “Linked service type not supported by DataScan” while scanning on-prem PostgreSQL in Azure Purview using SHIR

Mythili Velliangiri 0 Reputation points
2026-01-22T12:11:41.39+00:00

Hi ,

I am trying to integrate an on-premises PostgreSQL server (installed on a separate VM) with Azure Purview using a Self-Hosted Integration Runtime (SHIR).

I have:

Installed and configured SHIR successfully

Created the PostgreSQL data source in Purview

Provided the correct authentication and connection details

Verified network connectivity, ports, and credentials

However, when I test the connection or run the scan, I receive the following error Error: (3803) Linked service type not supported by DataScan

I have already performed basic troubleshooting:

Verified PostgreSQL port accessibility

Rechecked username/password

Confirmed SHIR is online and healthy

Retried scan after reconfiguring the data source

Despite this, the issue persists.

  1. Are there any additional configuration steps or prerequisites required to enable scanning for on-prem PostgreSQL?
  2. Has anyone encountered this error and found a resolution?

Note: The same setup working with Azure integration runtime, but issue persists with SHIR

Azure Data Explorer
Azure Data Explorer

An Azure data analytics service for real-time analysis on large volumes of data streaming from sources including applications, websites, and internet of things devices.

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Smaran Thoomu 35,045 Reputation points Microsoft External Staff Moderator
    2026-01-27T05:33:31.3466667+00:00

    Hi Mythili Velliangiri
    This is expected behavior.

    At the moment, on-premises PostgreSQL scanning via Self-Hosted Integration Runtime (SHIR) is not supported in Microsoft Purview. Because of this limitation, the scan fails with:

    Error (3803): Linked service type not supported by DataScan

    This is not related to network connectivity, credentials, or SHIR health. Even with a correctly configured and healthy SHIR, Purview does not support DataScan for PostgreSQL when accessed through SHIR.

    This also explains why the same setup works when using Azure Integration Runtime but fails when switched to SHIR.

    There are no additional configuration steps or prerequisites that can enable this scenario today.

    If scanning must be done via SHIR, you would need to wait for product support to be added. Otherwise, continue using Azure Integration Runtime where supported, or log a support ticket / feature request for tracking.

    Hope this helps clarify.

    1 person found this answer helpful.
  2. Manoj Kumar Boyini 13,930 Reputation points Microsoft External Staff Moderator
    2026-01-22T17:26:26.35+00:00

    Hi Mythili Velliangiri

    At this time, data quality is not supported on PostgreSQL, which is why the connection is failing.

    Below are the only data sources that supports Data quality User's image

    Please refer the below document for information related to Data sources and file formats supported for data quality in Unified Catalog https://learn.microsoft.com/en-us/purview/unified-catalog-data-quality-supported-sources-file-formats.

    Hope this helps please let us know if you have any questions and concerns.

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.