API Service Graph Connector for Azure API Management

  • Release version: Washingtondc
  • Updated July 31, 2025
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of API Service Graph Connector for Azure API Management

    The ServiceNow® API Service Graph Connector for Azure API Management allows you to import API details from Azure API Management applications into the Configuration Management Database (CMDB). This integration ensures a consistent and normalized data model across different technologies, enhancing your API management capabilities.

    Show full answer Show less

    Key Features

    • Integration of API data into CMDB for a comprehensive view of API inventory.
    • Support for multiple ServiceNow versions: Washington DC, Xanadu, and Yokohama.
    • Utilizes the Robust Transform Engine (RTE) for data mapping and the Identification and Reconciliation Engine (IRE) for data insertion.
    • Configuration through the SGC Central view in the CMDB Workspace, enabling effective management of connections.

    Use Cases

    • Maintain a detailed inventory of both exposed and backend APIs, enabling tracking of usage and ownership.
    • Identify impacted endpoints when services change or fail, facilitating incident management.
    • Address security vulnerabilities and compliance requirements related to API endpoints.

    Key Outcomes

    By utilizing the API Service Graph Connector, customers can expect improved oversight of API assets, streamlined incident management, and enhanced compliance tracking. Configuring the connector through SGC Central simplifies the process, providing a guided setup to ensure efficient data integration.

    Use the ServiceNow® API Service Graph Connector for Azure API Management to import API details from an Azure API Management application into the Configuration Management Database (CMDB).

    Request apps on the Store

    Visit the ServiceNow Store website to view all the available apps and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the ServiceNow Store version history release notes.

    Key features

    Import data into a normalized data model for consistency across other technologies.

    Supported ServiceNow versions

    • Washington DC
    • Xanadu
    • Yokohama

    Use cases

    You can use the API Service Graph Connector for Azure API Management to:
    • Maintain an end-to-end inventory of exposed and backend APIs, identifying what APIs are published, used, and by whom.
    • Track APIs from customer-facing endpoints to the underlying services, identifying impacted endpoints when services change or fail and creating incidents for reported issues.
    • Address vulnerabilities and security incidents related to API endpoints, and create compliance requirements to measure against.

    Configuring a connection for the connector

    You can configure a connection for the connector by using the SGC Central view in the CMDB Workspace. The view enables you to discover and install connectors, and then effectively manage the full life cycle of creating, editing, monitoring, and debugging connections. To configure the connector using SGC Central, see Configure API Service Graph Connector for Azure API Management using SGC Central.

    Important:
    Unless there are configuration issues, use the SGC Central view in the CMDB Workspace to configure the connection for the connector, as the guided setup method is being deprecated.

    Data mapping

    Data from the Azure API Management data sources is mapped and transformed into the CMDB Configuration Item (CI) class definitions using the Robust Transform Engine (RTE). Data is inserted into the CMDB using the Identification and Reconciliation Engine (IRE).

    When you complete setting up the connection, you can configure the integration to periodically pull data from an Azure API Management application.

    The following table lists the data sources in the order they run, the staging tables, and the target tables as CMDB CI and non-CMDB classes for an Azure API Management application.
    Table 1. Data mapping for Azure API Management
    Data source Staging table Target tables
    API Management Services SGA Azure API Management [sn_azure_api_gw_sga_azure_api_management] Azure API Management

    Azure Subscription

    Cloud Service Account

    Resource Group

    DNS Alias
    Managed API SGA Azure Managed API [sn_azure_api_gw_sga_azure_managed_api] Managed API
    API Frontend Backend SGA Azure API Frontend Backend [sn_azure_api_gw_sga_azure_api_frontend_backend_import] API Frontend

    API Backend
    API GraphQL Frontend Backend SGA Azure API GraphQL Frontend Backend [sn_azure_api_gw_sga_azure_api_graphql_frontend_backend] API Frontend

    API Backend
    API Consumer SGA Azure API Consumer [sn_azure_api_gw_sga_azure_api_consumer] API Consumer
    API Product SGA Azure API Product [sn_azure_api_gw_sga_azure_api_product] API Product Bundle
    API Consumer Subscription SGA Azure API Consumer Subscription [sn_azure_api_gw_sga_azure_api_subscription] API Consumer Subscription
    API Tag API Tag [sn_azure_api_gw_api_tag] Key Value
    API Consumer Access SGA Azure API Consumer Access [sn_azure_api_gw_sga_azure_managed_api] API Consumer Access

    For more information on where data is saved when pulling data from an Azure API Management application, see Target tables for storing API Service Graph Connector for Azure API Management data.

    You can use the IntegrationHub ETL app to view the data maps. See IntegrationHub ETL for more information.

    Record removal process

    The connector supports soft deletion for CMDB CI classes only, meaning records are not permanently removed from the system. Instead, any CMDB CI records not discovered during the last scheduled job run are marked as Non-Operational.