Unanswered

Action 'Create_user' failed, Invalid value specified for property 'mailNickname' of resource 'User'.

(0) Share

Report

Posted on by VikasNagaraj

318

I am trying to create a onboarding process, i have a flow to create AD account for new joiner. The flow was working fine few days back but now i get this error Invalid value specified for property 'mailNickname' of resource 'User'.

Here is the picture of the flow.

My company uses First name and first letter of last name for email address, so i am using toUpper(substring(triggerBody()?['LastName'],0,1)) to achieve this.

Please help!

Categories:

Building flows

I have the same question (0)

All responses (12)

Answers (1)

ChristianAbata 8,951 Most Valuable Professional on at

Like (0)

Report

Maybe the nick name is being empty @VikasNagaraj

Was this reply helpful? Yes No
Verified answer

v-bofeng-msft on at

Like (1)

Report
Hi @VikasNagaraj :

As the error message indicates the provided mail alias name is not in correct format or it includes invalid special characters. So try the below cases to fix this problem.

Remove white spaces in mailNickname (mail alias, email address).

Remove special characters in mailNickname (Ex: Space and “(),:;<>@[]).

I think this link will help you a lot:

Fix : BadRequest – Invalid value specified for property ‘mailNickname’ of resource ‘User’

Best Regards,

Bof

Was this reply helpful? Yes No
VikasNagaraj 318 on at

Like (0)

Report

@v-bofeng-msft
I managed to figure it out, it was the space issue. if there are space or any special character it gives a error. Thank you
I have one more issue i have posted it last week, will be really helpfull for me, please help me solve it.
https://powerusers.microsoft.com/t5/Building-Flows/Condition-help-for-onboarding-process/m-p/1490235#M166547

Was this reply helpful? Yes No
Biaigo 6 on at

Like (0)

Report

Just to make sure I understand what you said, because I'm having a problem with it. The MailNickname is an email address, but you can't use the '@' ??

Was this reply helpful? Yes No
VikasNagaraj 318 on at

Like (0)

Report

@Biaigo
Hi, i had this error because one of my managers gave a space after entering the email id. so make sure there is no space before or after when they enter it in sharepoint, if there is a space the the flow wont run.

Was this reply helpful? Yes No
Biaigo 6 on at

Like (0)

Report

Vikas- that was my issue. I wrapped my expression in a trim and it started working again.

Was this reply helpful? Yes No
jguzmanlozada 27 on at

Like (1)

Report

Greetings @VikasNagaraj and everyone from the tread!

I am experiencing this exact same issue and I would hate to create a new case. I revised the resolution and I am making sure there are no spaces nor special characters. To test that, I've tried entering the email plain, with no quotes but also wrapped it like "test.user@mydomain.com" and even 'test.user@mydomain.com' but the flow always fails with "Invalid value specified for property 'mailNickname' of resource 'User'."

I did a sample run to show how my form is filled and how its shown on my flow:

Form:

Flow showing data from form:
If I remove the Azure AD creation step, the flow works as it has some email notifications and affects an excel table. But I want to create the user with no avail.

Thanks in advance!
JG

Was this reply helpful? Yes No
kurthutchinson 3 on at

Like (0)

Report

I can't figure this out either. As you can see the way I'm passing mailnickname should be correct as well.

Was this reply helpful? Yes No
VikasNagaraj 318 on at

Like (0)

Report

@jguzmanlozada & @kurthutchinson
Could you please put a screenshot of your flow?

Was this reply helpful? Yes No
CoachOffice365 63 on at

Like (1)

Report

I also don't understand how to fix the error "Invalid value specified for property 'mailNickname' of resource 'User'." Would it be possible to completely remove the @-sign (as it is the culprit of my erroneous flow, I believe)? Or is it still needed for some function? What is the field 'mailNickname' even used for? Does anybody know?

Was this reply helpful? Yes No