This is a follow up to my Q&A I posted on the Visual Studio Market Place for Power Platform Build Tool: https://marketplace.visualstudio.com/items?itemName=microsoft-IsvExpTools.PowerPlatform-BuildTools&s...
Original post in the Q&A:
I have the same issue as Moses asked earlier. I'm using a SPN connection to import a solution, but it failed with the message "GraphUserDetailNotFound Message: The user '7ba93ec6-cd9b-41a2-9c74-fa1ec97fa9ab' was not found in Graph"
I have tried other Tasks in the build pipeline which perform OK with the same SPN connection configured. I've also tested a similar setup on another tenant, where I get the same issue.
Looking at the stack trace it looks like it happens when importing a Canvas Power App:
at Microsoft.Crm.ObjectModel.PowerAppsValidation.PowerAppsServiceResult[T](ResourceResult`1 powerAppsServiceResult)
I've been experimenting with the SPN connection setup through Microsoft.PowerApps.PowerShell-commands. Which also fails consistently. So maybe SPN connections and Canvas PowerApps are not (yet) compatible?
I do not know what the Graph is querying exactly, but I can confirm that the querying for "/users/7ba93ec6-cd9b-41a2-9c74-fa1ec97fa9ab" using the Graph Explorer does indeed not yield any results.
In the reply MS asked to share the DevOps logs here. So these are attached to the thread.
I hope this helps in fixing the issue in the build tools.
I have the same problem deploying a canvas app with the Import Solution task. Actually, the user id identified in the error message is the Azure Object Id from the service principal user in D365. It does not exist as a user in the Microsoft graph, so there would never be a result returned. I think this is is a bug related to canvas app validation when using a service principal account.
I am also facing same issue, GraphUserDetailNotFound
Previous answers are correct: Using AppID/SPN as authentication on the Azure DevOps pipeline task side will cause an Import error for a PowerApps/CanvasApp component. This is a bug on the PowerApps side, a fix is underway, but no ETA for deployment yet.
As workaround until then: use username/password authentication for the ImportSolution task (with that user having MFA disabled in the AAD tenant's ConditionalAccess).
Check out new user group experience and if you are a leader please create your group
Check out how to claim yours today!
Test your skills now with the Cloud Skill Challenge.
We are excited to announce that Demo Extravaganza for 2021 has started!
On-demand access to all the great content presented by the product teams and community members! #MSBizAppsSummit #CommunityRocks