This walk-through will help you get Microsoft 365 (formerly known as Office 365) integrated with Perch. Follow these steps and you’ll be ingesting logs like a pro.
To start collecting logs from Microsoft 365, Perch needs to verify that the Microsoft 365 instance has logs and that we’re able to ingest them properly.
As per Microsoft, there is no guaranteed maximum latency for notification delivery (in other words, there’s no SLA). Microsoft Support’s experience has been that most notifications are sent within one hour of the event. Often, the latency is much shorter, but it can occasionally be longer as well. This varies somewhat from workload to workload, but a general rule is that most notifications will be delivered within 24 hours of the originating event.
If at any time after setup you feel the need to test that your Microsoft 365 integration is still working as expected, simply click the Test button again.
Like all Perch integrations, you can enable or disable Microsoft 365 log ingestion at any time by toggling the switch from OFF (gray) to ON ( purple ), or the other way around, in the Perch app.
When disabling Microsoft 365 log ingestion, your configuration is preserved, so you won’t have to reauthorize Perch when you re-enable it.
Microsoft 365 subscribes to these feeds:
Perch supports all generally available Microsoft 365 plans with GCC support currently in the works.
Still having trouble? Reach out to one or our specialists at firstname.lastname@example.org