Employee's send out emails with no subjects all the time, however I am unable to add a null/blank subject as a condition in content search.

I am also unable to content search or filter based off of message ID.

There is also no time option, only date, as a search condition.

This makes content searching for an email with no subject a huge pain.

Please add the ability to create content searches based off of blank/null subjects, sent time between X and Y, and based off of message ID in the mail headers as an option.

Operations from sc center that Copy eDiscovery search results to a discovery mailbox would be very useful.

This operation is available only in Exchange Management Center.
but we want to implement this operation in SC center too. Please consider this function.

I have scripted out the entire eDiscovery process in E3 eDiscovery which allowed us to save time and money, and repeat searches with minor variations very easily. With Advanced eDiscovery, I am unable to do so. Please add powershell scripting support (or provide the documentation) so we can streamline our collection and export processes.

Currently users with the ediscovery role can run search for content and download that content. Using the New-ComplianceSearchAction -purge -softdelete you can delete this content (which we use for deleting spam or malware emails out of mailboxes). We do not want our security operations team to use powershell to complete these deletes so we have to write a gui to provide this functionality. Please enable the ability to complete deletes within the SCC itself

I have a requirement from a large customer (85K users) that needs to be able to perform eDiscovery collections for specific Outlook folders. We can do date range and Full Mbx collections, but not specific folders. This was possible on-premises, but not in Exchange Online ????

Sensitive data searches for ediscovery currently work only in Sharepoint and One Drive. It also works for DLP in Exchange. This lack severely limits the usefulness of eDiscovery in Security and Compliance for Office 365.

Provide a mechanism to programmatically download the eDiscovery exports in Azure back to on-premise. Powershell cmdlets or command line parameters to existing eDiscovery download tool would suffice.

A keyword limit of 20 terms has recently been instituted in the Compliance Center eDiscovery searches. This limit is far too low and should be returned to an unlimited number of keywords (or at least a much higher limit like 100 keywords). This is negatively impacting the ability to do more complex searches in the Compliance Center.

Currently, performing a content search of OneDrives across a multi-geo environment isn't possible, it only searches the default Geo, not satellite Geos. If you create a security compliance filter targeted at your satellite geo and put the eDiscovery person in the role, then they can search that satellite geo. Please update oneDrive content search to search across geos the same way that an Exchange mailbox search works, without requiring adding/removing them from security compliance filters. (This workaround was the result of working with Microsoft Premier support, so it's legit.)

large e-discovery jobs keep failing due to wide scope. Could the tool autosplit the search into smaller jobs (smaller scope) and then recompile the result onto one report?

Currently, to export a mailbox as a PST file, you need to use a windows machine and use IE/Edge browser. You need to build out support for OSX and other browsers so businesses can use whatever hardware/software they use instead of only the one option.

Give the ability to review, remove, redact, and export to PDF all emails that are found in a discovery search to include the ability to convert and export attachments as PDF as well.

Add ability for compliance searches to search hyperlink URL and display text while supporting the existing wildcard structure available to other attributes like subject and body.

The new functionality could either be in a new attribute, or joined into the body attribute since the links would be in the body of the email.

Currently when we run an e-Discovery search through Compliance Management, it also shows emails that are in a user's Drafts folder. Since the emails were never sent to a recipient, we would like a feature that allows us to exclude emails in the Drafts folder that were never sent to a recipient.

Thanks!

If you have 150 to do its quite cumbersome to do it from the web console

When trying to exclude a SharePoint site from a retention policy in the new unified retention policy section, you have to be an admin of the SharePoint site. If you are not a site admin, when you try to FIND the site so it can be selected, it returns no site found. Support have verified this is not a bug and is the way this works at the moment, but for a company which is only giving access to sites to people who need it, this behaviour needs changing so that a O365 Global Admin/SharePoint Admin can lookup sites.

Currently there isn't a way to search for emails that were encrypted using OME. We need a way to identify that a message is encrypted. The use case it for intra-org encryption since the internal recipient would of received the email encrypted.

There is a mapi property on the message called content-class whose value of "rpmsg.message" identifies it was encrypted. Maybe that can be what is used as an option in the content search portion of eDiscovery.

ApplicationDataRoot folder and SubstrateFiles folder contained in exported PST files does not contain any data useful for auditors. eDiscovery managers should get an option to exclude those folders when exporting PST files via Contents Search.

When an export/download needs to be done in the Security & Compliance Center for a large mailbox due to being on litigation hold (e.g. 30+ GB), the download hangs at the end with just a few items left according to the progress bar. Repeated attempts are made and it still hangs. If I go to the Compliance Management area in the Exchange Admin Center, the data downloads without error. This needs to be fixed before the Compliance Management area in the EAC goes away in July 2017.