Skip to main content

Microsoft Azure Network

Microsoft Azure

The Azure Network connector integrates with Microsoft Azure and synchronizes the network resources that determine a workload's internet exposure and blast radius, using the Azure Resource Manager APIs (via the Azure SDK for Java). For each configured subscription it lists network interfaces, public IP addresses, network security groups, virtual networks, virtual network peerings, route tables, load balancers, and application gateways, and maps each to a Cloud Resource connector object.

Every resource carries its full Azure Resource Manager ID in RESOURCE_ID, and the references between resources are published as the same ARM IDs — so a network interface joins to the virtual machine that owns it, to the security group governing it, and to the public IP and subnet it is bound to, without any additional lookup. The network interface is the hinge of that chain: it is the object that ties a virtual machine to the addresses and rules that expose it.

When no subscription is configured the connector enumerates every subscription accessible to the configured Azure AD application; otherwise it processes only the comma-separated subscriptions provided. Subscriptions and resources are processed in parallel, and a subscription the service principal cannot read is logged and skipped rather than failing the whole sync.


Data retrieved from Microsoft Azure Network

Connector ObjectRequiredMaps to Data Model
Network InterfaceYesCloud Resource
Public IP AddressYesCloud Resource
Network Security GroupYesCloud Resource
Virtual NetworkYesCloud Resource
Virtual Network PeeringYesCloud Resource
Route TableYesCloud Resource
Load BalancerYesCloud Resource
Application GatewayYesCloud Resource

Model relationships

note

For detailed steps on how to view the data retrieved from Microsoft Azure Network in the Brinqa Platform, see How to view your data.

warning

The Public IP Address row is the one join here that matches on a value, not on a resource ID. A dynamically allocated address is released and reassigned, so the same address seen on a virtual machine and on a public IP resource is not proof they are the same resource at the same moment.

Prefer the resource-ID path, which is exact and stable: Virtual Machine NETWORK_INTERFACE_IDS → Network Interface RESOURCE_ID, then Network Interface IP_CONFIGURATIONS[].publicIpId → Public IP Address RESOURCE_ID (an intra-connector link, drawn as the Network Interface → Public IP Address edge above). Use the address match only to corroborate it.