A cloud-based service included in Microsoft 365, delivering scalable messaging and collaboration features with simplified management and automatic updates.
Hi Nurhaziq Adi
As far as I know, the ValidationException happens because the mailbox is still treated as being under a hold state. A hold is designed to preserve mailbox content for compliance/legal purposes until the hold is removed, so deletion workflows can be restricted while that hold state remains.
In hybrid scenarios, if the mailbox was originally synchronized from Exchange Server 2019 and the on‑premises AD object has already been deleted, it can leave the cloud mailbox in a “soft-deleted but held” condition where the hold can’t be cleanly managed through the original directory object.
Technically, you can try the below approach to see if it can help you:
- Confirm the mailbox is in the expected deletion state (inactive vs soft-deleted) and review hold-related settings.
- If any holds can be removed through normal administrative controls, remove them first, because holds are intended to preserve content until they are cleared.
Hope my answer will help you
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.