Skip to main content
Version: 0.10

Azure VMs (WIP)

Enumerates the subscriptions a service principal can see and imports their virtual machines, resolving each one's networking through its network interfaces and public IPs.

Type nameazure_assets
CreatesEndpoints
Runs onA sensor with outbound reach to management.azure.com
Presence flagazure_exists
Field prefixazure_

What it contributes​

Unlike the directory- and agent-based sources, this one reports infrastructure — what exists in the subscription, whether or not anything is installed on it.

  • Resource identity — resource ID, subscription ID, location, time created
  • Sizing and state — VM size, hardware profile size, VM status, provisioning state, hibernation capability
  • Networking — private IP, public IP, MAC, hostname, subnet, network interface IDs
  • Image — publisher, offer, SKU, version and exact version of the source image, and a combined OS description built from them
  • OS disk — OS type, disk name, create option, caching
  • OS profile — computer name, admin username, Linux SSH public key data
  • Security profile — security type, secure boot enabled, vTPM enabled

It writes the shared fields names (from the VM's resource name, with fqdn and domains when that is a qualified name), os, os_vendor, type, mac, private_ip, last_public_ip and updated_at:

  • type is Server unless the image is a desktop OS, such as a Windows 10 or 11 image.
  • mac gets the MAC of every network interface, added to the MACs other sources wrote rather than replacing them. Placeholder addresses that many machines share are never written.
  • private_ip and last_public_ip list the addresses of every IP configuration. An IP configuration with no public IP contributes N/A to last_public_ip.

last_seen is the time of the scan, for every VM listed, running or stopped, and first_seen is the VM's creation time.

This is how you find the machines nothing else sees

A VM with no EDR agent, no directory join and no Nessus agent is invisible to every other integration but present here. Comparing azure_exists against cs_exits or defender_exits is a direct agent-coverage report for your Azure estate.

Requirements​

The integration is outbound-only: it reads Azure Resource Manager on a schedule, so nothing is installed in the subscription, nothing runs inside the VMs, and nothing has to reach into the deployment.

Network access​

FromToProtocolPort
The sensor running the integrationlogin.microsoftonline.com — the token endpointHTTPS over TCP443
The sensor running the integrationmanagement.azure.com — Azure Resource ManagerHTTPS over TCP443

Two hosts, because authentication and data live in different services: the run takes a client-credentials token from the first, then reads subscriptions, virtual machines, NICs, public IPs, each VM's instance view and virtual networks from the second. If the sensor reaches the internet through a proxy, point Proxy settings at it rather than opening direct egress.

Access in Azure​

NeedWhy
An account that can create a service principalThe credential is an app registration with a client secret
An account that can assign Azure RBAC roles at the intended scopeThis integration uses Resource Manager, so access is a Reader role assignment rather than a consented Graph permission — assigning it needs Owner or User Access Administrator at that scope. See Permissions in Azure

Reader on a management group rather than per subscription is the assignment that keeps coverage correct as subscriptions are added — the warning under Permissions in Azure explains why.

In this deployment​

NeedWhy
A registered, healthy sensorThe integration runs on a sensor, on the platform's schedule — see Sensors

There are no special host requirements beyond a sensor that is checking in. The call count scales with the number of subscriptions and VMs, not with anything on the sensor host.

Configuration​

FieldRequiredNotes
NameYesLabel for this instance
Tenant IDYesEntra tenant ID
Client IDYesService principal client ID
Client SecretYesService principal secret. Write-only: once saved, the console shows a locked box with Replace and never displays it again
Proxy settingsNohttp://host:port
SensorYesSensor that will run the integration

There is no Ignore SSL field: the sensor always validates Microsoft's certificates.

Its Ignore of host is offline default is 180 days rather than the usual platform default. The run does not apply it today: every VM the subscriptions list is imported, whatever its power state.

Permissions in Azure​

This integration uses Azure Resource Manager, not Graph, so its permissions are Azure RBAC role assignments rather than app permissions:

ScopeRole
Each subscription to be discoveredReader

It authenticates for the https://management.azure.com/.default scope, lists /subscriptions, and then reads, per subscription: /providers/Microsoft.Compute/virtualMachines, /providers/Microsoft.Network/networkInterfaces, /providers/Microsoft.Network/publicIPAddresses and /providers/Microsoft.Network/virtualNetworks, plus each VM's instanceView for its power state. The virtual networks are read but not used for assets today. All of these are read operations that Reader covers.

Test connection lists the subscriptions, fails if none is visible (the shape a missing role assignment takes), and lists the VMs of the first subscription to prove Compute read access.

Coverage equals role assignments

The integration discovers only the subscriptions the service principal is assigned on. A subscription created later, or one assigned to a different management group, silently will not appear. Assign Reader at the management group covering everything you want inventoried, and re-check after tenant reorganisations.

Matching​

Each VM is matched to an existing endpoint by its Azure resource ID, then by host name. A VM that matches nothing creates a new endpoint, subject to the template's On New Asset Discovered action. A VM rebuilt under the same name gets a new resource ID, so it is matched by name.

See also​