The issue is caused by the Power Query Dataflows trigger, which performs a stricter ownership + licensing validation than most other connectors.
When the flow is turned on, Power Platform calls an internal check (BapListServicePlans) to verify that the flow owner exists in Dataverse and has valid service plan/licensing details. In your case, that lookup fails, leading to:
MissingUserDetails
This typically happens when the owner is a user/service account that is:
- Not properly provisioned in the environment, or
- Missing/changed licensing or Dataverse user mapping
Other connectors (like SharePoint or Dataverse actions) don’t trigger this validation at activation, which is why they work normally.
Why it work before
The owner likely had a valid Dataverse record and license earlier, but that mapping became invalid over time (license change, cleanup, or sync issue).
Switching to an Application User (service principal) fixes it because:
- It has a stable identity in Dataverse
- It is not affected by user licensing changes
- It avoids “missing user details” validation failures
For managed solutions across environments, use:
👉 Application User as flow owner + connection identity
This ensures consistent behavior across DEV / TEST / PROD and avoids user-based licensing and provisioning issues.
Vishnu WR
Please ✅ Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider answering Yes to Was this reply helpful? or give it a Like ♥
