Why are Azure subscriptions populated as CIs in two different classes?

[Johannes]

Our Azure subscriptions are put in two different classes, e.g.:

Classes are OOTB:

The CIs in these two tables are related

Does anybody know why the subscriptions are placed in two different tables?

[Dr Atul G- LNG]

Hi @Johannes 

Might be helpful

https://www.servicenow.com/community/itom-forum/mapping-cis-in-azure/m-p/969744

[Johannes]

No, that post talks about Azure discovery in general.

I am trying to understand why subscriptions are represented as CIs twice in two different classes.

[Dr Atul G- LNG]

Sorry, I miss understood.

@AJ_TechTrek any thoughts. 

[Johannes · Accepted solution]

I read a bit about "Azure and AWS accounts and subscriptions" here:
https://learn.microsoft.com/bs-latn-ba/azure/architecture/aws-professional/accounts

I guess my organization uses the same names on the Azure accounts as the Azure subscriptions, and thus made me believe they represented the same objects.