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.

[SK Chand Basha]

Hi @bipinksingh 

If want to automate the process need to trigger the Scheduled Jobs which is using to " Recaclulate Service"

There is Scheduled job "Generate Candidates for Service by Tags" which is used to update candidates

Once new Tags comes with that application service without wait for scheduled time you can trigger on demand by Flow.

[bipinksingh]

My issue is that the Tags are still not added in Azure, so those scheduled Jobs will not populate the candidate as per my Tag based family. 

I want to know if I know the tags that will be added in future in Azure so can I add them to current existing services with below steps and is that best practice ? 

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? (like with an Background Script).

[Sam Webb]

If the resources are not tagged in the cloud, yet, but will be according to policy - you can use the "update service candidates" feature on the tag-based Service Family. When they are, then a candidate will be created.

Once you have manually created a Service instance and a candidate exists, you are able to populate it using said identified candidate:

https://www.servicenow.com/community/itom-articles/populating-existing-service-instances-with-tag-ba...

You should not be looking to work around having the Cloud team tag resources, unless your intent is to capture connections to previously tagged resources - in which case you can look into traversal rules.

Hope that helps!

Sam