Showing results for 
Search instead for 
Did you mean: 
Resolver III
Resolver III

Using a Service Principal loses metadata

Hi All,

From what I have read, I expected to see the flow connecting with a service principal to execute with impersonation. When using a service principal to run flow that creates a record it does not appear to reflect anything about the user that initiated the flow.

Here's what I expected to see on a record created by a flow:

  • Created By:  Susan Human
  • Modified By:  Susan Human
  • Created By (Delegate):  Service Principal App User
  • Modified By (Delegate):  Service Principal App User
  • Owner:  Susan Human

But instead, here's what I see:

  • Created By:  Service Principal App User
  • Modified By:  Service Principal App User
  • Created By (Delegate):  
  • Modified By (Delegate):  
  • Owner:  Service Principal App User

I see this as a big problem.  The flow knows which user is triggering the flow - why know reflect that on the records in CDS?



Helpful resources

Process Advisor

Introducing Process Advisor

Check out the new Process Advisor community forum board!

MPA User Group

Welcome to the User Group Public Preview

Check out new user group experience and if you are a leader please create your group

MBAS on Demand

Microsoft Business Applications Summit sessions

On-demand access to all the great content presented by the product teams and community members! #MSBizAppsSummit #CommunityRocks

MBAS Attendee Badge

Claim Your Badge & Digital Swag!

Check out how to claim yours today!

Users online (34,065)