Customer is using Discovery Patterns for Azure Cloud Discovery. No Service Mapping.
All the examples below are the result of OOTB Azure discovery patterns.
Consider this example, an Azure Resource Group. The relationships created by the pattern show a correct downstream and upstream relationship - with the Azure Datacenter naturally being upstream.
One of the downstream items is a Computer Security Group. This has an upstream relationship to the Resource Group (which is good), but then has a downstream relationship back to the datacenter.
One could theoretically click through the downstream relationships forever as moving to the datacenter will take you back to the top level, and so on. This is demonstrated by showing L2 levels in the relationships, which does not make any sense. The Computer Security Group DOES NOT contain Resource Groups. It is CONTAINED BY one resource group.
Viewing the dependency map confirms the upside down nature. Somehow the resource groups and subscription are downstream which would eventually lead back to where we started.
I appreciate that the map often shows a direction which is not intuitive. It is the cyclical relationship which is doesn't make any sense.
This (Parent) Hosted On relationship is created throughout the Azure estate, at least in forty or so classes, and is confusing CMDB stakeholders. I am not sure why it exists.
At the very least, it should be a "Hosted by (Parent)" relationship, then it would appear upstream rather than downstream.
Or are we missing the point ... some advice would be greatly appreciated.
