--- sourceDocument: Yokohama IT Operations Management sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management Release : - yokohama ft:locale : - en-US ft:publication_title : - Yokohama IT Operations Management ft:clusterId : - itom bundleId : - itom workflow : - Technology --- # Azure Private Link Private Endpoint # Azure Private Link Private Endpoint pattern-based discovery {#ariaid-title1} * Release version: Yokohama * * Updated August 11, 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) 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 Private Link Private Endpoint pattern-based discovery This pattern-based discovery enables ServiceNow customers to discover and map Azure Private Link Private Endpoint resources within their cloud environments. It uses Discovery and Service Mapping Patterns to identify Azure services, populating relevant data into both CMDB and non-CMDB tables. This functionality is essential for maintaining accurate cloud resource inventories and understanding their relationships and statuses. Show full answer Show less ## Key Features * **Pattern Activation:** The Azure Private Link Private Endpoint pattern is disabled by default and requires activation. Starting with Visibility Content version 6.28.0, enabling or disabling patterns is treated as a non-customization and patterns update automatically after upgrades. * **Discovery Prerequisites:** Microsoft Azure discovery prerequisites must be met. For Azure GovCloud (US) discovery, configuration of the discovery schedule with a datacenter URL is necessary. * **Data Storage:** * **Non-CMDB Tables:** When running the Azure - Private Link Private Endpoint - Extended Inventory (LP) pattern, the application stores data in non-CMDB Azure tables accessible via the configuration navigation. Key fields include kind, location, object ID, provisioning state, resource group, subscription ID, tenant ID, and a reference to the related Cloud Resource record. * **CMDB Tables:** The same pattern populates the Cloud Resource \[cmdbcicmpresource\] table with essential information such as install status, location, name, object ID, operational status, and resource type (set as microsoft.network/privateendpoints). * **Configuration Item Relationships:** The discovery pattern creates relationships between cloud resources and resource groups, datacenters, and private endpoints to support comprehensive mapping and dependency analysis. * **Tag Discovery:** The pattern collects Azure tags associated with private endpoints and stores them in the Key Value \[cmdbkeyvalue\] table, capturing tag names and values for enhanced resource categorization. ## Practical Benefits for ServiceNow Customers * Enables automated, accurate discovery and mapping of Azure Private Link Private Endpoint resources to maintain an up-to-date CMDB. * Supports compliance and governance by providing visibility into provisioning states, operational statuses, and resource groupings. * Facilitates cloud resource management by capturing detailed attributes and relationships, improving service impact analysis and operational decision-making. * Enhances tagging and categorization capabilities, aiding in cost allocation, reporting, and resource organization. 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 {#azure-private-link-private-endpoint__section_ipy_53n_jfc} Verify the Microsoft Azure discovery prerequisites{#azure-private-link-private-endpoint__verify-azure-discovery-prerequisites-dlentry} : For more information, see the prerequisites section in [Microsoft Azure Cloud components discovery using patterns](https://servicenow-prod.fluidtopics.net/JeDZ0tlC9eLF5fei5qSv3w "Discovery uses multiple patterns to discover components of the Microsoft Azure Cloud deployment during horizontal discovery. Discovering some of these resources may require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store."). Enable the relevant pattern{#azure-private-link-private-endpoint__enable-pattern-reuse-dlentry} : 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](https://servicenow-prod.fluidtopics.net/R5W5GP640V_5uNIhVNRPCw "If you want to use a pattern for discovery that's disabled by default, activate it manually.").{#azure-private-link-private-endpoint__activating-disabled-pattern-not-customization} Configure the Discovery schedule to support GovCloud{#azure-private-link-private-endpoint__configure-govcloud-azure-dlentry} : 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](https://servicenow-prod.fluidtopics.net/wA59_lRoV_0PzpuODHnNjA "Create and configure cloud service accounts at ServiceNow AI Platform for the corresponding Microsoft Azure accounts.").{#azure-private-link-private-endpoint__configure-govcloud-azure-dd} {#azure-private-link-private-endpoint__configure-govcloud-azure-dd} Discovery and Service Mapping Patterns application populates data in both CMDB and non-CMDB tables. ## Data stored in non-CMDB tables {#azure-private-link-private-endpoint__section_aq4_qkq_hfc} Discovery and Service Mapping Patterns application populates data in the non-CMDB table when running the Azure - Private Link Private Endpoint - Extended Inventory(LP) pattern. You can review the non-CMDB Azure tables by navigating to AllConfigurationAzure. You can also search the navigation filter for the specific pattern name. {#azure-private-link-private-endpoint__section_aq4_qkq_hfc__entry__2} | Field | Description | |-|-| | Kind \[kind\] | The specific category or variant of the resource type. | | Location \[location\] | The geographic region where the resource is deployed. | | Object Id \[object_id\] | The unique identifier for the resource. | | Provisioning State \[provisioning_state\] | The current provisioning or deployment state of the resource. | | Resource Group \[resource_group\] | Name of the resource group. | | Subscription ID \[subscription_id\] | The subscription ID. | | Tenant ID \[tenant_id\] | The identifier for the tenant associated with the resource. | | Configuration Item \[configuration_item\] | References the Cloud Resource \[cmdb_ci_cmp_resource\] table. | [Table 1. Azure Private Link - Private Endpoint \[cmdb_azure_private_link_private_endpoint\]] ## Data stored in CMDB tables Discovery and Service Mapping Patterns application populates data in the CMDB when running the Azure - Private Link Private Endpoint - Extended Inventory(LP) pattern. {#azure-private-link-private-endpoint__entry__20} | Field | Description | |-|-| | Install Status \[install_status\] | Install status of the resource. Default value is Installed. | | Location \[location\] | The geographic region where the resource is deployed. | | Name \[name\] | The name of the resource. | | Object ID \[object_id\] | The unique identifier for the resource. | | 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/privateendpoints. | [Table 2. Cloud Resource \[cmdb_ci_cmp_resource\]] ## CI relationships The pattern creates these relationships to support discovery. {#azure-private-link-private-endpoint__entry__35} | CI | Relationship | CI | |-|-|-| | 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 Private Link - Private Endpoint \[cmdb_azure_private_link_private_endpoint\] | References | Cloud Resource \[cmdb_ci_cmp_resource\] | [ ] ## Azure tag discovery {#azure-private-link-private-endpoint__section_ezc_jwt_jfc} The pattern collects tags and populates them in the Key Value \[cmdb_key_value\] table. {#azure-private-link-private-endpoint__table_axq_spc_y2c__entry__2} | Field | Description | |-|-| | Key \[key\] | Tag name. | | Value \[value\] | Tag value. | [Table 3. Key Value \[cmdb_key_value\]] {#azure-private-link-private-endpoint__table_axq_spc_y2c} *[\>]: and then