Troubleshooting Microsoft Graph Security API integration
-
- UpdatedFeb 1, 2024
- 2 minutes to read
- Washington DC
- Security Incident Response integrations
This section covers important troubleshooting tips and frequently asked questions related to the Microsoft Graph Security API alert ingestion integration.
- Integration run: When a scheduled job starts executing, an integration
run record with logs, errors, and warnings is displayed. The number of alerts pulled and the
number of incidents created in a scheduled job run are also displayed. Users with the
sn_si.analyst
role can see if any errors/profiles pulling failed during the integration run. Users with thesn_si.analyst
role can check thesn_event_ingestion_integration_run
table for any errors that have occurred. To troubleshoot any integration issues, you must first check the integration run. Errors are logged as worknotes in the integration run records for every scheduled job run. - Incomplete profile: While configuring the profile, in the Additional Options (Automate alert updates and closure based on SIR incident status) section, you must click the Finish button to ensure that the profile is moved to Waiting state indicating that it is waiting for ingestion.
- Validate profile: To validate if the integration is working correctly, check the profile states, last pulled date of profile, alert import table, alert to task table records.
- SSL issues: When connecting through the Microsoft Graph Security API, ensure that the instance has a valid CA certificate which has not expired. You can import RSA or your own certificates into the platform and ensure that the common name of the certificate matches host name. See KB0778285 for details.