---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Create an OCI Discovery schedule in Discovery Admin Workspace

# Create an OCI Discovery schedule in Discovery Admin Workspace {#ariaid-title1}

* Release version: Yokohama
* 
* Updated July 27, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read

Use the Discovery Admin Workspace dashboard to create an Oracle Cloud Infrastructure (OCI) Discovery schedule.

## Before you begin

Verify the following:

* You have at least one validated MID Server with a status of Up. The MID Server must reach the IP ranges that you intend to discover. You can install the MID Server by using [Use MID Server guided setup](https://www.servicenow.com/docs/access?context=use-mid-server-guidedsetup&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US) or by manually downloading and running the installer. For details, see the MID Server installation instructions for [Linux](https://www.servicenow.com/docs/access?context=t_InstallAMIDServerOnLinux&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US) and [Windows](https://www.servicenow.com/docs/access?context=mid-server-install-prereqs&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US).
* The MID Server used for Cloud Discovery is configured with the Cloud Management capability.
* Configure an OCI user in the Oracle Cloud console with an API signing key and the required Identity and Access Management (IAM) policies. This grants the MID Server access to the cloud resources you plan to discover.
* You have created a suitable OCI API credentials in the ServiceNow AI Platform to connect with the OCI user you want to use for discovery. For more information, see [Create Oracle API credentials](https://servicenow-prod.fluidtopics.net/O_bSlsJbW12~eKeDqOEz0g "Create Oracle API credentials on the ServiceNow AI Platform to enable access to your Oracle resources during Oracle discovery.").
* You're using Discovery Admin Workspace v1.13.0 or later.
{#create-oci-schedule-DAW__ul_lzn_tsj_jhc}

Role required: discovery_admin

## Procedure

1. Navigate to WorkspacesDiscovery Admin WorkspaceSchedules.
2. Select New Discovery from the header of any tab on the Schedules page.
3. Select Cloud-based discovery and select Continue.
4. Enter a unique and descriptive name for the Discovery schedule.
5. Select OCI as the cloud provider.
6. Choose a MID Server.

   | Option | Description |
   | Use a cluster of MID servers | Select an existing MID Server. Clusters provide failover protection and load balancing between MID Servers. See [Configure a MID Server cluster](https://www.servicenow.com/docs/access?context=t_ConfigureAMIDServerCluster&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US) for more information. |
   | Automatically select a MID server | An available MID Server is automatically selected when the Discovery schedule runs. See [Automatic MID Server selection](https://servicenow-prod.fluidtopics.net/cq2QqTE0RIUEE_i4lIQ2Mg "Automatic selection of MID Servers ensures that each agent uses the most efficient available MID Server.") for more information. |
   | Search for a MID server | Choose a MID Server to run the Discovery schedule. Only MID Servers that are validated, up, and have the Cloud Management capability are displayed. |
   |-|-|

   {#create-oci-schedule-DAW__choicetable_bcg_4pg_z2c}
7. Select Next.
8. Select a cloud account.

   | Option | Description |
   | Existing cloud account | Select an existing cloud account on your instance. Once an account is selected, the Account name and Account ID fields auto-populate. |
   | New cloud account | Add a new cloud account to your instance by entering an account name, compartment ID, and Datacenter URL. Note: * You can access the compartment ID, also referred to as the Oracle Cloud Identifier (OCID) of the compartment, in the Oracle Cloud console via Identity \& SecurityCompartments. * Example URLs: * For commercial cloud: `https://{service}.ap-mumbai-1.oraclecloud.com` * For GovCloud: `https://{service}.us-gov-ashburn-1.oraclegovcloud.com` {#create-oci-schedule-DAW__ul_fbd_511_b3c} {#create-oci-schedule-DAW__ul_pwv_s11_b3c} |
   |-|-|

   {#create-oci-schedule-DAW__choicetable_bbl_3zw_zgc}  
   Even if the cloud account was previously verified, you can reverify if policies or permissions may have changed by selecting Verify information.
9. Select Discover all Projects or Discover specific Projects.  
   Note:  
   This option displays only when the target cloud account is an Oracle compartment account.
   1. If discovering specific projects, select Add projects.  
      The Discoverable Projects dialog displays.
   2. Select the check box next to one or more corresponding names and then select Add.
   {#create-oci-schedule-DAW__substeps_a5n_qkl_jhc}
10. Select Next.
11. Select cloud regions for the discovery schedule.  
    You can choose to include all regions linked to the cloud account or select specific regions. There's no restriction on the number of cloud regions that you can add.
    1. **Optional:** To discover specific cloud regions, select the check box for the cloud region you want to scan from the Available cloud regions list.
    2. **Optional:** If the cloud regions don't appear, select Refresh cloud regions.
    {#create-oci-schedule-DAW__substeps_pzz_fjl_jhc}
12. Select Next.
13. **Optional:** To complement your cloud schedule with an IP-based Discovery schedule, enable the Create a server discovery schedule toggle.
    1. **Optional:** Select a MID Server or cluster that can discover the Virtual Machines (VM) and their attributes.
    {#create-oci-schedule-DAW__substeps_egp_vjl_jhc}
14. Select Next.
15. Configure the Discovery schedule.

    | Option | Description |
    | Run at a scheduled time | The schedule runs at a scheduled date and time. Use the fields to define when the schedule runs. |
    | Run on demand | The schedule only runs when triggered manually. The schedule can be triggered by selecting Finish and run at the end of this setup, or by navigating to the schedule in the Discovery Schedules \[discovery_schedule\] table and selecting Discover Now. |
    | Run after series | The schedule runs after another existing Discovery schedule completes, staggering or chaining them together. Selecting an existing schedule displays a relationship map of all the other associated schedules. |
    | Set discovery time out | If the schedule exceeds the maximum runtime, it's canceled. After toggling, configure the runtime threshold. |
    | Finish and run | After being selected, all the information provided is validated. Then, a Discovery schedule is created in the background, a Discovery status is created, and the schedule is run. You're redirected to the Status Details page for the schedule. |
    | Finish | After being selected, all the information provided is validated. A Discovery schedule is created, and you're redirected to its entry in the Discovery Schedules \[discovery_schedule\] table. You can edit the schedule information or run it by selecting Discover Now. |
    |-|-|

    {#create-oci-schedule-DAW__choicetable_hcg_ypg_z2c}

*[\>]: and then