ServiceNow discovery creates duplicates for the resource type "Microsoft.Cache/Redis"DescriptionDuring Azure discovery activities, duplicate Configuration Items (CIs) are created on a recurring basis—typically after each daily execution of Azure discovery jobs. Two LP discovery patterns independently process the same Azure Redis Cache resources: 1. Azure Database (LP) Pattern Creates CIs in the cmdb_ci_cloud_database tablePopulates source_native_key using the Azure resource’s object_idImplements this behavior in the step: “Add source native key to cmdb_ci_cloud_database” 2. Azure Resource Inventory (LP) Pattern Creates CIs in the cmdb_ci_cmp_resource tableAlso populates source_native_key using the same object_idImplements this in the step: “Create Generic CI”Steps to Reproduce 1) Open Discovery SchedulesNavigate to Discovery > Schedules in the platform. 2) Select any Azure Cloud Service Account Discovery JobLocate a schedule configured to run Azure discovery using both: Azure Database (LP)Azure Resource Inventory (LP)(Example: Any Cloud Service Account discovery job associated with an Azure subscription.) 3) Run the Discovery Job ManuallyClick "Discover Now" to initiate the Azure discovery process for that service account. 4) Allow the Patterns to ExecuteWait for the following LP patterns to complete: Azure Database (LP) — discovers database resources including RedisAzure Resource Inventory (LP) — discovers generic cloud resources 5) Review the CMDB for Redis-related CIsSearch the CMDB for the Redis resource name under: cmdb_ci_cloud_databasecmdb_ci_cmp_resource 6) Observe Duplicate CI CreationVerify that: A Redis CI is created under cmdb_ci_cloud_database, andAn identical Redis CI is also created under cmdb_ci_cmp_resource 7) Confirm Duplicate sys_object_source EntriesCheck sys_object_source for multiple entries referencing the same Redis object_id, confirming that both patterns produced identical source_native_key values. Workaround To prevent redundant discovery of Redis resources by the Azure Resource Inventory (LP) pattern, remove the Redis resource type from the Cloud Inventory resource inclusion list. Workaround Steps Remove the entry for:Microsoft.Cache/Redisfrom the table:sa_cloud_inventory_resource_whitelist_list This change ensures that Redis resources are not processed as generic cloud resources by the Azure Resource Inventory (LP) pattern. Why This Workaround Is Effective Redis Cache behaves as a database-type resource in Azure.The Azure Database (LP) pattern is the appropriate and more accurate mechanism for discovering Redis resources.Removing Redis from the Cloud Inventory whitelist prevents the Azure Resource Inventory (LP) pattern from creating a second CI under cmdb_ci_cmp_resource.This eliminates the conflicting discovery paths, ensuring that only a single CI is created for each Redis resource, avoiding: Duplicate entriesReconciliation conflictsClass flip situations Related Problem: PRB1971439