Hi @Renat Khamzin , ADFS only passes the ADFS Password Change URL in the Saml token to Entra if:
- The relevant claimrule is configured
- Password portal is enabled in ADFS
- The user's password in Active Directory is within 14 days of expiry
Assuming a user signed into their device for the first time, their password is still valid for more than 14 days. ADFS would not emit the URL. In that case Entra passes the Entra Password Portal URL to the device
The device caches this information and will load Entra Password Portal when the user invokes a PWD change on the device.
Eventually the user may perform a password logon when their password is closing in on the 14 days expiry mark.
The user performs password auth and ADFS adds the URL to the token. Entra will then pass down the ADFS Password Portal URL as part of the PRT. At this time the device updates the cached info and offers the ADFS Portal the next time when attempting a PWD change
Note:
Users that use WHFB for logging into Windows or are on staged rollout for managed auth will rather get the Entra Password Portal because Entra would be the primary authentication authority.
Going forward, for security reasons we would rather recommend to use Entra SSPR with Password Writeback for a number of reasons.
Here's a brief comparison of functionality:
Change Password | Reset Password | supports SmartLockout | MFA Protection | |
---|---|---|---|---|
Change Password | Reset Password | supports SmartLockout | MFA Protection | |
ADFS Password Portal | ![]() |
![]() |
![]() |
![]() |
Entra SSPR | ![]() |
![]() |
![]() |
![]() |
Besides the Security benefits sticking with one PWD change portal adds to more consistency in the user experience.
Please let me know if you have any questions and I can help you further.
If this answer helps you please mark "Accept Answer" so other users can reference it.
Thank you,
James