Configure and run Discovery for your Azure subscription

Specify the subscriptions to manage and configure the Discovery schedule for discovering resources in the subscriptions.

Before you begin

Role required: cloud_admin or sn_azure.admin

About this task

You use the Subscriptions form to:
  • View the list of subscriptions that the service principal can access.
  • From the list, specify which subscriptions that you, the cloud_admin, want to administer.
Note: Running multiple scheduled jobs at one time can cause significant performance degradation. When possible, schedule cloud discovery, billing data download, and resource optimization jobs to run a few hours apart instead of overlapping.


  1. Open the Azure Subscriptions form. Either:
    • From the related list on the Service Principal form
    • Navigate to Microsoft Azure Cloud > Configuration > Accounts (Subscriptions).
  2. On the Azure Subscriptions form, click the subscription to configure.
  3. Click the Create Discovery Schedule related link.
  4. On the Discovery Schedule form, specify the schedule for Discovery. For example, you can schedule Discovery to run every day at 3:00 AM for a total of 365 days.
    Note: Do not modify the values in the remainder of the fields. These values are populated automatically during discovery.
    Field Value
    Name Name of the Azure subscription that uses the Discovery schedule that is defined on this page.
    Discover Type of resources to discover.
    MID server MID server that will manage the Discovery process.
    Active Check box to activate this schedule.
    Max run time Overall time period over which the schedule applies. For example, enter 365 days if you want this schedule to be used for one year. Specify a period less than a day using hh:mm:ss format.
    Run The options are described in the following step.
  5. Specify the Run option.
    Table 1. Options for a Discovery Run Schedule
    Run option Description
    Daily Runs every day. Use the Time field to select the time of day this discovery runs.
    Weekly Runs on one designated day of each week. Use the Time field to select the time of day this discovery runs.
    Monthly Runs on one designated day of each month. Use the Day field to select the day of the month. Use the Time field to select the time of day this discovery runs. If the designated day does not occur in the month, the schedule does not run that month. For example, if you designate day 30, the schedule does not run in February.
    Periodically Runs every designated period of time. Use the Repeat Interval field to define the period of time in a days, hours, minutes and seconds. The first discovery runs at the point in time defined in the Starting field. The subsequent discoveries run after each Repeat Interval period passes.
    Once Run one time as designated by the date and time defined in the Starting field.
    On Demand Does not run on a schedule. Click the Discover now link to run this discovery.
    Weekdays Runs every Monday, Tuesday, Wednesday, Thursday, and Friday. Use the Time field to select the time of day.
    Weekends Runs every Saturday and Sunday. Use the Time field to select the time of day.
    Month Last Day Run the last day of every month. Use the Time field to select the time of day.
    Calendar Quarter End Runs on March 31, June 30, September 30, and December 31. Use the Time field to select the time of day. To change these dates, modify the script include DiscoveryScheduleRunType.
    After Discovery Allows you to sequentially stagger the schedule. Use this option to run this schedule after the Discovery designated in the Run after field finishes. Check the Even if canceled check box to designate that this discovery should run even if the Run after Discovery is canceled before it finishes.
    • This option is not valid when the Discovery is started via DiscoverNow, or when using the Discover CI feature.
    • You cannot designate an inactive Discovery schedule.
    • You cannot create a loop by designating the run after Discovery to be the same Discovery.
    • This Discovery does not run if the Run after discovery does not finish, with the exception that the Even if canceled box is checked and the Discovery is canceled.
  6. Click Submit.


Discovery runs and populates your CMDB (configuration management database) and images that you can later approve to offer to cloud users in the catalog. The current state of the resource, if applicable, is updated accordingly (for example, Azure virtual machine instances, Azure virtual networks, Azure subnets, etc.). Cloud admins use the Accounts (Subscriptions) module to specify which subscriptions to manage, and to configure the Discovery schedule for subscriptions.