| 1 | --- |
| 2 | title: Office 365 |
| 3 | description: Ingest Microsoft 365 audit and sign-in telemetry, then visualize and alert on it in CoPilot. |
| 4 | --- |
| 5 | |
| 6 | ## What this integration is |
| 7 | |
| 8 | Office 365 (Microsoft 365) telemetry is typically **API-collected** audit/sign-in activity that becomes part of your tenant’s SIEM dataset. |
| 9 | |
| 10 | ## Data path (how it flows) |
| 11 | |
| 12 | **Typical flow:** |
| 13 | |
| 14 | 1. Microsoft 365 → **External Service integration** (API collector) |
| 15 | 2. Events → **SIEM storage** (Wazuh Indexer / OpenSearch-backed) |
| 16 | 3. Optional: events → **Graylog** alert definitions |
| 17 | 4. Alerts → `gl-events*` → **CoPilot Incident Management → Alerts** |
| 18 | 5. Operator workflow → **Cases** |
| 19 | |
| 20 | ## What data you get (high level) |
| 21 | |
| 22 | - Audit activity (user/admin activity) |
| 23 | - Authentication/sign-in related events (depending on collector scope) |
| 24 | |
| 25 | ## Setup (wireframe) |
| 26 | |
| 27 | - Configure Office 365 under **External Services / 3rd Party Integrations**. |
| 28 | - Ensure events are **tenant-aware** (associated with the correct customer). |
| 29 | |
| 30 | ## Success criteria |
| 31 | |
| 32 | - [ ] You can locate at least one **recent** Office 365 event in CoPilot |
| 33 | - [ ] The event is associated with the expected customer |
| 34 | |
| 35 | ## Dashboards |
| 36 | |
| 37 | After provisioning, CoPilot can deploy templated dashboards for supported integrations. |
| 38 | |
| 39 | - [ ] Confirm relevant Grafana dashboards for this customer are **populated** (not empty panels) |
| 40 | |
| 41 | ## Alerts (starter set) |
| 42 | |
| 43 | - Suspicious sign-ins (impossible travel / unfamiliar location, if available) |
| 44 | - Admin role changes |
| 45 | - Mailbox forwarding / inbox rule changes |
| 46 | - OAuth consent / suspicious app registrations (if available) |
| 47 | |
| 48 | ## Troubleshooting |
| 49 | |
| 50 | - Verify the external service/integration is connected and healthy |
| 51 | - Confirm customer code / tenant routing assumptions |
| 52 | - Validate the ingestion pipeline (collector → storage → CoPilot view) |