<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D50Z00008G7UxPSAVOkta Classic EngineLifecycle ManagementAnswered2024-04-17T12:26:53.000Z2017-07-20T16:57:25.000Z2017-07-20T16:57:25.000Z
  • justin.bergez (Regional Customer Success, Bay Area)

    Hi Matt,

     

    What you described above is the expected behavior when deprovisioning an app. The deprovisioning tasks that show up in the dashboard are dependent on the API call Okta gets back from the target app.

     

    Users are automatically deprovisioned from supported apps when their account is deactivated in AD or Okta. If you have apps with provisioning enabled, you can turn off the "Deactivate Users" feature from the Provisioning tab.

     

    If you feel like this could use a bit more clarity on either side, I would suggest opening a ticket with the Okta Support team and try to get someone on the phone to ensure you get the answers you're looking for. Our engineers are available 24/7/365.
    Expand Post
This question is closed.
Loading
Is there a way to only create deprovisioning tasks for specific apps?