A user profile may have an attribute updated in a profile sourcing application and deactivated or suspended at the same time. When the profile is imported from the application to Okta, the Okta User profile is only deactivated or suspended while the attribute has not updated.

• Active Directory
• Workday
• Profile Sourcing

This is the expected behavior since the deactivation phase of an import process in Okta occurs prior to the attribute update phase. In this scenario, Okta will only deactivate, suspend, or remove the assignment for the user (depending on the lifecycle sourcing configuration).

Split the user's profile updates into two imports. The first import will be any attribute change, and the second import will be the status change, like deactivating the user. For example, if the email attribute should be updated before deactivating the Okta User profile, follow the steps below:

1. The user needs to remain active in the profile source application.

2. Update the email attribute in the profile source application.

3. Run an import from the profile source application to Okta.

4. Confirm that the email attribute is imported.

5. Deactivate the user in the profile source application.

6. Run import from the profile source application to Okta.

7. Confirm the user has the email attribute updated and the profile is deactivated.