You’re offline. This is a read only version of the page.
Announcements
I am encountering issues with my Customer Insights environments when I am trying to connect to Dataverse through the Power Query connector
I get the below message even if the user is valid. I used to connect to both the environment domain (dataverse tenant) and CI. Both environment are created under the same tenant.
Does
This needs to be marked as the answer. It makes sense when you think about it. They are asking for the Environment Domain and not the full URL. It would just be nice if either the error message was clearer or there was a hint that it didn't require the https://
Even better would be if they just removed it for you, knowing that 99% of users will probably type the full url as you would normally in any other place when entering the environment address
Great thanks for your feedback Reddy.
Best,
Arnaud
Hi Arnaud Lebet ,
The solution is actually by getting rid of "HTTPS://" in the URL when you ingest the data using Power Query.
Reddy
Hi John Wiese,
I'm currently in another PoC where we have exactly the same urgent issue (using Dataverse connector using Power Query = invalid credentials).
Could you please enlighten here what the causes could be?
- I entered the correct Dynamics Environment domain
- successfully signed in
- click on "Next"
- cannot proceed due to Invalid Credentials
Then, to be sure, I went to PowerApps to check the existing connections, they are all fine (connected).
I'd highly appreciate your help.
Reddy
no, this is not correct. These are two totally different methods and unrelated.
The Power Query -> Dataverse connector uses the connector to get the meta data for the entities you select from your dataverse, allows you to transform that data, then imports the transformed data into the CI managed (or your data lake in the BYODL scenario) for use within CI.
The "Connect to Dataverse" method simply lets you choose which entities you want to use within CI and retains a link to the Dataverse datalake. Whenever we need to use that data (M3, or to build a measure, segment, activity) we connect to the Dataverse and pull the current (complete, all fields, all rows) dataset perform the task and then discard the data from memory.
They are in no way linked together. You can do one, or the other...or both.
Hi Arnaud,
The data lake connector that you are missing will connect to the data lake data created by your "Microsoft Dataverse" import method.
So the first import method creates the data lake and updates that one-to-one with dataverse entities you selected. Then your Dataverse - Data Lake (preview) will connect to that data lake and you can transform with Power Query on that data.
-Francis
Ok, thank you. I will create a ticket for this then.
Yes I did also create a data source using the Microsoft Dataverse Import Mode but there I have the issue that the data that I am ingesting is corrupt and cannot be used in the unification process.
What do you mean by "The data lake connector will get data from output of the first data source" ?
Arnaud
Ok ... that's the reason ..
I believe you need to create a ticket on this. I would think this connector was turned on for all CI instances now.
And you did create a data source based on
The data lake connector will get data from output of the first data source.
-Francis
Thanks for your quick feedback.
I don't have this connector available. I am using this one:
Hi Arnaud
Are you using this connector for the second step?
This is the one to go for.
#1
André Arnaud de Cal...
293,518
Super User 2025 Season 1
#2
Martin Dráb
232,594
Most Valuable Professional
#3
nmaenpaa
101,158
Moderator
Share
Report
All responses (
Answers (