Service Graph Connector for Microsoft Azure - Resource Inclusion Handling

[jevonweiman]

Hi,

Does anyone know of a method to selectively define generic cloud resource CI creation from SGC Azure?

For example if you want to prevent a specific generic cloud resource and allow other generic resources using SGC Azure.

I have two ideas that I’m noodling on: restrict the access to the resource object or disable the data import, both approaches are unappealing.

Does a method exists to define the generic resource types for SGC Azure perhaps like the Cloud Inventory Resource Inclusion approach used in patterned discovery?

Note from the SGC concept page:

Note: The connector utilizes the Service Graph Resource Inclusion Whitelist [sn_cmdb_int_util_service_graph_resource_inclusion_whitelist] table to differentiate between generic and other supported resource types.

The connector first populates all supported resources in the Service Graph Resource Inclusion Whitelist [sn_cmdb_int_util_service_graph_resource_inclusion_whitelist] table. These resources, categorized under their respective supported resource types, have specific data sources designated for ingestion within the connector. When the SG-Azure Generic Resources data source is executed and retrieves unsupported resource types, they are added to the Service Graph Resource Inclusion Whitelist [sn_cmdb_int_util_service_graph_resource_inclusion_whitelist] table and categorized as generic.

Service Graph Connector for Microsoft Azure (1.9.1) (servicenow.com)