I'll create a fix on our end to ensure the AAD error gets promptly surfaced to the task and push an updated BuildTools extension 1.0.4 or greater
or create an appID/ServicePrincipal, add that appID as AzDevOps ServiceConnection and use that to authenticate your import task with in the AAD tenant for your CDS environment, ensure that MFA is disabled for that user (under Conditional Access)
This should cause an error from AAD, but that error unfortunately never made it back to the task, hence the task stalls out. I was able to repro the same timeout (and abort) behavior on a pipeline of mine when using username/password authN for a user that has MFA required. Looking at your log (thx!), it's apparent that, before it times out due to the 60 min AzDevOps task timeout, your ImportSolution never got to establish a connection (and hence never even initiated the import).
0 kommentar(er)
