Skip to main content
Version: 0.10

Azure managed devices (WIP)

Pulls device objects from Entra ID via Microsoft Graph — everything registered or joined to the directory, with its compliance and management state.

Type nameazure_managed_devices
CreatesEndpoints
Runs onA sensor with outbound reach to graph.microsoft.com
Presence flagazure_md_exits
Field prefixazure_md_

What it contributes​

This is the directory's view of a device rather than an agent's view, so it is strong on enrolment and compliance and weak on live host detail.

  • Identity — object ID, device ID, display name, domain name, account enabled
  • Enrolment — enrollment type, enrollment profile name, registration date, device ownership, trust type, source type, external source name
  • Management — is managed, is compliant, is rooted, management type, MDM app ID, compliance expiration
  • Platform — operating system, operating system version, manufacturer, model, device version
  • Sync state — on-premises sync enabled, on-premises last sync, approximate last sign-in, created and deleted timestamps
  • Extras — device category, profile type, device metadata, system labels, physical IDs, extension attributes, alternative security IDs

It writes the shared fields names (with fqdn and domains when the display name is a qualified name), os, os_vendor, type and updated_at. It does not write private_ip or MAC addresses: the device object carries neither.

The approximate last sign-in is the sighting it reports for last_seen, and the earlier of the registration and creation times is its first_seen. There is no staleness filter: every device the listing returns is imported, whatever its last sign-in.

Deleted devices come back too

azure_md_deleted_date_time is populated for objects in the soft-delete window. A device with that field set is not a live asset — filter on it before treating this source as a list of active machines.

Requirements​

The integration is outbound-only: it is a scheduled Graph client, so nothing is installed in the tenant, nothing runs on the devices themselves, 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 integrationgraph.microsoft.com — the device objectsHTTPS over TCP443

Two hosts, because authentication and data live in different services: the run takes a client-credentials token from the first, then pages /v1.0/devices from the second. If the sensor reaches the internet through a proxy, point Proxy settings at it rather than opening direct egress.

Access in Entra ID​

NeedWhy
An account that can register applicationsThe credential is an app registration with a client secret
An account that can grant tenant-wide admin consentDevice.Read.All is an application permission, which is inert until consented — see Permissions in Entra ID

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 work is a paged HTTPS read per run, so it adds no meaningful load and needs no local storage.

Configuration​

FieldRequiredNotes
NameYesLabel for this instance
Application (client) IDYesApp registration client ID
Directory (tenant) IDYesEntra tenant ID
Client SecretNoRequired in practice for client-credentials auth. Write-only: once saved, the console shows a locked box with Replace and Remove, and never displays it again
Proxy settingsNohttp://host:port
SensorYesSensor that will run the integration
Ignore SSLYesNot used: the sensor always validates Microsoft's certificates

Permissions in Entra ID​

Register an application, add an application permission on Microsoft Graph, and grant admin consent:

APIPermissionType
Microsoft GraphDevice.Read.AllApplication

The integration authenticates with client credentials against login.microsoftonline.com for the https://graph.microsoft.com/.default scope, then pages /v1.0/devices. That listing is the only Graph call it makes.

Test connection takes a token and reads one device from the same listing, so a missing admin consent for Device.Read.All shows up there rather than on the first scheduled run.

One app registration can serve several integrations

Azure users, Azure VMs and Windows Defender all use app-registration credentials. Reusing one registration with the union of the required permissions is fine and often simpler to rotate — just keep it distinct from registrations used by anything other than Velum Edge.

Matching​

Each device is matched to an existing endpoint by the first rule that finds one:

  1. Object ID
  2. Device ID
  3. Display name, as both the Azure display name and a host name
  4. Azure display name alone
  5. Host name together with the OS vendor
  6. Host name alone

A device that matches nothing creates a new endpoint, subject to the template's On New Asset Discovered action.

See also​