> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/documentation/automation/connectors/microsoft-entra-id-connector/managing-devices.md).

# Managing Devices

Entra ID keeps a record of every device registered against it. These components let your flows read that inventory and clean it up — which matters, because device objects accumulate long after the hardware is gone.

#### List Devices

Returns the devices registered in Entra ID.

Besides an OData filter, this component has one input worth knowing: **Stale For (Days)**. It narrows the result to devices that have not signed in for that many days, and includes devices that never signed in at all. That single setting is what turns a device list into a cleanup workflow.

See [Working with the Connector](/documentation/automation/connectors/microsoft-entra-id-connector/working-with-the-connector.md) for how the Output Type setting shapes what leaves the component.

#### Get Device

Returns a single device object with its details.

#### Add Device, Update Device, Delete Device

Standard create, update and delete operations on device objects.

#### Disable Device

Deactivates a device so it can no longer authenticate against Entra ID.

This is the recommended step before deleting anything. A disabled device stops being useful to an attacker immediately, but the object stays available if you turn out to need it — which is not true once you delete it.

A sensible cleanup pattern is therefore two-staged: disable first, wait out a grace period, then delete.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://hub.equipme.io/documentation/automation/connectors/microsoft-entra-id-connector/managing-devices.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.