Subscription and Resource Group Relationships

Virima now automatically creates relationships from Azure Subscription CIs to Azure Resource Group CIs during Azure import. The resulting hierarchy gives a clear, navigable view of your Azure environment in the CMDB, showing which resource groups belong to each subscription and which Azure CIs belong to each resource group.

Where the relationships appear

The new relationships are visible in the following locations:

Location	What changed
CMDB > Azure Resource Group CI > Relationships tab	Lists all Azure CIs that belong to the resource group via the Contains relationship.
CMDB > Azure Subscription CI > Relationships tab	Lists the resource groups that belong to the subscription and the Azure services that depend on them.
ViVID and dependency maps	Azure subscription-to-resource-group containment is now visible in topology and dependency map views.

Relationship types created

The following relationships are created automatically during Azure import:

Relationship	Example
Azure Subscription > Contains > Azure Resource Group	subscription-prod contains rg-production.
Azure Resource Group > Contains > Azure CI	rg-production contains vm-web-01.

Procedure

Complete the following steps after upgrading to v6.1.2 to generate and verify the new relationships.

Include resource groups in the Azure import.

When configuring an Azure import, confirm that Resource Groups is selected in the import items list. Without this selection, the subscription-to-resource-group relationships are not created.
Re-run the Azure import.

Trigger a new Azure import, or wait for the next scheduled import to run. Subscription-to-resource-group relationships are created automatically during the import.
Verify the created relationships.

After the import completes, confirm that the new relationships are in place:
1. Go to CMDB and open any Azure Subscription CI.
2. Open the Relationships tab.
3. Confirm that the expected resource groups appear under the Contains relationship.

Note: Relationships are created only during a successful Azure import. If you do not see the expected relationships, re-run the import and confirm that Resource Groups is included in the import items.