2

Is it possible to update the AzureAD user's SignInNames using Powershell ? I tried to update it but it doesn't work out and gives a Bad Request error. No specific error is given. enter image description here

Let me know if that is possible! Thanks!

Rocket Singh
  • 469
  • 1
  • 10
  • 22
  • Is the `creationType` of your b2c account is `LocalAccount`? – Joy Wang Sep 27 '18 at 09:59
  • @JoyWang I am not sure what that property really means. When the user was originally created, it didnt had any SignInNames property set. But now we want to set the SignInNames property of all the existing users. But I do see this error – Rocket Singh Sep 27 '18 at 10:30
  • @JoyWang Yes I have set the creationType prroperty to "LocalAccount" but it still doesn't work – Rocket Singh Sep 27 '18 at 10:45
  • My account `creationType` is null, I got an error said my account `creationType` is invaild, when I new a user via powershell, also got bad request. – Joy Wang Sep 27 '18 at 10:49
  • 1
    According to the [AAD graph](https://msdn.microsoft.com/en-us/library/azure/ad/graph/api/entity-and-complex-type-reference#user-entity), the `signInNames` could not be set after creating the account, may be it also could not be set via powershell, because if you catch the request of the powershell via fiddler, it essentially call the AAD graph api, too. – Joy Wang Sep 27 '18 at 10:54
  • Woowww.. I love Microsoft :P – Rocket Singh Sep 27 '18 at 11:25
  • 1
    Do you think my comment is helpful? If so, I will add an answer. – Joy Wang Sep 27 '18 at 11:36
  • Thanks @JoyWang :) – Rocket Singh Sep 27 '18 at 11:40
  • Have added an answer, may be you could accept it. – Joy Wang Sep 27 '18 at 11:50

1 Answers1

0

According to the AAD graph, the signInNames could not be set after creating the account, may be it also could not be set via powershell, because if you catch the request of the powershell via fiddler, it essentially call the AAD graph api, too.

Joy Wang
  • 39,905
  • 3
  • 30
  • 54