Microsoft Endpoint Configuration Management ConfigMgr Device Lookup

Version 1.0.0

Find a Configuration Manager device by name and read its full record and discovered system.

1 workflow 1 source API 1 provider
View Spec View on GitHub ComplianceConfiguration ManagementDevice ManagementEndpoint ManagementMobile Device ManagementPatch ManagementSoftware DeploymentArazzoWorkflows

Provider

microsoft-endpoint-configuration-management

Workflows

configmgr-device-lookup
Resolve a device by name, read it by id, and correlate its discovered system.
Lists devices via the versioned route filtered by name, reads the matched device by id, and lists discovered systems filtered by the same name.
3 steps inputs: deviceName outputs: device, matchedDeviceId, systems
1
findDevice
List devices via the versioned route filtered to the supplied name.
2
getDevice
Read the matched device's full record by id via the versioned route.
3
correlateSystem
Query discovered system resources filtered by the same name to correlate discovery data.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Microsoft Endpoint Configuration Management ConfigMgr Device Lookup
  summary: Find a Configuration Manager device by name and read its full record and discovered system.
  description: >-
    A Configuration Manager AdminService device investigation flow. The
    workflow lists devices via the versioned route filtered by name, reads the
    matched device's full record by id, and then queries the discovered system
    resources to correlate the device with its underlying SMS_R_System
    discovery data. Every step spells out its request inline so the flow can be
    read and executed without opening the underlying OpenAPI description.
  version: 1.0.0
sourceDescriptions:
- name: devicesApi
  url: ../openapi/microsoft-endpoint-configuration-management-devices-api-openapi.yml
  type: openapi
workflows:
- workflowId: configmgr-device-lookup
  summary: Resolve a device by name, read it by id, and correlate its discovered system.
  description: >-
    Lists devices via the versioned route filtered by name, reads the matched
    device by id, and lists discovered systems filtered by the same name.
  inputs:
    type: object
    required:
    - deviceName
    properties:
      deviceName:
        type: string
        description: The name of the device to resolve.
  steps:
  - stepId: findDevice
    description: List devices via the versioned route filtered to the supplied name.
    operationId: listDevicesV1
    parameters:
    - name: $filter
      in: query
      value: "Name eq '$inputs.deviceName'"
    - name: Authorization
      in: header
      value: "Negotiate"
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      matchedDeviceId: $response.body#/value/0/MachineId
      devices: $response.body#/value
    onSuccess:
    - name: deviceFound
      type: goto
      stepId: getDevice
      criteria:
      - context: $response.body
        condition: $.value.length > 0
        type: jsonpath
    - name: deviceNotFound
      type: end
      criteria:
      - context: $response.body
        condition: $.value.length == 0
        type: jsonpath
  - stepId: getDevice
    description: Read the matched device's full record by id via the versioned route.
    operationId: getDeviceV1
    parameters:
    - name: deviceId
      in: path
      value: $steps.findDevice.outputs.matchedDeviceId
    - name: Authorization
      in: header
      value: "Negotiate"
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      device: $response.body
  - stepId: correlateSystem
    description: Query discovered system resources filtered by the same name to correlate discovery data.
    operationId: listSystems
    parameters:
    - name: $filter
      in: query
      value: "Name eq '$inputs.deviceName'"
    - name: Authorization
      in: header
      value: "Negotiate"
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      systems: $response.body#/value
  outputs:
    matchedDeviceId: $steps.findDevice.outputs.matchedDeviceId
    device: $steps.getDevice.outputs.device
    systems: $steps.correlateSystem.outputs.systems

Work with this as data

Every workflow here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for arazzo workflows

4 MCP tools reach this
  • find_arazzoBrowse and filter every workflow in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This workflow
curl "https://apis.io/api/v1/arazzo/microsoft-endpoint-configuration-management-configmgr-device-lookup-workflow"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.