This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(291.2, 61%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EO9%3C/text%3E%3C/svg%3E)
Account synced from onprem ad.
I update user using graph api as Azure AD application to update user properties. Permissions are all User.ReadWrite.All, Directory.ReadWrite.All listed in the document.
Password, mobile phone, business phone, and accountenabled are all not set. The properties to include in the modification are as follows:
usageLocation, userPrincipalName, mailNickname
However, an error occurs in the efficient privileges to complete the operation (403). But if you try again over time, it succeed.
Do you know why it happens??
Hi @Heo Jaehyun
This may be caused by delay, please do not try to get an access token immediately after you grant permissions and admin consent, it may take some time for the permissions to take effect, please wait half a minute or so and try again.
Also, note that you must be an administrator to modify other users' information.
Hope this helps.
If the reply is helpful, please click Accept Answer and kindly upvote it. If you have additional questions about this answer, please click Comment.
I don't got an access token immediately after grant permissions and admin consent. I received 204 response code before the error occurred. And if you try again a few days later, it returns an 403 response code. This situation repeats over and over again.
Hi @Heo Jaehyun
What authentication flow are you using? auth code flow or client credentials flow?
I used client credentials flow.
I used client credentials flow.
Hi @Heo Jaehyun
Does this error occur when you modify some specific user or when you modify the same user?
Hmm, yes, it happens when you modify for the same user.
At first, I thought it was caused by the expiration of the issued access token, but when the access token expires, it response 401 code.
403 errors are listed in the docs(https://learn.microsoft.com/en-us/graph/resolve-auth-errors), but not in any case. If the error continues to occur, I would think something is wrong, but I don't know the cause because success and failure are repeated.
Hi @Heo Jaehyun
Did you only modify the three basic attributes "usageLocation, userPrincipalName, mailNickname" for the same user?
Yes, I modified basic attributes. Additionally, this error does not occur frequently.