NickT.68327 (Customer) asked a question.
I have locked a user on the AD side, but this lock is not reflected in okta, the user still shows "active" in okta, not "locked out". I have tried an incr and a full import to see if any change but the user remains active in okta.

Hey Nicholas,
I am hoping its AD mastered user on which you are trying. Are you manually locking the user or by unsuccessful sign-on attempts. Lock out depends on the AD password policy configured in OKATA. You may check the "Lock out user after X unsuccessful attempts" in password policy - (Security > Authentication > Password > Active Directory Policy). More details on below link -
https://support.okta.com/help/s/article/How-does-the-password-policy-soft-lock-functionality-work?_ga=2.20827000.178653873.1594077558-499733930.1589287835
Thanks,
Saurabh
Have you checked the Account locked attribute matches with the AD attribute name ? This is a very common use case & should work. check your configuration, you might be missing a small thing.
Yeah, this is kind of the next step following my comment in your other thread @NickT.68327 (Customer)
Unless the lockout attribute from AD is mapped to a similar Okta attribute that governs the status, a lockout in AD won't automatically propagate to a lockout in Okta. You can either ensure that attribute is mapped, as @sandeepk.84743 (Wipro Technologies) suggests, or take the approach I mentioned previously: delegated authentication, where since authentication to Okta happens at AD a lockout status i AD will effectively prevent authentication to Okta.
Sandeep - do you have the attribute name on the Okta side? Is this a custom attribute you need to create before adding the mapping?
You can create a custom Boolean attribute in OKTA & map it to the AD Attribute. Custom attribute is the only best option. There is no default attribute available in OKTA.