How Provisioning To Active Directory Works
In brief
The documentation now specifies that password writeback isn't available for users created in Microsoft Entra. These users can authenticate to Kerberos-based applications only through passwordless authentication using the provisioned AD account.
What Entra admins need to know
Administrators should account for this limitation when planning authentication for provisioned users.
This editorial summary was generated by AI from the documentation changes. Verify important details in the full Microsoft Learn article.
Documentation change
The comparison below shows only the changed extract. Use the full-page view for complete context.
Password writeback
Password writeback, which synchronizes password changes in Microsoft Entra ID to the matched AD account, isn't available.available for users created in Microsoft Entra. Users accesswill only be able to authenticate to Kerberos-based applicationsapplications, through passwordless authentication using the AD account that provisioning creates. For more information, see How cloud-managed users sign in to the application.
Sync frequency
@@ -152,7 +152,7 @@ Delete behavior depends on the object type and lifecycle event. AD user accounts ## Password writeback -Password writeback, which synchronizes password changes in Microsoft Entra ID to the matched AD account, isn't available. Users access Kerberos-based applications through passwordless authentication using the AD account that provisioning creates.+Password writeback, which synchronizes password changes in Microsoft Entra ID to the matched AD account, isn't available for users created in Microsoft Entra. Users will only be able to authenticate to Kerberos-based applications, through passwordless authentication using the AD account that provisioning creates. For more information, see [How cloud-managed users sign in to the application](tutorial-users-groups-provisioning-walkthrough.md#how-cloud-managed-users-sign-in-to-the-application). ## Sync frequency 