Forum Discussion
Retention Policy, email to Managers
The only way that what you describe should be possible is if the O365 is deleted, and deleted directly from the O365 portal, and the only way that is possible is if the account in in-cloud only, and not synced from AD.
If you disable an AD account which is synced to O365, the effect is that the O365 account is blocked from signing in.
If you delete an AD account which is synced to O365, the effect is that the O365 account is moved from Active Users to Deleted Users, the licence is removed and the user will be purged after 30 days.
If you delete an O365 cloud only account from the O365 portal, it will result in the behaviour that you are referring to. This is the only way to trigger this behaviour currently.
Hi, this will not happen when you disable the O365 user, but when you delete it. It gives you the option to convert the mailbox to shared and assign delegate access, and also informs the nominated users that they have 30 day access to the deleted users OneDrive. This only works for cloud only accounts however, not for AD synced accounts.
Hi Peter, and thanks for answering. Ii this really the only way? like i mentioned above, we never delete any AD user , we disable them and move them to Disabled OU, and we convert the email from O365 to shared manually. Im asking this because i know that one manager one time he received the email with the One Drive link , and im not sure what we did different.
The only way that what you describe should be possible is if the O365 is deleted, and deleted directly from the O365 portal, and the only way that is possible is if the account in in-cloud only, and not synced from AD.
If you disable an AD account which is synced to O365, the effect is that the O365 account is blocked from signing in.
If you delete an AD account which is synced to O365, the effect is that the O365 account is moved from Active Users to Deleted Users, the licence is removed and the user will be purged after 30 days.
If you delete an O365 cloud only account from the O365 portal, it will result in the behaviour that you are referring to. This is the only way to trigger this behaviour currently.
Thanks Peter, i think i should improve or adequate our termination procedures to O365 methods. I will do some testing and then implement it ,thank you very much.
