@Thota Harsha Vardhan - Thanks for the question and using MS Q&A platform.
It's possible that the issue you're facing with registering your on-premises SQL Server to Azure Purview is related to the linked service configuration. The error message you're seeing indicates that the test connection to the linked service failed.
Adding a proxy to the integration runtime should not cause this issue, but it's important to ensure that the proxy is properly configured and that it allows traffic to flow between your on-premises environment and Azure Purview.
To troubleshoot the issue further, you can check the following:
- Verify that the linked service configuration is correct. Make sure that you have provided the correct server name, database name, and authentication details.
- Check that the firewall settings on your on-premises SQL Server allow traffic from the integration runtime. You may need to add the IP address of the integration runtime to the firewall rules.
- Check that the integration runtime is running and properly configured. You can use the Integration Runtime Configuration Manager to verify the configuration and status of the integration runtime.
- Check that the self-hosted integration runtime has access to the internet and can connect to Azure Purview. You can test this by opening a web browser on the machine running the integration runtime and navigating to the Azure Purview portal.
For more details, refer to Connect to and manage an on-premises SQL server instance in Microsoft Purview.
Hope this helps. Do let us know if you any further queries.
If this answers your query, do click Accept Answer
and Yes
for was this answer helpful. And, if you have any further query do let us know.