Unanswered

'GraphUserDetailByEmailMultipleFound'. Error Message: 'Found multiple matching users for abc

(3) Share

Report

Posted on by Community Power Pla...

Hi there,

I get this error mentioned in the subject line for the Flow that is used for sending Approval. I have checked the O365 Admin and Azure AD user profile and there is just one primary email ID/ profile for the affected user name. Looking for suggestions, please.

Categories:

Building flows

I have the same question (0)

All responses (12)

Answers (0)

v-yuazh-msft on at

Like (1)

Report

Hi @ MB3,

Could you please share a screenshot of the configuration of your flow?

Which action would run failed with the error message that you provided?

Please share more details so we could provide a proper workaround for you.

Regards,
Alice Zhang

Was this reply helpful? Yes No
MartinM 13 on at

Like (5)

Report

Hi,

I got the same error suddenly.
I'm testing with a very simple, 1-step approval flow on files stored in a SharePoint library.
The name of the approver is taken from a field of the library.

The approval actions fails with the error message:
The request failed. Error code: 'GraphUserDetailByEmailMultipleFound'. Error Message: 'Found multiple matching users for ....

Any suggestions what could be wrong?

thx
Martin

Was this reply helpful? Yes No
agzertuche 14 on at

Like (5)

Report

I faced the same problem, but modifying the AD accounts to avoid this issue is not a solution for me.
So, what I end up doing was to assign the approval to the "Id" of the user instead of the "email", as follows:
1. Before the approval action, add a new Office365 "Get user profile" action to get the "Id" of the account, then look for the account using your approver email.
2. On the approval action, update the "Assign to" field to the outcome of the "Id" field from the previous action
3. Save and test the flow

Was this reply helpful? Yes No
siegard 2 on at

Like (0)

Report
Ok, I'm having the same error and I swear I've used your work around in the past but now I'm trying to re-create an old workflow I had and when I use the "ID" attribute I get this.

BadRequest. The request failed. Error code: 'InvalidApprovalRequestor'. Error Message: 'The approval requestor must be a single, valid user account within your organization.'.

Was this reply helpful? Yes No
QuentinY 5 on at

Like (0)

Report

Hello
I also encounter this issue, any idea of it

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

I tried this fix as "Get Manager" and "Get User Profile" as a step before the approval and it doesn't work. I get the error "Assign To" field must be an email. When I switch the assign to field to Mail from the Get User profile step it creates the exact same error again.
"BadRequest. The request failed. Error code: 'GraphUserDetailByEmailMultipleFound'. Error Message: 'Found multiple matching users"

Any help is appreciated.

Thanks

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

Invalid request error, after using 'ID' in the 'Assigned To' field.

Was this reply helpful? Yes No
QuentinY 5 on at

Like (0)

Report

The issue fixed on my side now. In my scenairo, fo work convincence, tagart user used to add his email address on another domain ID.(we seperate privilaged ID and normal user ID).
To make the email address unique, I use a dummy mail address to override one of ID. the issue fixed when I try it afte 24hrs.
Hope this would help.

Was this reply helpful? Yes No
kmw1130 988 on at

Like (0)

Report

I'm having the same issue, but when I look in Azure AD, I do not see any duplicates. It seems to be a sync issue. The error gave me two GUIDs "Found multiple matching users ('GUID #, GUID#') for first.last@site.com". Are these GUIDs from AD?

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

I'm still having the exact same issue and splitting off to a separate domain isn't an option. Does anyone have a working solution? I've even tried the Get User Profile and use the ID and it still results in the same error.

Was this reply helpful? Yes No