rencore.com (opens in a new tab) Start a trial (opens in a new tab)

Power Platform: the user cannot be created in Microsoft Dataverse

Last updated Scanning Power Apps Power Automate

AI summary

When a Power Platform scan cannot access flows because the consent account is not a member of the Dataverse environment's security group, ask an administrator to add it. The next scan will retrieve the missing flow details.

A Power Platform scan reports that the consent account cannot be added to a Dataverse environment because it is not a member of the environment’s security group. Rencore Governance skips the details of the affected flows, and the rest of the scan continues.

What you see

The error:

The user ‘{userId}’ cannot be created in Microsoft Dataverse because the account is not a member of group ‘{groupId}’. Please ask an administrator to add user to the group.

The message in Rencore Governance:

We encountered an issue while retrieving information about Flow from the tenant url {URL}. Please ask an administrator to add user to the group or refer to the documentation link for further information regarding the issue.

Why it happens

The Dataverse environment that stores the flow only allows members of a security group. The account used for the Power Platform consent is not a member, so Microsoft cannot add it to the environment. Rencore Governance skips the details of the affected flows, and the rest of the scan continues.

How to fix it

  1. Ask an administrator to add the consent account to the group named in the error.
  2. Wait for the next scan. It collects the missing flow details.

Frequently asked questions

Why does my Power Platform scan say the user cannot be created in Microsoft Dataverse?

The Dataverse environment that stores the flow only allows members of a security group. The account used for the Power Platform consent is not a member, so Microsoft cannot add it to the environment.

Does the scan stop when the consent account is not in the Dataverse security group?

No. Rencore Governance skips the details of the affected flows, and the rest of the scan continues.

How do I fix the Dataverse group membership error in a Power Platform scan?

Ask an administrator to add the consent account to the group named in the error. Then wait for the next scan, which collects the missing flow details.