---
sourceDocument: Australia Security Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/security-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Security Management

ft:clusterId :

    - security

bundleId :

    - security

workflow :

    - Technology


---

# Troubleshoot

# Troubleshooting Microsoft Graph Security API integration {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

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 the `sn_si.analyst` role can check the `sn_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](https://servicenow-prod.fluidtopics.net/0FN~EzIxaNfTCYcJ5WGzyw "The Microsoft Graph Security API alert ingestion integration has a bi-directional interface that allows for both alerts to create security incidents, as well as an ability to update the alerts once the security incident is created and/or closed with relevant incident details such as SIR incident number, assignment group, SIR incident URL, and so on. T")) 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](https://support.servicenow.com/kb_view.do?sysparm_article=KB0778285) for details.
{#ms-graph-trouble__ul_vzy_n1d_nlb}

