Azure Synapse Link for Dataverse - Stuck on Fetching App

[fearnworks]

I am attempting to set up a link from Dataverse to export its tables as parquet files with Azure Synapse Link and a Spark 3.1 Pool. I've now arrived at the stage where it is letting me proceed and all of the pool configs are validated, but it just hands forever at this screen with the Fetching App loading icon : 

Unfurling the accordion does not provide any additional info. I have tried recreating this several times and kicking it off in different ways but it always gets stuck here. Unclear what options to take at this point as I can not find any info on this issue.

My main goal is to get my dataverse data into a format where I can inject it into my existing python based ETL pipelines and models.  But it seems like this is unnecessarily complicated. 

[elmaslouhi]

Have the same issue here, trying to do some labs. were you able to find a solution to this? 

[ianjensen]

Same issue here.

[dpoggemann]

Same here...  I am going to check with Microsoft Development.

[Dave145232]

For me the solution was to add the service principal of power query. This link helped me: Azure Synapse Link for Dataverse gets stuck “Fetching app…” | Doy's Microsoft 365 and Azure Dev Blog...

[ChrisPiasecki]

Hi @fearnworks,

We'll need a bit more information to help troubleshoot. A few questions:

• Are you using a Synapse workspace, or just syncing direct to Data Lake? 
• Do you have any network restrictions setup for the storage account / synapse workspace ?
• Do you setup all pre-requisite permissions setup on the workspace/storage account?
• Can you verify if the Power Query Online principal has been granted the Reader and Data Access role on the storage account?
  

---
Please click Accept as Solution if my post answered your question. This will help others find solutions to similar questions. If you like my post and/or find it helpful, please consider giving it a Thumbs Up.

[NC611]

Hi Chris,

What does this Power Query Online principal does? We are not using Power Query anywhere, do we still need to add it?

In developer tools, i am seeing 404 error for https://graph.windows.net/myorganization/servicePrincipalsByAppId/xxxxxxxxxxxxxxxxxxxx 

[ChrisPiasecki]

Hi @NC611,

It's a service principal managed by Microsoft that is used as part of the Synapse Link for Dataverse service to write data to your data lake enabled storage account. As part of the setup it should be automatically granted access assuming you have the correct pre-requisite permissions mentioned in the documentation to the Azure storage account and Synapse Workspace.

Did you read through the documentation to ensure you've setup permissions and everything else correctly? You can also try configuring Synapse Link from another environment (in the same region) to rule out environment specific issues.

---
Please click Accept as Solution if my post answered your question. This will help others find solutions to similar questions. If you like my post and/or find it helpful, please consider giving it a Thumbs Up.

[NC611]

Thanks for the Clarification Chris. Yes I read the documentation and all works fine until I check the option 'Use spark Pool for delta lake conversion'. I recently thought to try Delta lake option otherwise it was working in other scenarios. I also tried from different environment and same error there.

I will now try to add Service principal which it is complaining about and see if that works. Thanks for your Help!!

[sandyrob7]

Hi @fearnworks, have you tried the below solutions:

1. While Fetching App is showing, Go to Developer tools in your browser. 
2. Navigate to the “Network” tab.
3. While in the network tab, look for a 404 error that matches the following description or states “app not found.”
4. You will see link like this: https://graph.windows.net/myorganization/servicePrincipalsByAppId/653068b3-88c1-4891-8e93-c8xxxxxxx5.../objectId?api-version=1.6
5. Copy the code mention, like from above it is: 653068b3-88c1-4891-8e93-c8xxxxxxx56a
6. Launch PowerShell as an Administrator in your PC/Laptop
7. Connect to the tenant:
   
   • Run the following command: Connect-AzAccount
   • Log in with the user who has privileges to create a Service Principal in the tenant, such as a global administrator.       
8. Add the Principal:
   • Run this command: New-AzADServicePrincipal -ApplicationId ‘653068b3-88c1-4891-8e93-c8xxxxxxx56a’
9. Try Setting up Synapse Link Again:
   • You should now attempt to set up Synapse Link again. Ideally, this should work without any issues.

------------------------------

Please click Accept as Solution if my post answered your question. This will help others find solutions to similar questions. If you like my post and/or find it helpful, please consider giving it a Thumbs Up