Devops and D4T Deployment
So I've been using Dataverse for Teams quite intensively and I like the idea of having a REAL relational database for your data (compared to SharePoint). I'm aware of the limitations, especially about no API's for D4T Teams, but I was still wondering whether it is possible to leverage D4T Solutions in Devops? I started with the basic one - that is exporting a package - and I already got stuck there.
To authenticate to the environment I need:
- Environment URL
- User Name & Password
As for the environment URL, I realized you can't get it by going to the Power Platform Admin Center --> Click on Environment Name and then get the Environment URL from there. However, thanks to a post I've found, I figured you could get it by opening up Power Apps in MS Teams, click on the About tab, click on Session Details and get the Instance URL from there (though, is it really the right one?).
When I'm trying to open this URL, I'm stuck in a refresh loop (probably due to the D4T limitations), meaning, I can't create a Service Principal... right? Even though this kinda sucks (--> MFA), this is anyway fine by me for now, as I can simply use a Generic Authentication in DevOps for the time being (hopefully not forever...).
BUT... and here it comes...
I'm stuck with the Power Platform Export Solution step. My DevOps pipeline throws the error:
[error]Failed to connect to instance: https://orgxxxxx.crm4.dynamics.com/. Please verify your credentials for *** and instance url.
The generic username & password are correct, so I assume it has something to do with the URL.
Does anyone know if DevOps really is allowed to connect to mentioned D4T ***.dynamics.com URL?
Thanks for your time and cheers!
As tag "office-deployment" focus more on general issues of Office deploymet, but your issue is more realted to Power Apps which is not supported on Q&A forum currently. I find that you have posted a same thread on Power Apps community that is an appropriate forum.
I would modify the tag to be "not-supported", thanks for your understanding.
Sign in to comment