---
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


---

# Schedule incident retrieval

# Schedule incident retrieval {#ariaid-title1}

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

Set a schedule that determines how frequently Microsoft Defender incidents are pulled into SIR to ensure timely and efficient ingestion.

## Before you begin

Role required: sn_si.admin, sn_si.ingestion_profile_admin

## Procedure

1. If you aren't continuing from the previous section of the Filtering and Aggregation criteria, access the profile you're defining.
   1. Navigate to AllMicrosoft Defender IntegrationDefender Incident Profiles.
   2. Select the profile that you're continuing to define.
   3. Select Scheduling in the progress bar.
   {#ms-defender-schedule-inc__substeps_qbv_p2t_zfc}
2. On the form, fill in the fields.  
   {#ms-defender-schedule-inc__table_kyc_qbg_p4b__entry__2}

   | Field | Description |
   |-|-|
   | Ongoing incident ingestion | Option to set ongoing incident ingestion that the ServiceNow AI Platform instance pulls from the Microsoft tenant for new incidents. Security incidents are created if triggered incidents are found and the incident generation filtering criteria matches. |
   | Polling increment (minutes) | Polling frequency defined in minutes. |
   | Set incident ingestion time | Option to add Date and time for the initial ingestion. |
   | Input incident ingestion time | Date and time that you specify for the incident ingestion. |
   | One-Time Retrieval | Option to enable one-time retrieval of historical Microsoft Defender incidents and followed by the reconciliation of the data. When processing the data, both ongoing incidents and historical data are pulled. Note: The retrieved historical Microsoft Defender incidents undergo de-duplication checks to avoid any duplicates within the Security Incident Response application. |
   | Since date | The date since historical incidents were ingested from Microsoft. |
   [Table 1. Scheduling form]

   {#ms-defender-schedule-inc__table_kyc_qbg_p4b}

3. Select Continue.

## What to do next

[Automate incident updates and closures](https://servicenow-prod.fluidtopics.net/IZC2CN2hZ_UhDDl5YpQ2GQ "Automate incident updates and closures based on the incident status. The Microsoft Defender integration has a bi-directional interface that enables incidents to create security incidents and to update the incidents after the security incident is created or closed.")

*[\>]: and then