Azure Datacenter dependent on Cloud Service Account?

[Niklas Peterson]

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 · Accepted solution]

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

[Niklas Peterson]

Thanks @Harneet Sital !

Bit curious to see what would happen if I change the identification rule to independent....

Regards,
Niklas

[Shantanu1]

I updated the identification rule for the logical datacenter rule and made it "independent". I was able to get all the information of service accounts/subscriptions on one unique logical datacenter. Same process worked for AWS & GCP.

[Ram Devanathan1]

As Harneet says this is by design. There's a little bit of history to this design, which came from the original design on VMware model was built. if you know vCenter setup, the datacenter (which groups clusters) is really logical there, not a physical location. That unfortunately has become the default model and this is how we have taken this forward. there's initiatives to change this model in the roadmap, so the datacenter details for each CI is just an attribute, and the datacenters are unique.

For now though, my recommendation is - don't get to the level of the records as it can be confusing and it might look all duplicated. use our cloud operations workspace app to view the records through the cloud resources inventory dashboard - this also gives new set of tables which list the datacenter and account in the same flat record.

install the cloud operations workspace store app or Performance Analytics content pack for Cloud Resources.