Azure Service Endpoint Policy pattern-based discovery

  • Release version: Yokohama
  • Updated August 11, 2026
  • 3 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 Azure Service Endpoint Policy pattern-based discovery

    The Azure Service Endpoint Policy pattern-based discovery in ServiceNow enables automated detection and mapping of Azure service endpoint policies within your cloud environment. This functionality is part of the Discovery and Service Mapping Patterns application, helping you populate both CMDB and non-CMDB tables with detailed Azure resource information. The discovery process supports comprehensive tracking of Azure resources, relationships, and tags, ensuring your CMDB accurately reflects your Azure infrastructure.

    Show full answer Show less

    Key Features

    • Pattern Activation: The Azure Service Endpoint Policy discovery pattern is disabled by default and requires manual activation. From Visibility Content version 6.28.0 onward, pattern activations are preserved through updates without being treated as customizations.
    • Discovery Prerequisites: Ensure Microsoft Azure discovery prerequisites are met, including setting up Azure service accounts correctly, especially for Azure GovCloud (US) environments which require a datacenter URL configuration.
    • Data Storage: The discovery populates data into both CMDB tables (e.g., Cloud Resource [cmdbcicmpresource]) and non-CMDB tables (e.g., Azure-specific tables reachable via navigation under Configuration > Azure).
    • Resource and Relationship Mapping: Key Azure resource details such as Object ID, Kind, Location, Resource Group, Subscription ID, and Tenant ID are captured. The discovery also establishes relationships between resources, resource groups, subnets, and datacenters to provide a comprehensive view of your Azure service endpoint policies.
    • Tag Collection: Azure tags are collected and stored in the Key Value [cmdbkeyvalue] table, enabling enhanced resource categorization and filtering within the CMDB.

    Key Outcomes

    • Enhanced Visibility: Gain detailed insights into your Azure service endpoint policies, including provisioning and operational states, through automated discovery and inventory.
    • Accurate CMDB Population: Keep your CMDB up-to-date with authoritative Azure resource data and their relationships, supporting better cloud management and operations.
    • Governance and Compliance: Leverage tag discovery and resource state tracking to improve governance and compliance monitoring for Azure environments.
    • Support for Azure GovCloud: The discovery process accommodates Azure GovCloud environments by requiring specific configurations, ensuring broad applicability across Azure deployments.

    Discovery and Service Mapping Patterns finds Azure services on your cloud environment. Discovering some of these resources may require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.

    Pattern-based discovery and mapping requirements

    Verify the Microsoft Azure discovery prerequisites
    For more information, see the prerequisites section in Microsoft Azure Cloud components discovery using patterns.
    Enable the relevant pattern
    The pattern for this service is disabled by default. Starting with Visibility Content version 6.28.0, activating or deactivating a pattern won't be considered a customization, and it will continue to receive updates. Patterns that were previously activated or deactivated will reset to the latest predefined version after upgrading while retaining the last active field value. For more information on enabling patterns, see Activate a disabled pattern.
    Configure the Discovery schedule to support GovCloud
    Discovering Azure GovCloud (US) accounts requires using a datacenter URL when setting up an Azure service account. For more information, see Set up Azure service accounts.

    Discovery and Service Mapping Patterns application populates data in both CMDB and non-CMDB tables.

    Data stored in non-CMDB tables

    Discovery and Service Mapping Patterns application populates data in the non-CMDB tables when running the Azure - Service Endpoint Policy - Extended Inventory(LP) pattern.

    You can review the non-CMDB Azure tables by navigating to All > Configuration > Azure. You can also search the navigation filter for the specific pattern name.

    Table 1. Azure Service Endpoint Policy [cmdb_azure_service_endpoint_policy_service_endpoint_policy]
    Field Description
    Object Id [object_id] The unique identifier of the Azure resource.
    Kind [kind] The specific kind or stock-keeping unit (SKU) of the resource.
    DC Location [location] The geographic region where the resource is deployed.
    Resource Group [resource_group] The name of the resource group containing the resource.
    Subscription Id [subscription_id] The Globally Unique Identifier (GUID) of the subscription that owns the resource.
    Tenant Id [tenant_id] The GUID of the Azure AD tenant the resource belongs to.
    Provisioning State [provisioning_state] The current provisioning status of the resource.
    Configuration Item [configuration_item] References the Cloud Resource [cmdb_ci_cmp_resource] table.
    Table 2. Azure Service Endpoint Policy Definition [cmdb_azure_service_endpoint_policy_definition]
    Field Description
    Object Id [object_id] The unique identifier of the Azure resource.
    Name [name] The name assigned to the resource.
    Type [type] Type of resource. The value is set to microsoft.network/serviceendpointpolicies.
    Provisioning State [provisioning_state] The current provisioning status of the resource.
    Configuration Item [configuration_item] References the Cloud Resource [cmdb_ci_cmp_resource] table.
    Service [service] The specific Azure service related to the resource.

    Data stored in CMDB tables

    Discovery and Service Mapping Patterns application populates data in the CMDB when running the Azure - Service Endpoint Policy - Extended Inventory(LP) pattern.

    Table 3. Cloud Resource [cmdb_ci_cmp_resource]
    Field Description
    Object ID [object_id] The unique identifier of the Azure resource.
    Name [name] The name assigned to the resource.
    Location [location] The geographic region where the resource is deployed.
    Install Status [install_status] Install status of the resource. Default value is Installed.
    Operational status [operational_status] Operational status of the resource. Default value is Operational.
    Resource type [resource_type] Type of resource. The value is set to microsoft.network/serviceendpointpolicies.

    CI relationships

    The Azure - Service Endpoint Policy - Extended Inventory(LP) pattern creates these relationships to support Azure Service Endpoint Policy discovery.

    CI Relationship CI
    Azure Service Endpoint Policy Definition [cmdb_azure_service_endpoint_policy_definition] References Cloud Resource [cmdb_ci_cmp_resource]
    Cloud Subnet [cmdb_ci_cloud_subnet] Uses::Used by Cloud Resource [cmdb_ci_cmp_resource]
    Resource Group [cmdb_ci_resource_group] Contains::Contained by Cloud Resource [cmdb_ci_cmp_resource]
    Cloud Resource [cmdb_ci_cmp_resource] Hosted on::Hosts Azure Datacenter [cmdb_ci_azure_datacenter]
    Azure Service Endpoint Policy [cmdb_azure_service_endpoint_policy_service_endpoint_policy] References Cloud Resource [cmdb_ci_cmp_resource]

    Azure tag discovery

    The pattern collects tags and populates them in the Key Value [cmdb_key_value] table.
    Table 4. Key Value [cmdb_key_value]
    Field Description
    Key [key] Tag name.
    Value [value] Tag value.