---
sourceDocument: Australia IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/it-operations-management

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Define and run discovery schedule

# Define and run discovery schedule {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

The discovery schedule is the control point for running discoveries. The schedule controls when discovery runs, defines the MID Server to use, the type of discovery that should run, and the IP addresses to query.

## Vorbereitungen

Role required: discovery_admin

## Prozedur

1. Navigate to AllCloud Provisioning and GovernanceCloud Admin Portal.  
   The Cloud Admin Portal opens in a new browser tab.
2. On the Cloud Admin Portal, navigate to ManageDiscovery Schedules.
3. Select Add New Schedule.
4. Fill in the details (by selecting the provider).  
   For more information on the field details, see [Create a new discovery schedule form reference](https://servicenow-prod.fluidtopics.net/kwlGUFTXh6W0thEPSQmNgQ "The Create a new discovery schedule form displays information related to the schedule and the target cloud provider. The Create a new discovery schedule form is available in the Cloud Discovery Workspace.").

   If the system can't detect an appropriate MID Server, you're prompted to configure a MID Server.
5. Select Next.  
   After the schedule runs, the system discovers resources from the org and org units linked to the AWS account or Azure tenant and management groups. The details are populated in the following tables:
   * cmdb_ci_cloud_org_list.do
   * For AWS: cmdb_ci_aws_org_unit_list.do
   * For Azure: cmdb_ci_azure_management_group
   {#define-run-discovery-schedule__ul_ydj_tqd_w1c}
{#define-run-discovery-schedule__steps_krl_vmc_w1c}