I'm getting an error saying 'No connection can be used' when trying to create Data Quality rules under a Data Product, even though I've already successfully connected to Azure Synapse

USer22222 0 Reputation points
2024-10-15T15:25:53.06+00:00

Hi everyone,

I'm encountering an issue when trying to create Data Quality rules under a Data Product in Microsoft Purview. The error message I receive is: 'No connection can be used, try to create a connection first.'

I've already established a successful connection with Azure Synapse, so I'm not sure why it's not recognizing it. I'm wondering if the issue might be related to the technical assets(Azure Synapse Dedicated SQL Tables) I've connected with the Data Product. The assets are from an Azure Synapse Dedicated SQL, but the Data Quality connection doesn't directly reference Synapse—it connects via Azure SQL DB, and I manually added the endpoint from my Azure Synapse Dedicated SQL Pool.

Has anyone experienced this or know what I might be missing?

Thanks in advance!

Azure Synapse Analytics
Azure Synapse Analytics
An Azure analytics service that brings together data integration, enterprise data warehousing, and big data analytics. Previously known as Azure SQL Data Warehouse.
4,989 questions
Microsoft Purview
Microsoft Purview
A Microsoft data governance service that helps manage and govern on-premises, multicloud, and software-as-a-service data. Previously known as Azure Purview.
1,221 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Vinodh247 23,111 Reputation points MVP
    2024-10-16T05:23:10.7433333+00:00

    It seems that the issue might be related to how the connection is being established and referenced for the Data Quality rules in Microsoft Purview. Here are a few points to check and potentially resolve the issue:

    1. Connection Type: Ensure that the connection type being used for data quality rules supports synapse dedicated SQL pool. Even though you’ve manually added the endpoint, the purview data quality feature might require a specific connection type or method, such as azure SQL db, which may not be fully compatible with synapse.
    2. Mapping the Assets Correctly: Verify that the technical assets (synapse dedicated SQL pool tables) are correctly mapped under the data product in purview. The Data Quality rules need to reference the assets as per their connection type.
    3. Permissions: Ensure that the permissions for your Purview service and synapse resources are properly configured. Purview requires specific data access permissions to apply data quality rules.
    4. Purview Connection Setup: While you have manually added the synapse endpoint, try creating an explicit azure SQLdb connection in Purview, even though your assets are from Synapse. This might help Purview recognize the connection in the context of data quality.
    5. Feature Support for Synapse: Check if microsoft purview's data quality feature fully supports synapse dedicated SQL Pools, or if there are specific limitations or requirements for using it with Synapse. There could be a mismatch between what's supported for Synapse versus azure SQL db.

    Try reviewing these aspects and let me know if this helps or in case you encounter further issues.


Your answer

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