Updating Cloud Inventory Resource Inclusion Lists: Removing Entries to Enable New Azure LP Patterns DiscoverySummary<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } New Azure LP patterns have been introduced to enhance the discovery of several Azure resources, including Logic Apps, Service Bus entities, Application Insights, Data Factory, Key Vaults, and Data Protection Backup Vaults. These resources were previously discovered by the Azure Resource Inventory pattern. To ensure accurate discovery and proper management with the newly introduced patterns, the patterns supporting discovery of these resources first must be activated and then specific entries from the Cloud Inventory Resource Inclusion Lists table (sa_cloud_inventory_resource_whitelist) deleted. This will prevent the Azure Resource Inventory pattern from continuing to discover the same resources. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } August 2025 Instructions<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } 1. After upgrading to the August release, enable the new patterns delivered with the release. Azure - Compute Snapshot - Extended Inventory(LP)Azure - App Service App Service Plan - Extended Inventory(LP)Azure - Logic App - Extended Inventory(LP)Azure - Event Hub Namespace - Extended Inventory(LP)Azure - Event Grid System Topic - Extended Inventory(LP)Azure - Service Bus Queue - Extended Inventory(LP)Azure - Service Bus Topic - Extended Inventory(LP)Azure - Container Registry - Extended Inventory(LP)Azure - Application Insight Component - Extended Inventory(LP)Azure - Automation Account - Extended Inventory(LP)Azure - Compute Gallery Image Definition - Extended Inventory(LP)Azure - Data Factory - Extended Inventory(LP)Azure - Databricks Workspace - Extended Inventory(LP)Azure - Service Bus Namespace - Extended Inventory(LP)Azure - Key Vault - Extended Inventory(LP)Azure - Data Protection Backup Vault - Extended Inventory(LP)Azure - Networks IP Group - Extended Inventory(LP)Azure - Application Security Group - Extended Inventory(LP)Azure - Disk Encryption Set - Extended Inventory(LP)Azure - Managed Identity User Assigned Identity - Extended Inventory(LP)Azure - App Configuration Configuration Store - Extended Inventory(LP)Azure - Private Link Private Endpoint - Extended Inventory(LP) 2. To avoid duplicate discovery and ensure the new patterns are the only ones populating these resources, delete the following resource type records from:[sa_cloud_inventory_resource_whitelist] - Cloud Inventory Resource Inclusion Lists Existing OOTB Resource Types microsoft.apimanagement/servicemicrosoft.datafactory/factoriesmicrosoft.insights/componentsmicrosoft.keyvault/vaultsmicrosoft.logic/workflowsmicrosoft.servicebus/namespacesmicrosoft.web/serverfarmsmicrosoft.operationalinsights/workspaces Additional Resource Types (If Manually Added) microsoft.compute/snapshotsmicrosoft.eventhub/namespacesmicrosoft.eventgrid/systemtopicsmicrosoft.containerregistry/registriesmicrosoft.automation/automationaccountsmicrosoft.compute/galleries/imagesmicrosoft.databricks/workspacesmicrosoft.network/ipgroupsmicrosoft.network/applicationsecuritygroupsmicrosoft.compute/diskencryptionsetsmicrosoft.managedidentity/userassignedidentitiesmicrosoft.appconfiguration/configurationstoresmicrosoft.network/privateendpoints After completing the deletion of the above records, re-run Azure Cloud Discovery. This will ensure the new patterns exclusively discover the identified resources and the updated custom deletion strategy correctly manages them. If you don't plan to activate and use the listed patterns, no changes are needed. These two steps must be completed before running a new Cloud Discovery to avoid duplicate or inconsistent inventory data.