Forum Discussion
Issue connecting Azure synapse link for Dataverse
Thank you v-ssriganesh,
We were able to resolve the issue.
The reason was synapse workspace was set up in a V-net and private end points had been enabled, we created a new workspace and disabled V-net and private end points. Now we are able to successfully create the link.The support ticket: Issue connecting Azure synapse link for Dataverse - TrackingID#2412200040003954.
Hi Anonymous ,
Thank you for reaching out and sharing the details of the issue you're experiencing while connecting Dataverse to Microsoft Fabric using Azure Synapse Link.
It looks like your setup is correct, but you're encountering a problem with setting permissions after selecting the tables for Delta Lake conversion. Here are some steps to troubleshoot the issue:
- Ensure that your Spark pool is properly configured. You mentioned using version 3.3 with medium nodes; confirming that there are sufficient resources allocated for your workload can be crucial. If possible, try increasing the number of nodes or changing to a larger instance size temporarily to see if that resolves the issue.
- Confirm that the service principal or identity you are using has the necessary permissions to access both the Dataverse and the ADLS Gen2 storage. You might need to adjust permissions in the Azure portal.
- Ensure that there are no network restrictions or firewall rules blocking the connection between Dataverse and the Spark pool. Check if there are Virtual Network (VNet) configurations that might be affecting connectivity.
- If you have access to the Azure logs, check to see if there are any specific errors logged during your attempts—it might provide clues as to what’s going wrong.
If the above steps do not resolve the issue, consider opening a support ticket with Microsoft Azure support. They can provide more detailed insights into the logs and any backend issues that may be affecting your setup. Below this link create Microsoft support ticket:
https://learn.microsoft.com/en-us/power-bi/support/create-support-ticket
If this helps then please Accept it as a solution and dropping a "Kudos" so other members can find it more easily.
Hope this works for you!
Thanks.
Thank you v-ssriganesh,
We were able to resolve the issue.
The reason was synapse workspace was set up in a V-net and private end points had been enabled, we created a new workspace and disabled V-net and private end points. Now we are able to successfully create the link.The support ticket: Issue connecting Azure synapse link for Dataverse - TrackingID#2412200040003954.
Additionally, during the troubleshoot "Set permissions for MEF on Synapse Workspace" happened to show during a networking check. This occurs if the V-net or managed private endpoints are set.
Hope this helps!