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:
- 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.
- 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.
- 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.
- 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.
- 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.