Dataverse Connector - Connect to Dynamics CRM, Scope Error

[klambert]

I am trying to connect to Dynamics CRM, I have followed the set up instructions on the dataverse connector however I am getting the following error:

"The provided request must include a 'scope' input parameter. The provided value for the input parameter 'scope' is not valid."

I have gone into the app registration and tried to add the scopes in the format:  api://<Application ID URI>/openid for example, but I am still getting this error. Has anyone had any success with this connector?

[VojtechT]

Hi @klambert ,

could you share a printscreen of your auth page setting before you click the "Connect" button? The Dataverse requires to authentication to happen twice - the first time to obtain the list of available environments from the Dataverse tenant, then a second one to actually log in into that environment specifically. 

The error indicates that both of these steps did not happen. Is that possible?

[klambert]

Thank you @VojtechT !

This is the auth page before hitting connect:

It pops up with the login window, says I am connected but sits on loading for hours until eventually the error message pops up.

If I connect without "Use service principal" it connects fine and I can see the tables, but I would like to have the ability to schedule without having to keep logging in to collect the data.

Thank you!

[VojtechT]

If your intention is not to use the Service Principal, you should not have any Application level permissions in the Azure app. Could you verify that only Delegated ones are present? 

[klambert]

I do wish to use the service principal (I understand this is needed to avoid access expiring after 24 hours?), within Azure I have followed the process as detailed here:

https://help.alteryx.com/20221/designer/microsoft-dataverse

At the moment, it is successful connecting without the service principal but not with it. This is currently the set up with the API permissions:

[VojtechT]

Actually, the latest version of Dataverse connector - 1.1.0 - does not have this limitation and the user login is valid for 6 months, instead of the previous 24 hours. 

Setting up the Dataverse to use Service principal is little bit more tricky - did you create and assign also the role for the app? As described at the end of the page. 

[Ujjwal]

Hi, I am able to select the environment and then able to select the dataverse table. But while running the flow, it says authentication failed.

Alteryx Version - 2021.4

Dataverse Connector : V1.1.1