Forum Discussion

KirillOdinets's avatar
KirillOdinets
Regular Visitor
6 months ago
Solved

Sync delete task for user

Hi,

Not sure if anyone noticed it, but i tested users sync from Entra/Azure to Goto Organization and Admin panel
And when new user is created - provision sends data about user to goto, and user is created

But when i remove user from the "sync group" or even delete the user, and then try to sync, it says below on the action that has been processed.

But on the Organization and Admin panel side user persists.

 

And when i run the provision again in Entra, i see the delete task was actually sent to Goto, but nothing then was removed up there as i mentioned.



And when i run the User sync in the Admin panel in goto afterwards, i see also that nothing changed

 

Can anyone suggest what is going wrong in here?

 

  • GlennD's avatar
    GlennD
    6 months ago

    At this time, inventory tracking is done manually.

6 Replies

  • GlennD's avatar
    GlennD
    GoTo Manager
    6 months ago

    At this time, inventory tracking is done manually.

  • KirillOdinets's avatar
    KirillOdinets
    Regular Visitor
    6 months ago

    How then it is represented in the inventory list while user is assigned to specific inventory item, how do i know which user was then suspended and so i would be sure of the items given to the user that has left that should be returned? I want to understand how it is handled

  • KirillOdinets's avatar
    KirillOdinets
    Regular Visitor
    6 months ago

    Thanks for the info!

    But then how it is then mirrrored into the inventory list? How should i track which inventory items were assigned to the users that were suspended?

     

  • GlennD's avatar
    GlennD
    GoTo Manager
    6 months ago

    KirillOdinets​ When users are removed from the sync group in Entra/Azure, they are not deleted from the GoTo Organization or Admin panel after syncing. Instead, their product entitlements are revoked, and their account status is updated to "Suspended." This approach ensures the user is no longer active while retaining a record in the system for administrative purposes.