Rule 6 - Mapping of Azure Record Sets to ServiceNow Category and Sub-Category Values

Rule Synopsis

These are the rule/s that determine the ServiceNow Category and Sub-Category values for each Azure Resource Type.

Rule Details and Default

The rule/s are described by the mapping table shown below.

Resource Type	Category Value	Sub-Category Value
API Management Service	Resource	Cloud
Application Gateway	Resource	Cloud
App Service	Resource	Cloud
App Service Plan	Resource	Cloud
CDN Profile	Resource	Cloud
CDN Profile End Point	Resource	Cloud
Cognitive Services	Resource	Cloud
Container Registry	Resource	Cloud
Container Instance	Resource	Cloud
Container	Resource	Cloud
CosmosDb for MongoDb	Resource	Cloud
Azure Datacenter	Resource	Cloud
Azure Database for MySQL	Resource	Cloud
Azure Database for PostgreSQL	Resource	Cloud
Disk	Resource	Cloud
DNS Zone	Resource	Cloud
DNS A-Record	Resource	Cloud
DNS CNAME-Record	Resource	Cloud
Event Hub	Resource	Cloud
Express Route	Resource	Cloud
Frontdoor	Resource	Cloud
Frontdoor Frontend	Resource	Cloud
Frontdoor Frontend Endpoint	Resource	Cloud
Image	Resource	Cloud
Key Vault	Resource	Cloud
Kubernetes Service	Resource	Cloud
Load Balancer	Resource	Cloud
Local Network Gateway	Resource	Cloud
Logic App	Resource	Cloud
NAT Gatway	Resource	Cloud
Network Security Group	Resource	Cloud
Network Interface	Resource	Cloud
Private DNS Zone	Resource	Cloud
Private DNS A-Record	Resource	Cloud
Private DNS CNAME-Record	Resource	Cloud
Private End Point	Resource	Cloud
Public IP Address	Resource	Cloud
Recovery Services Vault	Resource	Cloud
Resource Group	Resource	Cloud
Snapshot	Resource	Cloud
Storage Account	Resource	Cloud
Subscription	Resource	Cloud
Virtual Machine (Instance)	Resource	Cloud
Virtual Machine Scale Set	Resource	Cloud
Virtual Networks	Resource	Cloud
Virtual Network Gateway	Resource	Cloud
Virtual Network Subnet	Resource	Cloud

Override Options

Context

Customers may consider changing these mappings to meet the requirements of a customer specific instance of ServiceNow (e.g. to ensure the Category and Sub-Category values operate correctly for your business processes/workflows).

Options

The Category and Sub-Category values can be changed for each Azure Record Set.

Overriding via Connection Settings

N/A

Additional Information

N/A

Support Model for Rule Overrides

Question: Can overrides be performed by customers without a Syncfish Extended Implementation and Support Plan?

Answer: No (a plan is needed - see below)

Question: Which Syncfish Extended Implementation and Support Plan is required to obtain overrides of this rule

Answer: Either a Bronze Plan, Silver Plan or Gold Plan