Monitoring connections and integrations

A connected source lets a request search your live systems rather than only what someone has uploaded by hand. Connections do not stay healthy on their own: consent gets withdrawn, licenses change, tenants get reconfigured. This article covers where to check.

How to check a connection

1. Go to Settings, then Integrations.

2. Find the integration you want to check.

3. The card shows its current state, and how much it has indexed where that applies.

4. Open it to see the connection detail and, where a connection has failed, the reason.

Why the failure state matters

A failed connection is reported on this screen rather than returning empty search results.

That distinction is the whole point. If a broken connection returned nothing, an officer would read "no responsive records" and close a request on the strength of a search that never ran. Because failure is reported as failure, an empty result means nothing matched.

Take that seriously in both directions: an empty result is evidence, and it is only evidence if the connection was healthy when the search ran.

What is connected today

Microsoft Purview eDiscovery searches your Microsoft 365 tenant, including mail and files. Microsoft 365 connects an individual account.

Integrations marked SOON are not yet available, including SharePoint, Google Drive, outbound SMTP, single sign-on, webhooks and API keys.

Things that break a working connection

• Consent withdrawn. The admin consent granted at setup can be revoked in Microsoft 365 without anyone telling Govflo.

• License changes. Purview eDiscovery has to remain available on the tenant's license.

• Tenant reconfiguration. Directory or security changes on your side can invalidate the connection.

Check the connection before a large discovery run rather than after it. Finding out a search did not run is much cheaper before you have relied on the result.