Skip to content

Commit 7f11eab

Browse files
committed
Misc changes
1 parent b7023da commit 7f11eab

File tree

1 file changed

+4
-9
lines changed

1 file changed

+4
-9
lines changed

defender-endpoint/isolation-exclusions.md

Lines changed: 4 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,7 @@ There are two steps to using isolation exclusion: defining isolation exclusion r
5858
### Prerequisites
5959

6060
* Isolation exclusion is available on Windows (minimum client version 10.8470) and macOS (minimum client version 101.240902).
61-
* Isolation exclusion must be enabled. Enabling isolation exclusion requires Security Admin permissions or above. To enable isolation exclusion, sign in to the [Microsoft Defender portal](https://security.microsoft.com) and go to **Settings** > **Endpoints** > **Advanced features** and enable **Isolation Exclusion Rules** feature.
61+
* Isolation exclusion must be enabled. Enabling isolation exclusion requires Security Admin or Manage Security settings permissions or above. To enable isolation exclusion, sign in to the [Microsoft Defender portal](https://security.microsoft.com) and go to **Settings** > **Endpoints** > **Advanced features** and enable **Isolation Exclusion Rules** feature.
6262

6363
:::image type="content" source="./media/isolation-exclusions/enable-exclusions.png" alt-text="Screenshot showing how to enable isolation exclusions." lightbox="./media/isolation-exclusions/enable-exclusions.png":::
6464

@@ -113,7 +113,8 @@ Exclusions that were applied to a specific device can be reviewed in the Action
113113

114114
### API Configuration
115115

116-
To trigger isolation with exclusions via API, set the IsolationType parameter to "Selective". See [Isolate machine API](/defender-endpoint/api/isolate-machine) for detail.
116+
> [!NOTE]
117+
> Alternatively, you can apply selective isolation via API. To do so, set the **IsolationType** parameter to *Selective*. For more information, see [Isolate machine API](/defender-endpoint/api/isolate-machine).
117118
118119
## Exclusion Logic
119120

@@ -147,13 +148,7 @@ Rule 3:
147148

148149
## Considerations and limitations
149150

150-
When a device is isolated, any new isolation exclusion rules added from the portal won't apply to the currently isolated device. Instead, newly added exclusions will only take effect for future isolation requests.
151-
152-
If an exclusion needs to be applied to a device that is already isolated, the following steps must be taken:
153-
154-
1. Unisolate the device.
155-
1. Ensure that the relevant, correctly defined exclusion rule is in place.
156-
1. Reisolate the device for the updated exclusion rule to take effect.
151+
Changes to exclusion rules only impact new isolation requests. Devices that were already isolated remain with the exclusions that were defined when they were applied. To apply updated exclusion rules to isolated devices, release those devices from isolation and then reisolate them.
157152

158153
This behavior ensures that isolation rules remain consistent throughout the duration of an active isolation session.
159154

0 commit comments

Comments
 (0)