---
sourceDocument: Australia ServiceNow AI Platform Capabilities
sourceDocumentLink: https://www.servicenow.com/docs/r/servicenow-platform

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# Configure using SGC Central

# Configure Service Graph Connector for Microsoft Azure using SGC Central {#ariaid-title1}

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

Use the playbook available with the SGC Central application to set up the Service Graph Connector for Microsoft Azure for pulling in Microsoft Azure data into the CMDB.

## Before you begin

Install Service Graph Connector for Microsoft Azure version 1.9.0 or later from the ServiceNow Store. For ServiceNow Store installation steps, see [Install a ServiceNow Store application](https://www.servicenow.com/docs/access?context=installing-applications-in-application-manager&version=australia&pubname=australia-platform-administration&ft:locale=en-US).  
Important:  
After the initial import of Azure data, the application performs a delta import of data. However, you can perform a full pull of data anytime later by disabling the delta synchronization and setting the sn_sg_azure_integ.is_delta_sync_enabled property to `false`. For more information, see [Configuring data synchronization in Service Graph Connector for Microsoft Azure](https://www.servicenow.com/docs/D3AYLr_tQtSUgFKiNa~OYw#sgc-cmdb-azure-data-sync "You can configure the system property for synchronizing only delta data from an Azure instance.").  
Role required: The following table shows the roles required for each stage of the playbook.{#sgcc-configure-azure-integ__table_u12_qcp_l3c__entry__2}

| Stage | Role |
|-|-|
| Prerequisites | admin |
| Setup | SGC-Admin (sn_cmdb_int_util.sgc_admin) or admin |
[Table 1. Role required for each playbook stage]

{#sgcc-configure-azure-integ__table_u12_qcp_l3c}  
Note:  
The admin user role is required to run background scripts and to provide access to global tables to the SGC-Admin user. For information about the user roles for Service Graph Connectors, see [Service Graph Connector user roles](https://www.servicenow.com/docs/llR5whccV6~8Oi~Q_e8~xQ#cmdb-sgc-intro__section_ett_spp_4hc).

## About this task

The playbook experience for onboarding connectors is activated with SGC Central in the Service Graph Workspace or CMDB Workspace. To configure the SGC Central application, see [Configuring SGC Central](https://www.servicenow.com/docs/7dDf5rxNMnkcccCA02GxmQ "Set up the SGC Central application for onboarding and maintaining Service Graph Connectors and monitoring the errors related to connections added using Service Graph Connectors.") and for more information on how to interact with a playbook, see [Interact with Playbook](https://www.servicenow.com/docs/access?context=playbook-ui&version=australia&pubname=australia-build-workflows&ft:locale=en-US).

The connector uses the Azure Management APIs for the complete pull of data from Azure. However, to pull delta changes from Azure, the Azure Resource Graph APIs are used. The domain name system (DNS) is Microsoft Azure Management, but the path is a resource graph.

## Procedure

1. Use one of the following methods to open SGC Central:
   * Navigate to WorkspacesService Graph Workspace, and from the left navigation panel, select the Ingestion icon ![]() to open the SGC Central view.
   * Navigate to WorkspacesCMDB WorkspaceSGC Central.
   {#sgcc-configure-azure-integ__choices_bd1_nrz_k3c}
2. On the Overview page, select Create connection.  
   Tip:  
   Alternatively, you can select Create connection on the All connections page.
3. On the Create connection window, select the Microsoft Azure connector type and then select Create connection.
4. Complete the initial prerequisites when setting up a connection for the first time using a connector.  
   Note:  
   This step is required only during the first-time setup. See [Perform initial setup tasks when creating a connection in SGC Central](https://www.servicenow.com/docs/0vWb7VG8kY9kzX25jOf72Q "Complete the prerequisites for setting up a connection for the first time using a Service Graph Connector within the SGC Central view of the Service Graph Workspace or CMDB Workspace.").
5. Complete the prerequisites for setting up the Azure environment.
   1. Complete the instructions required for setting up the Azure environment.  
      1. In the Prerequisites stage of the playbook, select the Review setup instructions activity.
      2. Obtain the OAuth credentials including client ID, client secret, and token URL from your Microsoft Azure administrator.
      3. For importing hardware data, grant the `User.Read` permission on the Microsoft Graph API in the Azure environment. Also, ensure that the IAM policy for the Azure subscription has the Reader role. See [Assign a user as an administrator of an Azure subscription with conditions](https://learn.microsoft.com/en-us/azure/role-based-access-control/role-assignments-portal-subscription-admin) on the Microsoft Azure documentation site.
      4. For importing software data, grant the `Data.Read` permission on the Log Analytics API in the Azure environment. In addition, set up a Log Analytics workspace in the Azure environment.
      5. After completing the Review setup instructions activity, select Continue.
      {#sgcc-configure-azure-integ__ol_l2w_kkr_pcc} {#sgcc-configure-azure-integ__prereq-azure}
   {#sgcc-configure-azure-integ__prereq-azure} {#sgcc-configure-azure-integ__substeps_tsw_kvq_fcc}
6. Determine whether to import only hardware data or both hardware and software data.
   1. In the Setup stage of the playbook, select the Select services activity.  
      If needed, expand the Setup stage to select an activity.
   2. **Optional:** To import both hardware and software data, select the Hardware and software check box.  
      Note:  
      Importing software data requires a hardware connection.

      If you need to import only hardware data, the Hardware only check box is already selected by default.
      {#sgcc-configure-azure-integ__prereq-sw}
   {#sgcc-configure-azure-integ__prereq-sw}
   3. Select Continue.
   {#sgcc-configure-azure-integ__substeps_phc_gkw_fcc}
7. Enter the connection details and test the API connection for importing hardware data.
   1. In the Setup stage of the playbook, select the Create and test hardware connection activity.
   2. On the form, fill in the fields.  
      {#sgcc-configure-azure-integ__table_npd_v2z_swb__entry__2}

      | Field | Description |
      |-|-|
      | Connection name | Name to identify the hardware connection record. For example, <kbd class="ph userinput">SG-Azure hardware connection</kbd>. |
      | Connection URL | Base URL to connect to your Azure client application. Note: This field is automatically set to the URL to connect to the application. Leave the field value as is. |
      | OAuth client ID | Application (client) ID of your Azure client application as noted in step [5.a](https://www.servicenow.com/docs/z1VwhjSE00IMW61Le79~9w#sgcc-configure-azure-integ__prereq-azure). |
      | OAuth client secret | Client secret of your Azure client application as noted in step [5.a](https://www.servicenow.com/docs/z1VwhjSE00IMW61Le79~9w#sgcc-configure-azure-integ__prereq-azure). |
      | OAuth token URL | Callback URL for the Azure client application. Based on the region of your Azure client application, enter the token URL in one of the following formats: * Global https://login.microsoftonline.com/<var class="keyword varname">&lt;tenantid&gt;</var>/oauth2/v2.0/token * US Government https://login.microsoftonline.us/<var class="keyword varname">&lt;tenantid&gt;</var>/oauth2/v2.0/token * China https://login.partner.microsoftonline.cn/<var class="keyword varname">&lt;tenantid&gt;</var>/oauth2/v2.0/token * Germany https://login.microsoftonline.de/<var class="keyword varname">&lt;tenantid&gt;</var>/oauth2/v2.0/token {#sgcc-configure-azure-integ__ul_nwf_hg3_yxb} Where <var class="keyword varname">&lt;tenantid&gt;</var> is the tenant ID of your Azure client application as noted in step [5.a](https://www.servicenow.com/docs/z1VwhjSE00IMW61Le79~9w#sgcc-configure-azure-integ__prereq-azure). |
      [Table 2. Create and test hardware connection form]

      {#sgcc-configure-azure-integ__table_npd_v2z_swb} {#sgcc-configure-azure-integ__hw-id}
   {#sgcc-configure-azure-integ__hw-id}
   3. Select Create and test connection.
   4. Once the connection test is complete, select Continue.
   {#sgcc-configure-azure-integ__substeps_vrw_2tk_wbc}
8. Configure the import schedule to import hardware data at regular intervals.
   1. In the Setup stage of the playbook, select the Configure hardware import schedule activity.
   2. Select Configure import schedule.
   3. Expand the Parent scheduled data import within the Import schedules list to select the <var class="keyword varname">Connection name</var>-SG-Azure Subscriptions import schedule.
   4. In the Configure import schedule dialog box, select the Active check box, and then fill in the run schedule and time details.  
      For more information, see [Schedule a data import](https://www.servicenow.com/docs/access?context=t_ScheduleADataImport&version=australia&pubname=australia-integrate-applications&ft:locale=en-US#table_r53_5hm_xp).
   5. Select Save.  
      Alternatively, select Execute Now to execute the import schedule immediately.
   6. Select Continue.
   {#sgcc-configure-azure-integ__substeps_lf4_yvw_fcc}
9. Enter the connection details and test the API connection for importing software data.  
   The Create and test software connection activity for importing software data appears only when the Hardware and software check box is selected in step [6.b](https://www.servicenow.com/docs/z1VwhjSE00IMW61Le79~9w#sgcc-configure-azure-integ__prereq-sw).
   1. In the Setup stage of the playbook, select the Create and test software connection activity.
   2. On the form, fill in the fields.  
      {#sgcc-configure-azure-integ__table_vw2_jzw_fcc__entry__2}

      | Field | Description |
      |-|-|
      | Software connection name | Name to identify the software connection record. For example, <kbd class="ph userinput">SG-Azure software connection</kbd>. |
      | Hardware connection name | Name of the hardware connection record. Note: This field is automatically set to the hardware connection name specified in step [7.b](https://www.servicenow.com/docs/z1VwhjSE00IMW61Le79~9w#sgcc-configure-azure-integ__hw-id). |
      | Connection URL | Base URL to connect to the Log Analytics workspace in the following format: https://api.loganalytics.io/v1/workspaces/<workspace_id> Where `<workspace_id>` is the ID of the Log Analytics workspace as noted in step [5.a](https://www.servicenow.com/docs/z1VwhjSE00IMW61Le79~9w#sgcc-configure-azure-integ__prereq-azure). Note: This field is automatically set to the URL to connect to the Log Analytics workspace. Replace the `<workspace_id>` variable in the auto-generated URL with the workspace ID of your Log Analytics workspace. |
      | OAuth client ID | Application (client) ID of your Azure client application as noted in step [5.a](https://www.servicenow.com/docs/z1VwhjSE00IMW61Le79~9w#sgcc-configure-azure-integ__prereq-azure). |
      | OAuth client secret | Client secret of your Azure client application as noted in step [5.a](https://www.servicenow.com/docs/z1VwhjSE00IMW61Le79~9w#sgcc-configure-azure-integ__prereq-azure). |
      | OAuth token URL | Token URL of your Azure client application. Based on the region of your Azure client application, enter the token URL in one of the following formats: * Global https://login.microsoftonline.com/<var class="keyword varname">&lt;tenantid&gt;</var>/oauth2/v2.0/token * US Government https://login.microsoftonline.us/<var class="keyword varname">&lt;tenantid&gt;</var>/oauth2/v2.0/token * China https://login.partner.microsoftonline.cn/<var class="keyword varname">&lt;tenantid&gt;</var>/oauth2/v2.0/token * Germany https://login.microsoftonline.de/<var class="keyword varname">&lt;tenantid&gt;</var>/oauth2/v2.0/token {#sgcc-configure-azure-integ__ul_ww2_jzw_fcc} Where <var class="keyword varname">&lt;tenantid&gt;</var> is the tenant ID of your Azure client application as noted in step [5.a](https://www.servicenow.com/docs/z1VwhjSE00IMW61Le79~9w#sgcc-configure-azure-integ__prereq-azure). |
      [Table 3. Create and test software connection form]

      {#sgcc-configure-azure-integ__table_vw2_jzw_fcc}
   3. Select Create and test connection.
   4. Once the connection test is complete, select Continue.
   {#sgcc-configure-azure-integ__substeps_uw2_jzw_fcc}
10. Configure the import schedule to import software data at regular intervals.  
    The Configure software import schedule activity for importing software data appears only when the Hardware and software check box is selected in step [6.b](https://www.servicenow.com/docs/z1VwhjSE00IMW61Le79~9w#sgcc-configure-azure-integ__prereq-sw).
    1. In the Setup stage of the playbook, select the Configure software import schedule activity.
    2. Expand the Parent scheduled data import within the Import schedules list to select the <var class="keyword varname">Connection name</var>-SG-Azure TCP import schedule. {#sgcc-configure-azure-integ__parent}
    {#sgcc-configure-azure-integ__parent}
    3. In the Configure import schedule dialog box, select the Active check box, and then fill in the run schedule and time details.  
       For more information, see [Schedule a data import](https://www.servicenow.com/docs/access?context=t_ScheduleADataImport&version=australia&pubname=australia-integrate-applications&ft:locale=en-US#table_r53_5hm_xp).
    4. Select Save.  
       Alternatively, select Execute Now to execute the import schedule immediately. {#sgcc-configure-azure-integ__save}
    {#sgcc-configure-azure-integ__save}
    5. Repeat steps [10.b](https://www.servicenow.com/docs/z1VwhjSE00IMW61Le79~9w#sgcc-configure-azure-integ__parent) to [10.d](https://www.servicenow.com/docs/z1VwhjSE00IMW61Le79~9w#sgcc-configure-azure-integ__save) for any other parent import schedule if not already set to active.
    6. Select Continue.
    {#sgcc-configure-azure-integ__substeps_mbb_qcx_fcc}
11. In the Setup stage of the playbook, select the Connection setup complete activity to verify whether the connection was created.

## What to do next

Select View all connections to review the connection details. The created connection appears in the Installed connections list.
**Related concepts**   

* [Service Graph Connector for Microsoft Azure](https://www.servicenow.com/docs/801RZ5n3RQtBXent91TMCQ "Use the Service Graph Connector for Microsoft Azure to pull data from Microsoft Azure into your CMDB.")
* [Accessing the connection details of Service Graph Connector for Microsoft Azure](https://www.servicenow.com/docs/iVgW3jFOuW8YW5ZMeJHLUg#sgc-cmdb-azure-conn "You can access the connection details of the Service Graph Connector for Microsoft Azure in a single view using the common connection framework (CCF) included within the Integration Commons for CMDB (sn_cmdb_int_util) store app.")
* [Additional features within the Service Graph Connector for Microsoft Azure](https://www.servicenow.com/docs/ZKg8oYs09YMDJR71XTQq0g "Use the additional features available within the Service Graph Connector for Microsoft Azure to maximize its use for importing data.")  
**Related reference**   

* [CMDB classes targeted in Service Graph Connector for Microsoft Azure](https://www.servicenow.com/docs/nEnkCPuhX06ZCQ5l2yUg2Q "When you complete setting up the connection, you can configure the integration to periodically pull data from Microsoft Azure. The data is saved in tables that extend from the Configuration item [cmdb_ci] table.")
* [Data mapping for Service Graph Connector for Microsoft Azure](https://www.servicenow.com/docs/hDwKlizI0yp3_L7MQKU0Og "Data from the Azure data sources is mapped and transformed into the ServiceNow CMDB Configuration Item (CI) class definitions using the Robust Transform Engine (RTE). Data is inserted into the ServiceNow CMDB using the Identification and Reconciliation Engine (IRE).")
* [Supported Microsoft Azure resource types](https://www.servicenow.com/docs/QBS_kAiAdw_QOrNAnCcRBQ "Several Microsoft Azure resource types are imported as CMDB data.")
* [Service Graph Connector for Microsoft Azure properties](https://www.servicenow.com/docs/DgMopeFsCD5GwkeXAhXnJA "Service Graph Connector for Microsoft Azure properties control the behavior of the connector.")

*[\>]: and then


