Synapse Link for Dataverse "SYN-806: Default storage container in Synapse workspace is not accessible error" when enabling tables

Question

Hi

I'm trying to setup Synapse link via dataverse in PowerApps to F&O. I'm able to setup the connection but when I enable tables sync status is throwing out error.

Error details - SYN-806: Default storage container in Synapse workspace is not accessible.

I did not change anything in the Synapse Workspace or the Storage Account after setting up the Synapse Link.

I saw the documentation on this issue in the documentationhttps://learn.microsoft.com/en-us/power-apps/maker/data-platform/azure-synapse-link-troubleshooting-guide). Unfortunately, the resolution on this issue is not helping me as I don't think it is clear enough.

The Synapse Link setup worked fine and it created the containers on the storage account itself. How can it be that the access is suddendly not possible anymore? For me, just after the setup, I have two containers:

1. dataverse-dynamics365t-xxxxxx
2. power-platform-dataflows

There are also files and folders for the tables that I connected. But still, the Sync Status in PowerApps reports: SYN-806: Default storage container in Synapse workspace is not accessible. Visit aka.ms/SynapseLinkErrors to fix

Answer 1

Hi @Grossmann Manuel

Thanks for the question and using MS Q&A platform.

As I understand that you are trying to set up Synapse Link to synchronize tables between Dataverse in PowerApps and Finance and Operations (F&O). The connection setup seems successful, but enabling table sync throws the "SYN-806: Default storage container in Synapse workspace is not accessible" error.

The error message indicates that the Synapse workspace cannot access the storage container it needs to perform the synchronization. Even though the setup initially seemed successful, the error can occur due to the following reasons:

Check Azure Resource Access: Ask your Azure Administrator to verify if any recent changes have been made to the storage account or container access control. They can check for any automated scripts or policies impacting permissions.

Check Permissions: While you might not have changed permissions manually, it's possible there are automated security policies or scripts that could have accidentally modified permissions on the storage containers, restricting Synapse Link's access.

Azure Resource Manager (ARM) Template Deployment: If your Synapse Workspace was deployed using an Azure Resource Manager (ARM) template, there might be a configuration issue in the template itself. Double-check the permissions defined for the storage account within the template.

Recreate the Connection (With Caution): Try to recreate the connection, as it involves deleting and recreating the Synapse Link connection in PowerApps. This can potentially force Synapse Link to re-establish the connection and pick up the correct permissions during the process. However, be aware that this might cause some initial data synchronization delays.

Intermittent issue: In rare cases, there could be temporary permission glitches within Azure. Try waiting for a short period and then attempt enabling table sync again. Sometimes, a quick refresh can resolve temporary access issues.

I hope this information helps! Please do let us know if you have any further questions.

---

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.

Answer 2

Hi @Chandra Boorla and anyone encountering this

For me the solution was that there was no default container in the linked Data Lake inside the Synapse Workspace. During all my tests I accidentely deleted the container.
The default container has the suffix "(Primary)" after its name. Make sure to have it!

Also, there are more useful debug information in the container that is used by Synapse Link to store the table contents. For me, there was a "SparkError"-Folder with files and log messages inside. Go and have a look there!

I hope no-one else needs to spend so much time on this problem as me :)