Automating Tag-Based Service Mapping for Untagged Azure CIs (Zurich)

[bipinksingh]

Hi Everyone,

I am working on implementing Tag-Based Service Mapping for existing Application Services in ServiceNow and would like some guidance on the best scalable approach.

Current setup:

- We already have existing Application Services.

- I created a Tag-Based Service Family using tags:

  - "ApplicationServiceId"

  - "Environment"

- I generated candidates and used them to populate/tag the existing Application Services.

- Azure resources are being discovered and tags are getting imported into CMDB.

Example:

- "ApplicationServiceId = SNSVC**********"

- "Environment = Non Production"

Current objective:

I want to automate the process so that whenever any new Azure resource/CI is created in future with the same tags, it should automatically become part of the correct existing Application Service and update the service map without any manual candidate generation or manual tagging activity.

My questions:

1. Is using “Populate Service → Tags → Use a list of tags” the correct long-term approach for this scenario?

2. Will Service Mapping automatically update the existing Application Service whenever new Azure CIs are discovered with matching tags?

3. Is there a better or more scalable approach recommended for enterprise environments?

4. Has anyone implemented a dynamic tag-based population model for Azure cloud resources at scale?

Any suggestions or best practices would be appreciated.