I am trying to export a powerApps solution into a repository using Azure DevOps pipelines, but every time I try to run a pipeline to automate this process it shows a failed to connect to dataverse error. I have a powerApps for office 365 plan as well as a powerApps per user plan trial. I have made sure I used the correct environment URL with the right credentials for the service connection.
Am I getting this error because of the access rights I have?
Do I need to have a dataverse in my powerApp to be able to use Azure DevOps pipeline? The pipeline I am using
The error I get
@dashv, could you confirm which Authentication type did you provide for the ALM pipeline, is it username/password or Service Principal Name? if it's username/password you need to make sure there is no MFA turned on it will not support if it has.
Thank you, that's helpful: we use solutions, so now I know Dataverse exists in our case. Now the question is how to understand what is wrong with the connection from ALM pipeline to Dataverse? Maybe there is some settings inside Power Apps platform or inside Dataverse (haven't access it so far), that manage permissions?
Slight variation to this - you need Dataverse, which comes with D365 customer engagement apps or a Power Apps premium license that also gives you Dataverse. I does not matter whether the app itself uses Dataverse, SQL or SharePoint or any other datasource, the important thing is that the environment itself has a Dataverse instance. If you can create a solution, you have Dataverse so any authentication issues has to be with the access rights or credentials used
you need to have the dynamics 365 customer engagement plan to be able to connect to dataverse
you need to have the dynamics 365 customer engagement plan to be able to connect to dataverse
Have the same problem, I'm also not using Dataverse explicitly (actually we have SQL Database)
same issue here
WarrenBelz
87
Most Valuable Professional
mmbr1606
71
Super User 2025 Season 1
Michael E. Gernaey
65
Super User 2025 Season 1