- The delta conversion is failing because the ABFSS URI is malformed, the container/account parts are swapped and an extra path segment appears:
abfss://[mystorageaccount]/default/default@[mystorageaccount].dfs.core.windows.net/...instead of the correct form:abfss://<container>@<storageaccount>.dfs.core.windows.net/<path> - That malformed URI produces an "invalid authority" error and prevents delta files / near real-time table from being created.
- Two common reasons for this in Synapse + Synapse Link:
- Synapse workspace default storage/container is configured incorrectly (container name and account were mixed or set to the storage account name instead of the container).
- Your network configuration (managedVNet / private endpoints / data exfiltration protection) is blocking the service or causing Synapse Link to attempt an incorrect internal path. Note: Synapse Link for Dataverse does not support managed private endpoints / managed VNet per the product doc.
Export dataverse data to in delta lake format not working
We have setup Azure Synapse Link for Dataverse and followed the documentation here:
- https://free.blessedness.top/en-us/power-apps/maker/data-platform/azure-synapse-link-synapse
- Export Microsoft Dataverse data in Delta Lake format - Power Apps | Microsoft Learn
According to this we should see a near real-time table and a snapshot table in our Azure Synapse Analytics environment but the near real-time table is missing.
Documentation:
Our environment:
Similarly the delta files have never been created in the appropriate /deltalake folder of our ADLS Gen2 storage location:
The spark pool appears to be writing the csv's correctly to the target folders in our storage account ADLS Gen2 and the spark job states that it was successful in synapse workspace.
However when I dig into the logs of the spark executions there's an error in the DeltaConversion job stating "invalid authority" when trying to access the default workspace storage location. It's referring to an abfss path that looks incorrect to me as it's in the format of:
- abfss://[mystorageaccount]/default/default@[mystorageaccount].dfs.core.windows.net/synapse/workspaces/[mysynapseworkspace]/warehouse
I am assuming it should be in the format of:
- abfss://default@[mystorageaccount].dfs.core.windows.net/synapse/workspaces/[mysynapseworkspace]/warehouse
There is also an error reading / writing to the metastore.
The above issues could be a symptom of something else - any assistance with what is going on would be appreciated.
FYI we are using managed VNet and managed private endpoints. I understand this article https://free.blessedness.top/en-us/power-apps/maker/data-platform/azure-synapse-link-synapse states that, "Synapse workspaces featuring managed private endpoints, data exfiltration protection, or managed virtual networks aren't supported." however the architecture we have was advised to us by Microsoft resources in Australia we no longer have access to.
Spark version 3.4
Delta Lake 2.4
Azure Synapse Analytics
-
Vinodh247 39,201 Reputation points MVP Volunteer Moderator2025-10-26T11:18:45.39+00:00