Scheduling Full Loads for hardware data import in Service Graph Connector for Azure

.kb-content { background-color: white; padding: 30px; border-radius: 5px; box-shadow: 0 2px 4px rgba(0, 0, 0, 0.1); } h1 { color: #032D42; font-size: 28px; margin-bottom: 10px; border-bottom: 3px solid #63DF4E; padding-bottom: 10px; } .subtitle { color: #666; font-style: italic; margin-bottom: 30px; font-size: 14px; } h2 { color: #044355; font-size: 20px; margin-top: 25px; margin-bottom: 15px; } h3 { color: #044355; font-size: 16px; margin-top: 15px; margin-bottom: 10px; } .code-block { background-color: #f5f5f5; border-left: 3px solid #032D42; padding: 12px; margin: 15px 0; font-family: 'Courier New', monospace; color: #555; } .critical-note { background-color: #ffebee; border-left: 4px solid #d32f2f; padding: 15px; margin: 20px 0; border-radius: 3px; } .critical-note strong { color: #d32f2f; } .important-note { background-color: #fff3cd; border-left: 4px solid #ff9800; padding: 15px; margin: 20px 0; border-radius: 3px; } .step-header { font-weight: bold; color: #032D42; margin-bottom: 10px; } Scheduling Full Loads for Hardware data import in Service Graph Connector for Azure SGC Azure 1.17 Release

Overview Starting with the 1.17 release of Service Graph Connector (SGC) for Azure, administrators can now schedule full load operations for Azure resources. This knowledge base article provides step-by-step instructions for configuring and scheduling full loads to ensure optimal synchronization with your ServiceNow CMDB.

Prerequisites ServiceNow instance with SGC Azure 1.17 or later Required Role: cmdb_inst_admin Important Timing Consideration CRITICAL: Schedule this script execution at least 30 minutes BEFORE the subscriptions import schedule time. If scheduled after this window, the full load will execute during the subsequent scheduled run.

Example: If your subscriptions import runs at 2:00 PM, schedule the full load by 1:30 PM or earlier.

Scheduling Full Loads for Default Connection Log in to ServiceNow Log in to your ServiceNow instance with an account that has the cmdb_inst_admin role.

Navigate to Scheduled Script Execution Navigate to the Scheduled Script Execution form using the following URL:

/sn_cmdb_int_util_scheduled_script_execution.do?sys_id=0123f607ff600310e562ffffffffff49 Activate the Script Check the Active checkbox to enable the scheduled script.

Configure Schedule Time Configure the schedule to run at your desired time (minimum 30 minutes before subscriptions import) and save.

Scheduling Full Loads for Multiple Connections If you have multiple Azure connections and need to schedule full loads for each one, follow these steps:

Locate Your Connection's sys_id Navigate to Service Graph Connectors > Azure > Connections

Find the Azure connection you want to schedule full loads for and note/copy its sys_id (visible in the URL on form or right click on the connection).

Get the Scheduled Job Script The scheduled job executes the following script:

new SGAzureDSHelperBase().clearLastSuccessTime('d10cf37643716110f3063fea8eb8f224'); This script contains a placeholder sys_id that you will replace with your connection's sys_id.

Replace the Connection sys_id Replace the sys_id d10cf37643716110f3063fea8eb8f224 in the script with the connection sys_id you copied in Step 1.

Example: If your connection sys_id is a5e1f8c9b2d4e6f7g8h9i0j1k2l3m4n5 , the script becomes:

new SGAzureDSHelperBase().clearLastSuccessTime('a5e1f8c9b2d4e6f7g8h9i0j1k2l3m4n5'); Create a New Scheduled Execution Entry Navigate to /sn_cmdb_int_util_scheduled_script_execution.do and create a new record (or duplicate an existing one).

Paste your modified script (from Step 3) into the script field.

Activate and Schedule Click the Activate button to enable the scheduled script.

Click the Schedule button and set the execution schedule (minimum 30 minutes before subscriptions import).

Repeat for Each Additional Connection Repeat Steps 1-4 for each additional Azure connection, ensuring:

You use the correct connection sys_id for each connection Each scheduled entry has a unique script with the correct sys_id Each script execution schedule is scheduled at least 30 minutes before the corresponding Subscriptions import schedule time Note: Do not modify the default scheduled script execution record. Always create new records for additional connections to maintain flexibility and prevent conflicts. Validation After scheduling, verify the configuration by:

Confirming the scheduled script is Active (status should show as enabled) Verifying the schedule time is at least 30 minutes before subscriptions import Checking execution logs in SGC Azure monitoring to confirm successful runs