Azure Plugin combining resources from different account labels

We have several Azure subscriptions (Account labels) with credentials entered in the plugin and it seems to be combining VMs from different subscriptions/accounts.

eg: 3 subscriptions (eg: corpprd, corpnonprd, corpsbx) all have VMs in them but the plugin seems to be mixing things up somehow. The middle account/subscription showing 253 VMs actually has 17.

These 2 subscriptions have 19 and 29 VMs respectively. Not 121 between them

Any other instances of/resolutions for this across the forum community?
Just checking here before opening a case.

It sounds a problem of VM visibility: if a VM is discoverable by many accounts, it will be associated to the last one that discovered it.

@IanDM, I am not going to rule out a bug of some sort but it is worth noting that unfortunately, plugins discover all instances, not just VMs (i.e. Infrastructure as a Service) where you manage the actual OS but also any PAAS, SAAS, instances that you may use. a ton may even be “appliances” (devices stood up by the particular public cloud provider for PAAS/SAAS offering that you don’t have access to whatsoever). I say unfortunately because i have raised this when the product first came out (HCL Software - Sign In) but still uncommitted and there just a ton of additional proxy records that you are never going to be able to have agent installed on… In most cases, if you look up the images they are provisioned with you would be able to deduce what those are but it is still annoying nonetheless.

Are you saying every subscription needs a dedicated limited application ID to prevent seeing VMs in subs other than the one it was used to add to the portal? I’m not sure I see the connection/understand the suggestion.

If we add a single subscription, only VMs under that sub are discovered. Why would adding another subscription cause VMs discovered to move/jump to different subscriptions. Is there some best practice in the docs I overlooked?

It’s not that it isn’t finding all VMs or finding VMs we are not interested in. Yes, we can see the VMs that are appliances related to storage and other services, but the issue is that the Plugin Portal is inconsistent about the subscription it records the VMs under. In some cases, VM in the console look like they are in an empty subscription, other cases subs with tens of VMs have 0.

After watching, it seems to be changing sometimes when the plugin portal refreshes against Azure. When I check now, subs that had VMs when I created this post a few hours ago have 0 VMs now. [In reality] We have VMs in more than 6 subscriptions but that’s all we see in the console now. The sub showing 467 VMs actually has 230 VMs (including TF deployed, appliances and PaaS

image

Probably best to open a case.

After the latest refresh:
image

Ah ok, yea, that does look like a bug. Have a case and see if Support can sort it out.