How to run eDiscovery Standard search content on Exchange Online

By Sai Kiran Pandrala · reviewed by Sai Kiran Pandrala, Editor Last verified: 2026-05-30

Why this matters

Run ediscovery standard search content on a Exchange Online device is one of the highest-volume how-to searches for the Microsoft 365 Admin category. Most users find the menu path inconsistent across Exchange Online model revisions, so this guide gives a generalised path plus model-specific notes.

Pre-requisites

• A Exchange Online device that's powered on and on the latest stable service version / OS.
• The Exchange Online companion app or management tool installed and signed in.
• 5-15 minutes uninterrupted.

Step-by-step

1. Locate the setting. Open settings on your Exchange Online device. For "run eDiscovery Standard search content", the option lives under one of: General, Advanced, Connectivity, Accessibility, or a Exchange Online-specific menu. Check the Exchange Online user manual for your exact model if you can't find it.
2. Toggle the feature on. Confirm the on-screen prompt.
3. Configure sub-options. Most features have 2-3 sub-options (mode, schedule, paired device). Pick values that match your real-world usage pattern.
4. Save / apply. Some Exchange Online models auto-save, others require an explicit Done / Save tap.
5. Test live. Trigger the feature in a real scenario to confirm the configuration is correct.

Tips that save time

• Pair this feature with a Exchange Online automation / routine if the device supports it.
• If the feature relies on cloud sync, give it 1-2 minutes after enabling to propagate.
• For multi-user households / multi-admin teams, set per-user profiles so each user sees their preferred state.

Common gotchas

• Feature greyed out, usually service version too old. Update + retry.
• Feature works once then stops: battery saver / power saver mode is killing the Exchange Online app process. Whitelist it.
• Feature works but with delay, usually cloud-sync latency; check internet speed and Exchange Online service status.

Region / variant notes

Some Exchange Online features are region-locked or only available on higher-tier SKUs. If your variant doesn't show "run eDiscovery Standard search content" at all, check the Exchange Online model spec sheet to confirm support.

Frequently asked questions

How long should the recovery / setup take?

For most Exchange Online Microsoft 365 Admin cases, allow 15-45 minutes the first time. Repeats are usually under 10 minutes once you know the menu path.

Will this exact procedure work on every Exchange Online model?

The procedure reflects current Exchange Online behaviour. Menu paths shift between service version generations; verify against the manual for your specific model + revision.

Is the procedure safe in production / live use?

Apply during a maintenance window where possible. Capture pre-change state. Exchange Online doesn't usually publish rollback procedures, so make sure you can restore manually.

Does this affect my Exchange Online support coverage?

Standard operation per the user manual + applying official service version updates does NOT void support coverage. Opening managed services, third-party repair, or unauthorised modifications can void support coverage. check before going further.

Related guides

• All Microsoft 365 Admin guides → /microsoft/section/microsoft_365_admin.html
• All Microsoft guides → /microsoft/

Related fixes

Related guides worth a look while you sort this one out:

• How to run eDiscovery Standard search content on Defender for Cloud Apps
• How to run eDiscovery Standard search content on Defender for Identity
• How to run eDiscovery Standard search content on Defender for Office 365
• How to run eDiscovery Standard search content on Defender XDR
• How to run eDiscovery Standard search content on Microsoft 365 admin center
• How to run eDiscovery Standard search content on Microsoft 365 Apps (deployment)

References

• Exchange Online official support portal for your model.
• Exchange Online community forum + Reddit threads.
• Vendor PSIRT / advisory page (where applicable).

Reference material, not professional advice. Validate with your vendor manual and follow local regulations.

Why this matters for your day-to-day

this device that's misbehaving costs more than the fix itself: lost productivity, missed calls, security risk, even safety risk in some categories. Treating the symptom quickly with a documented procedure is cheaper than letting it persist. The steps above are written to get you back to working in under an hour where possible, and to flag clearly when escalation is the right call.

Before you start

A few things to confirm so the unit fix goes cleanly:

• Latest service version downloaded if you're going to update.
• support coverage + support contract status checked, opening managed parts may void it.
• Backup of current configuration (where applicable) taken.
• Spare parts on hand if you anticipate replacement.
• Adequate workspace, lighting, and time: rushing causes regressions.

Quick verification

Before you walk away from this device fix, run through:

1. Reproduce the original trigger, does the issue reappear? 2. Check the device's status / health screen for any new alerts. 3. Confirm paired devices (app, hub, controller) reconnected. 4. Save / commit any configuration changes per the device's normal workflow. 5. Note the change in your maintenance log with date + service version version.

Escalation guide

For this unit, the right escalation depends on impact:

• Cosmetic / minor: log a ticket via the How app or web portal. Response 1-3 business days.
• Mid-impact: phone support. Have your serial number ready.
• Critical (production down, safety issue): in-person dealer / TAC visit. Bring proof of purchase.
• Out of support coverage: third-party repair shop with manufacturer-certified technicians.

More frequently asked questions

Will this void my support coverage?

Applying official service version updates and following the user manual will not affect support coverage. Opening managed services, jumping safety circuits, or using third-party parts can void support coverage in most jurisdictions.

Should I update service version first or last?

Update service version first if a release note specifically mentions your symptom. Otherwise, finish the troubleshooting flow first, then update; that way you can isolate whether the update or the underlying fix solved it.

What if the fix returns after a reboot?

Persistent fault returns mean either: a hardware fault (escalate), a configuration that's being overwritten by a sync source (check cloud profiles), or a regression in a recent service version update (rollback).

Can I roll this back if something breaks?

Yes for software-level changes (service version rollback, config rollback). Hardware changes are usually one-way. Always back up settings before starting.

Are there safer alternatives for non-technical users?

Yes. the manufacturer's self-service troubleshooter (HP Smart, LG ThinQ, Samsung Members, similar) usually walks through the same steps in a guided UI. Use that first if you're not comfortable with menu paths.

Field notes from real Microsoft 365 Admin incidents

When I work on run eDiscovery Standard search content on Exchange Online the rhythm I lean on is the one I have built over years of these tickets. Microsoft Graph PowerShell is the tool I now reach for over the legacy MSOnline module, because the legacy module's deprecation timeline is finally serious. Service Health is the first tab I open before I touch a single setting; half the M365 tickets I work on resolve themselves once I confirm Microsoft has already flagged the incident. Message Trace gives the truth that the user's Sent folder cannot, if a mail did not leave the org, it will say so in plain English.

Tools I actually reach for

For run eDiscovery Standard search content on Exchange Online on Exchange Online the cheapest signal I can land usually comes from MicrosoftTeams PowerShell module, then Microsoft 365 Apps admin center, Microsoft 365 admin center, Message Trace, Microsoft 365 Service Health dashboard when MicrosoftTeams PowerShell module cannot see the layer the fault sits in, and Exchange Online PowerShell for the cases where neither of those answers cleanly. That ordering is not academic. It matches the layers the failure tends to surface through, so the cheap signal lands first and the heavier tooling only comes out when the simpler answer does not hold up under scrutiny.

Verification I run before I close the ticket

Before I mark run eDiscovery Standard search content on Exchange Online resolved on a Exchange Online unit, the verification loop below is what I actually run. Each step proves a different layer is green, and the order matters - the cheap checks gate the more expensive ones.

Get-MgServicePrincipal -Filter "displayName eq 'Office 365 Management APIs'"

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

Connect-ExchangeOnline; Get-MessageTrace -StartDate (Get-Date).AddDays(-1)

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

az ad signed-in-user show  # for cross-check against Entra

Only when every line above runs clean do I close the ticket and update the runbook with the timestamps.

Where I check first when the docs disagree

When two sources contradict each other on a Microsoft 365 Admin detail, the disambiguation order I lean on is stable. I usually start at learn.microsoft.com/microsoft-365 for the ground-truth view on Microsoft 365 Admin. I usually start at admin.microsoft.com for the ground-truth view on Microsoft 365 Admin. I usually start at techcommunity.microsoft.com/category/microsoft365 for the ground-truth view on Microsoft 365 Admin. Random blog posts and reseller wikis are signal, not ground truth, and I treat them as such until the references above either confirm or contradict the claim.

Pitfalls I have walked into on this exact path

The shortcuts that look smart on run eDiscovery Standard search content on Exchange Online have a habit of biting back. The pitfalls below are the ones I have personally walked into on a Exchange Online unit, not things I read about. Microsoft Graph PowerShell is the tool I now reach for over the legacy MSOnline module, because the legacy module's deprecation timeline is finally serious. Message Trace gives the truth that the user's Sent folder cannot: if a mail did not leave the org, it will say so in plain English. When in doubt I revert to the slower path that the manual prescribes - the time I save by skipping it is always smaller than the time I spend cleaning up afterwards.

What I tell the next on-call

When I hand run eDiscovery Standard search content on Exchange Online off to the next person on rotation, the three lines I leave in the runbook are these. First, the symptom signature for Exchange Online on the Microsoft 365 Admin family - not a paraphrase, the exact string that surfaces. Second, the diagnostic that gave the highest signal in the least time. Third, the exact verification command whose green output justified closing the ticket. That trio is what turns a one-off fix into a runbook entry the next engineer can use without paging me at three in the morning.

I also add a one-line note on the cost of getting this wrong. For run eDiscovery Standard search content on Exchange Online on a Exchange Online unit, the cost is rarely the replacement part. It is the downtime, the second site visit, and the trust deficit you spend with whoever owns the asset when the fix does not hold. That framing keeps the next on-call from choosing the cheap-looking shortcut that ends up costing the most in elapsed hours and goodwill.