The Insight Azure integration allows the configuration of multiple subscriptions over the same object schema.

However when configuring multiple subscriptions and targeting the same object types in all subscriptions some data inconsistencies can manifest.

Example:

1. Configure multiple subscriptions over the same object schema and targeting the same object schema.
2. The default configuration for some object types (ex. Virtual Machines) in the import is set such as any previously object (Virtual Machines) not found on the subscription has the attribute status set to not found:
   
3. Now when manually or automatically launching the sync on all those subscriptions, it will happen that as every subscriptions has its own virtual machines, the next scan for another subscription will not find those objects and therefore will mark them as attribute status not found.

At the moment the only way to overcome this is to create multiple object types manually in the schema under an abstract structure such as:

• abstract parent object type > Virtual Machines
• child object types under the parent Virtual Machines:
  • Virtual Machines subscription 1
  • Virtual Machines subscription 2
• then map each import configuration manually to the child object type. This way the parent one still will show all the child objects virtual machines.

Please improve this behaviour by providing a way to distinguish the objects related to each subscriptions during the import.

attribute to edit when missing objects