Fetching App

Today I set up Synapse Link to a “Bring Your Own DataLake” for a customer. When I went through the configuration in SynapseLink and I had configured my D365FO Entities the process hung at the status Message “Fetching App”

After I looked around a bit I found the solution on Yammer… The issue was that the Service Principal for Common Data Service – Azure Data Lake Storage was missing from Microsoft Entra ID.

The solution:

New-AzADServicePrincipal -ApplicationId 546068c3-99b1-4890-8e93-c8aeadcfe56a

This command needs to be run by someone who is an Azure Admin on the tenant level

Note: While researching this, I also saw that the Service Principal for Power Query Online (AppId: f3b07414-6bf4-46e6-b63f-56941f3f4128) also might be missing. In that case… Run this: New-AzADServicePrincipal -ApplicationId f3b07414-6bf4-46e6-b63f-56941f3f4128

Good Luck

User Access issues to Synapse Serverless Views

I just set up the CDMUtil for a customer to let them access Dynamics 365 for Finance and Operations Data, exported to a DataLake, through a serverless instance in Synapse. The customer had added a new user and got an error which vas not perfectly logical

Msg 15151, Level 16, State 1, Procedure CustTable, Line 1 [Batch Start Line 0]
Cannot find the CREDENTIAL 'dynamics365_financeandoperations_XXXXXXXX_sandbox', because it does not exist or you do not have permission.
Msg 4413, Level 16, State 1, Line 223
Could not use view or function 'dbo.CustTable' because of binding errors.

The issue was obiously a permission issue… but where??

When we added an earlier user we set up a Role in SQL that had read access to the SQL DataBase. When we added the user to that role it started working… The confusing part was that the error message did not mention the new user anywhere.

When you set up the Synapse connection to Data Lake and FnO… Make sure you add the correct permissions to new SQL-Native users using TSQL in Management Studio.