User17375907550938883031 (Customer) asked a question.
In the Provisioning tab of an app, there is a "Deactivate Users" setting that ensures that users that are deactivated in Okta going forward are also deactivated in the app.
However, we have a customer that didn't have this enabled for a while, so they now have users that are deactivated in Okta but are still active in the app. How can we reflect those deactivations in the app? The setting only applies going forward and doesn't affect users that are already deactivated in Okta.
I've read this help article that confirms that the setting only applies going forward: https://support.okta.com/help/s/article/provisioning-deactivate-users-button-deactivate-just-new-deactivated-unassigned-users?language=en_US
If there is a workflow connection for this I would suggest writing a flow that gets that list of users, whatever your criteria is, and then deactivates them in the downstream application. Other than that you can see if there is an API and do something similar either in workflows (you can make api calls directly by constructing the API connector cards) or you will have to use a csv or whatever other mechanism is supported by the downstream application.