Tags in Azure Change processing

[Jithin1]

We are leveraging Azure change processing to get Azure Events into ServiceNow. Change processing will bring the events and update or create a CI. But is there anyway for Azure change processing to bring in the Tags of the CI that is getting updated or Tags of the CI against which the event has occured?

For Alert driven discovery, which is still used in AWS event based discovery, a standalone discovery is initiated against the CI that has event, which discovers tags as well. But for Change processing how to get Tags of the CI as well?

[AJ-TechTrek]

Hi @Jithin1 ,

I dont think so, tags are populated by Azure Event based discovery, Refer the below screenshot which help you what is captured by Azure event based discovery.

https://docs.servicenow.com/bundle/washingtondc-it-operations-management/page/product/it-operations-...

https://www.servicenow.com/community/itom-articles/list-of-azure-tags-supported-by-pattern-discovery...

https://www.servicenow.com/community/itom-articles/mar-2023-azure-event-driven-discovery-with-azure-...

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0953853

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.

Thanks

AJ

Linkedin Profile:- https://www.linkedin.com/in/ajay-kumar-66a91385/

ServiceNow Community Rising Star 2024

[Jithin1]

Hi @AJ-TechTrek ,

Thanks for taking time out and responding to this query.

I was looking to figure out, if there is any way to obtain Tags in Azure change processing, which is a new mechanism to update CMDB for Azure event as mentioned in one of the links that you have shared. 

[Mar 2023] Azure Event Driven Discovery with Azure... - ServiceNow Community

But this have limited set of classes which have been configured. To add additional attributes, we need to update the response mapping. I am not sure how to add response mapping to get tags. 

We are getting the tags from the scheduled discovery using the patterns which has been listed down in the rest of links.

As we depend on Tags for certain internal process, the CI getting onboarded through the Azure change processing is not getting processed as it misses tags. Missing Tags of those CIs gets updated only when the pattern-based discovery is run, which is not close to real-time.

[Katie Irvine]

Did you manage to resolve this issue?