I've been running into issues with the Compliance Search Purge lately. Whenever there's a nasty phishing attack, I usually yank those messages out of users' inboxes. However, I've noticed that the compliance search and purge functionality just isn't working anymore. The search part seems fine and it works through both PowerShell and the Purview web GUI, returning the correct number of hits.
I'm running commands like `New-ComplianceSearch -name $name -ContentMatchQuery $query -ExchangeLocation ALL` followed by `Start-ComplianceSearch`. That part goes smoothly, but when I try to purge with `New-ComplianceSearchAction -searchname $name -purge -purgetype SoftDelete`, it says it's successful immediately, but nothing actually gets deleted.
This setup has been reliable for me for about four years until this past summer. The advanced hunting tool isn't cutting it with its limits on how many it can delete, and ZAP is way too slow. Has anyone else been experiencing similar issues?
3 Answers
I've run some tests recently, and it seems like the command does report as completed very quickly now, which is definitely suspicious. In the past, you could see a process time that usually took about 20 minutes from start to finish. I've also tried reporting samples to ZAP without success, and the limitations in advanced hunting are just driving me nuts. I wish there was a straightforward purge button in the message trace because this current setup just isn’t cutting it!
Yep, I just started encountering this issue too. I reported it to Microsoft but haven't gotten any feedback yet. It's frustrating because this is exactly when I need it the most!
You're definitely not alone! I've been dealing with the same problem ever since they migrated everything to the new Purview portal. It seems like now you have to do the search, preview, and purge all via PowerShell, which is quite the hassle. The preview feature got messed up too; it requires a flag to enable search only sessions. It's been a frustrating change—used to manage everything smoothly through the GUI, and now it just feels convoluted. Ugh, Microsoft!
Totally get what you're saying. I noticed the same thing—had to shuffle between PowerShell and the GUI just to get everything done now. It's like they made it more complicated for no good reason.
Right? It's absurd that there are so many areas to manage these issues but no simple way to execute a purge. Having to go back and forth is really hindering the whole process!