Azure Datacenter dependent on Cloud Service Account?

Niklas Peterson · ‎09-15-2022

Hi,

When running Azure Discovery, Azure Datacenters are created per Service Account. Instead of having one West Europe Datacenter it creates one per Service Account. When you have lots of Azure subscriptions that means thousands of Azure Datacenters.

The identification rule is Dependant and there is a dependant relationship between Azure Datacenter class and Cloud Service Account class, so from that perspective it is doing what it is being told.

But why? What's the point of having one Azure Datacenter per Service Account? Wouldn't it make more sense to have just one West Europe and relate all Service Accounts to that one? What am I missing?

Regards
Niklas

Harneet Sital · ‎09-15-2022

Hi @niklaspeterson

We have exactly the same issue with GCP Cloud Discovery and the ServiceNow support team has come back with this -

* There is no fix for multiple datacenters. We build datacenters for each service account and it is by design*

Ideally, as per the design, the relationships are formed with Service Accounts and Datacenters hence each record is considered as unique. Can't even clean up, they will get created again.

I could find this article too which confirms the same and seems like there is no fix to this - https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1002544

-Harneet Sital
Request you to please mark my answer as helpful or correct based on the impact
Find all my ServiceNow articles here

View solution in original post

Niklas Peterson · ‎09-16-2022

Hi @Ram Devanathan ,

Thanks for explaining further. We are just doing Discovery at the moment and my concern is the ~50000 datacenter records we get due to our amount of subscriptions. We cannot really ignore that it looks duplicated and we cannot skip the populatation since it's kind of fundamental to the Azure patterns.

Looking forward to a future improvement of this.

Regards,
Niklas

Harneet Sital · ‎09-16-2022

@niklaspeterson

We have also created an idea so this can be potentially fixed early and have extended the idea to all other tables as well which has duplicated data. Feel free to upvote the idea so this can be prioritized -

https://community.servicenow.com/community?id=view_idea&sysparm_idea_id=94078b50db829d5cbb4a474d1396...

Ram Devanathan1 · ‎09-16-2022

Thank you Harneet for logging this idea, i will follow up on this.

Ram Devanathan1 · ‎09-16-2022

I hear you folks. It is not gone unnoticed with us, just that getting a change of this magnitude is not easy to bring around, suffice it to say it is high on our architectural priority.

will keep you posted. Happy to setup a meeting to review the ideas.

Please reach out from your official email id on ramkumar<dot>devanathan<at>servicenow<dot>com

Shreya Jain1 · ‎01-03-2023

@Niklas Peterson - Did you implement any workaround solution for this?