Azure Discovery — How to determine licensed CI count, deduplication behavior, and scope restriction<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Issue Customer needs guidance on how ServiceNow Discovery handles Azure resources for licensing. Three specific questions are commonly raised: How to determine the licensed CI count and how many CIs are currently discovered for Azure.Whether discovering the same CI twice causes the license usage to count twice.How to restrict Azure Discovery scope to specific resource groups or subscriptions. Symptoms Unable to determine remaining Azure CI discovery capacity from current license entitlement.Uncertainty about whether duplicate CI discovery inflates license consumption.Need to limit Azure Discovery scope to specific resource groups or subscriptions rather than the full tenant. Cause This is not a product defect. These are standard product behavior questions about how ServiceNow Discovery handles Azure resources for licensing entitlement, deduplication, and scope. The behavior is by design and configurable through Azure access permissions, dedicated subscription schedules, and ITOM/OT SU Licensing plugin updates. Resolution View licensed CI count (Entitlement): Navigate to System Diagnostics > License Management. Locate the ITOM Discovery or ITOM Visibility license entry. The Quantity (or Entitled) column reflects the licensed CI count.View currently discovered Azure CIs: Navigate to All > Configuration > CI Class Manager (or query the cmdb_ci table directly) and filter by Discovery Source = ServiceNow and cloud provider = Azure. Alternatively, the ITOM Visibility Dashboard provides a summary view of discovered CIs by cloud provider.Calculate remaining capacity: Remaining discoverable items = Licensed Count - Currently Discovered Count.Subscription model: Azure tenant-level discovery only finds subscription metadata. Each Azure subscription requires its own discovery schedule and credentials to discover the resources within it.Duplicate CI / deduplication: If a CI is discovered twice and the deduplication rules fail to merge them, license usage may count it twice. Update sets in the Service Mapping plugin v3.11.0 resolve this scenario by improving deduplication behavior.Restrict discovery scope: To restrict discovery to specific resource groups or subscriptions, limit the Azure access permissions granted to the Service Principal / credential to only those resource groups or subscriptions. ServiceNow Discovery will only discover what its credential has access to in Azure.