Forum Discussion
Question about Employee Terminations and shared documents in OD4B
The account was disabled in Active Directory on December 1 of 2015, not sure where else to check online to confirm whether or not everything terminated correctly, but don't have a reason to suspect it didnt.
We have an Exchange Transport Rule that cc's me whenever those OneDrive emails go out. For some unknown reason, the manager, nor I ever even received a termination email regarding OD4B for that particular user.
I questioned if maybe the manager field was blank for some reason near that date, but no one seems to think so.
They swear they could access the document very recently (and now I've got to come up with answers where there don't appear to be any). And of course it was a critical document, bleh...
Why is was in a user's OD4B is another matter......
- You mention that you disabled the account in December. The OneDrive cleanup job does not process disabled accounts, only deleted accounts. And - that is only if the account is deleted in AzureAD (in case you had some kind of sync issue not processing the delete).
Also - check what your tenant is set to for -OrphanedPersonalSitesRetentionPeriod (part of the Set-SPOTenant parameters) - the default is 30 days but it can go up to a whole year.
So OK...that's how it should work, but we also have a lot of examples where the OneDrive cleanup process doesn't work and we end up with a bunch of orphaned OneDrives - maybe that is what happened here as well. Or maybe it was just a case where an admin finally deleted the disabled account and kicked-off the deletion process a lot later than expected.- I've also seen cases where the creation and deletion of OneDrive sites has gotten "stuck" in the queue until someone noticed or a support call was opened. once someone on the Microsoft Operations team takes a look at the particular tenant the queue becomes "un-stuck" and OneDrives are created and deleted normally. As Adrian says I suspect that is what happened in your case. Someone finally hit the reset button in July and the site finally got deleted.
