07-24-2019 09:35 AM
07-24-2019 09:35 AM
1. Perhaps two years ago, I created a user f...@...law.com. The organizational structure changed, and I deleted that object about a year ago. It no longer appears under Users or Deleted Users in AAD, Exchange, or O365.
2. That user was an external. Their own e-mail address was f...@...ler.com. That was entered into AAD in the course of creating the user in my network.
3. I recently tried to share a SPO document with the person. I shared it to f...@...ler.com. The attached error message came back.
4. Somehow the f...@...law.com object still exists and is interfering with this person's ability to authenticate. (FWIW, this person has an O365 account from their own organization.) The object is not visible from any user or deleted user list in any of the ID management portals (Exchange, AAD, O365).
Q: How can I wipe this persistent user ID, and presumably the others that were created and deleted around the same time, from my system?
07-24-2019 09:57 AM
What you are showing on the screenshot is a sharing link to a SPO/ODFB file. Previously, SPO used their own method for sharing with external people, which is now converged with the B2B functionality of Azure AD. So this might be some artifact of the old method. You can try removing permissions from the file, then re-sharing it, and to be on the safe side maybe also check the permissions for the document library where the file is stored.
07-24-2019 12:18 PM
@Vasil Michev wrote:
You can try removing permissions from the file, then re-sharing it, and to be on the safe side maybe also check the permissions for the document library where the file is stored.
Thanks. I will do all those things, but I'm still concerned that somewhere in the system there is an object tied to a deleted user. The external referred to in my post and the sharing image is just one of several external users who were created around the same time and deleted around the same time. It is likely I will need to share with one of the others at some point, so I'm concerned with fixing the underlying problem, as well finding a fix for the sharing problem. Any idea of where that old userID object could still be living?