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(265.6, 68%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EFN%3C/text%3E%3C/svg%3E)
I'm using the .Net Microsoft Graph SDK. When users want to reset their password I call the following method:
client.Me.ChangePassword(current_password, repeat_new_password).Request().PostAsync();
The change is successful and user can sign in with their new password.
Only the new password doesn't work on-premise. After some research I found that the Password Writeback service is not triggered.
When users change their password trough the Office 365 portal it works just fine.
It this by design or should the password writeback be triggered when using the Graph API ChangePassword method?
That's pretty much the same as with admin-initiated password changes, and is not supported. Read here: https://learn.microsoft.com/en-us/azure/active-directory/authentication/concept-sspr-writeback#unsupported-writeback-operations
![](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(278.4, 57.00000000000001%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESS%3C/text%3E%3C/svg%3E)
Hello anonymous user ,
Password Write-back to on-premise from azure is done via Azure AD connect . It also requires Azure AD premium license to be associated for the user on the tenant. While configuring the Azure AD connect the Azure AD Administrator in your organisation can enable Password writeback to the on-premise domain if they have Azure AD premium license associated with the azure AD tenant. The password writeback is an internal operation and not exposed through any API. Azure AD connect runs a thread for password writeback and it automatically updates from azure whenever a password is changed. The service is polled every 2 minutes or so to get any changes in password. You will not be able to get this done programmatically through Graph API as of now. The password writeback must be triggered on Azure Side and then the Azure AD connect will poll that change.
Hope this clarifies your queries. In case the information provided in any of the posts helps you , please do mark it as answer so that its helpful for other members of the community. If you have any residual queries , please let us know and we will be happy to help .
Thank you.
Thanks for the quick answer @Shashi Shailaj ,
I understand the prerequisites and the configuration that are needed. This is all in place and configured.
I also understand that I've no access to the Password Write-back function operation trough an API or something else.
What I don't understand is that when a user changes his password with a Graph API call it is not seen as a change.
Like you said
Azure AD connect runs a thread for password writeback and it automatically updates from azure whenever a password is changed.
The password is changed when you change it trough the Graph API but the Password Writeback isn't triggered. What is the difference when changing it trough the Office 365 portal?