> For the complete documentation index, see [llms.txt](https://docs.realmjoin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmjoin.com/automation/runbooks/runbook-references/device/security/isolate-or-release-device.md).

# Isolate Or Release Device

### Description

This runbook isolates a device in Microsoft Defender for Endpoint to reduce the risk of lateral movement and data exfiltration. Optionally, it can release a previously isolated device. Provide a short reason so the action is documented in the service.

### Location

Device → Security → Isolate Or Release Device

**Full Runbook name**

rjgit-device\_security\_isolate-or-release-device

### Details

| Property         | Value                              |
| ---------------- | ---------------------------------- |
| Version          | 1.0.1                              |
| Required modules | RealmJoin.RunbookHelper (>= 0.8.9) |
| Schedulable      | no                                 |

### Permissions

#### Application permissions

* **Type**: WindowsDefenderATP
  * Machine.Read.All
    * *Looks up the Defender for Endpoint machine via /machines filtered by aadDeviceId*
  * Machine.Isolate
    * *Triggers the isolate or unisolate action on the machine*

### Parameters

#### DeviceId

The device ID of the target device.

| Property         | Value                                  |
| ---------------- | -------------------------------------- |
| Required         | true                                   |
| Default Value    |                                        |
| Type             | String                                 |
| Hidden in portal | yes (preset via runbook customization) |

#### Release

"Isolate Device" (final value: false) or "Release Device from Isolation" (final value: true) can be selected as action to perform. If set to false, the runbook will isolate the device in Defender for Endpoint. If set to true, it will release a previously isolated device from isolation in Defender for Endpoint.

| Property            | Value   |
| ------------------- | ------- |
| Required            | true    |
| Default Value       | False   |
| Type                | Boolean |
| Portal display name | Action  |

**Portal options**

| Portal option                 | Value |
| ----------------------------- | ----- |
| Isolate Device                | false |
| Release Device from Isolation | true  |

#### IsolationType

The isolation type to use when isolating the device.

| Property         | Value                                  |
| ---------------- | -------------------------------------- |
| Required         | false                                  |
| Default Value    | Full                                   |
| Type             | String                                 |
| Hidden in portal | yes (preset via runbook customization) |

#### Comment

A short reason for the (un)isolation action.

| Property            | Value                    |
| ------------------- | ------------------------ |
| Required            | true                     |
| Default Value       | Possible security risk.  |
| Type                | String                   |
| Portal display name | Reason for (Un)Isolation |

[Back to Runbook Reference overview](/automation/runbooks/runbook-references.md)


---

# 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://docs.realmjoin.com/automation/runbooks/runbook-references/device/security/isolate-or-release-device.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.