AI Service Graph Connector for Microsoft

  • Release version: Australia
  • Updated March 12, 2026
  • 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 AI Service Graph Connector for Microsoft

    The AI Service Graph Connector for Microsoft enables ServiceNow customers to discover and import AI assets from Microsoft Azure AI Foundry and Copilot Studio environments into the ServiceNow AI Control Tower. This integration helps catalog AI agents, models, and prompts from multiple Microsoft platforms while providing detailed usage metrics and governance capabilities through the AI Control Tower value dashboard.

    Show full answer Show less

    Key Features

    • Discovery of Azure AI Foundry agents, including ML Services, AI Services, and new Foundry variants.
    • Discovery of Microsoft Copilot agents across single or multiple Power Platform environments.
    • AI asset lineage and dependency tracking via sub-component relationships.
    • Aggregation of usage and execution metrics by agent, date, and session.
    • Support for tenant-wide or filtered discovery by resource and region for Azure Foundry.
    • Multi-environment discovery using a single Copilot connection, enabling efficient management of multiple environments.

    Supported Versions and Roles

    The connector is supported on ServiceNow releases Australia, Zurich, and Yokohama Patch 11.

    To configure the connector, users must have either the snaidisc.discoveryadmin or sncmdbintutil.sgcadmin role assigned.

    Prerequisites and Setup

    Before initial configuration, the following setup steps must be completed:

    • Update Data Source Access: Grant write permissions (create, update, delete) on the Data Source table in the Global application scope to enable the connector to create data sources.
    • Clear Cache: Run a background script to clear cached data for the Data Source and Tables to ensure proper synchronization. This process may take several minutes.

    After setup, enter multiple environment IDs as comma-separated values to enable discovery across several environments using the same OAuth credentials (Client ID and Client Secret). Ensure the application user is configured with required security roles in each environment, as each environment is discovered and validated separately during import.

    Practical Benefits for ServiceNow Customers

    This connector empowers ServiceNow customers to achieve comprehensive visibility and governance over their Microsoft AI assets and operations. By integrating AI asset discovery and usage metrics into the AI Control Tower, customers can effectively monitor, manage, and optimize AI deployments across multiple Microsoft environments, improving operational control and compliance.

    The AI Service Graph Connector for Microsoft enables you to discover and import AI assets from Azure AI Foundry and Copilot Studio environments into ServiceNow AI Control Tower.

    The connector creates separate AI connections for each Microsoft platform, cataloging AI agents, models, and prompts. The usage information is consumed by the AI Control Tower value dashboard, providing comprehensive visibility and governance of your AI operations.

    Key capabilities:

    • Discovery of Azure AI Foundry agents across ML Services, AI Services, and New Foundry variants.
    • Discovery of Microsoft Copilot agents across single or multiple Power Platform environments.
    • AI asset lineage and dependency tracking through sub-component relationships.
    • Usage and execution of metrics aggregated by agent, date, and session.
    • Support for tenant-wide discovery or filtered discovery by resource and region (Azure Foundry).
    • Multi-environment discovery using a single Copilot connection.

    Download apps from the store

    Visit the  ServiceNow store website to download the AI Service Graph Connector for Microsoft  application.

    Supported ServiceNow versions

    Release Status
    Australia Supported
    Zurich Supported
    Yokohama Patch 11 Supported

    User Roles

    You must have one of the following roles assigned to complete the configuration task.

    Required Role
    sn_ai_disc.discovery_admin
    sn_cmdb_int_util.sgc_admin

    ServiceNow Prerequisites

    Complete the following setup steps once when configuring the connector for the first time.

    Note:
    Updating data source access and clear cache is a prerequisite that needs to be completed only once, when setting up a new instance for the first time.
    Update Data Source Access

    The connector requires write permissions to the Data Source table to create data sources.

    To enable data source creation:
    1. Select Global from the application picker.
    2. Navigate to Application Access.
    3. Select the Can create, Can update, and Can delete check boxes.
    4. Select Update.
    5. Switch to the connector application scope.
    Clear cache

    Clear the cached data for the Data Source and Tables.

    To clear the cache:
    1. Navigate to System Definition > Background Scripts.
    2. Enter the following script in the Run Script text box:
      GlideTableManager.invalidateTable('sys_data_source');
      GlideCacheManager.flushTable('sys_data_source');
      GlideTableManager.invalidateTable('sys_db_object');
      GlideCacheManager.flushTable('sys_db_object');
      
    3. Select Run Script.
      Note:
      The script might take several minutes to complete. After completion, switch to the connector application scope.
    4. After completion, switch to the connector application scope.
    • Enter multiple environment IDs as comma-separated values in the Environment ID field (eg: env-id-1, env-id-2, env-id-3).
    • The same OAuth credentials (Client ID and Client Secret) are used for all environments.
    • Verify the application user is configured in each environment with the required security roles.
    • Each environment will be tested and discovered separately during the import process.