Skip to content

Commit f2a6401

Browse files
authored
Merge branch 'main' into docs-editor/linux-whatsnew-1741342825
2 parents 8d248df + 508fd94 commit f2a6401

File tree

1 file changed

+11
-13
lines changed

1 file changed

+11
-13
lines changed

defender-endpoint/migrate-devices-streamlined.md

Lines changed: 11 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -3,8 +3,8 @@ title: Migrate devices to use the streamlined onboarding method
33
description: Learn how to migrate devices to Defender for Endpoint using the streamlined connectivity method.
44
search.appverid: met150
55
ms.service: defender-endpoint
6-
ms.author: deniseb
7-
author: denisebmsft
6+
ms.author: ewalsh
7+
author: emmwalshh
88
ms.localizationpriority: medium
99
manager: deniseb
1010
audience: ITPro
@@ -13,7 +13,7 @@ ms.collection:
1313
- tier1
1414
ms.topic: how-to
1515
ms.subservice: onboard
16-
ms.date: 03/06/2025
16+
ms.date: 03/11/2025
1717
---
1818

1919
# Migrate devices to use the streamlined connectivity method
@@ -31,9 +31,9 @@ This article describes how to migrate (reonboard) devices that had been previous
3131
In most cases, full device offboarding isn't required when reonboarding. You can run the updated onboarding package and reboot your device to switch connectivity over. See the following information for details on individual operating systems.
3232

3333
> [!IMPORTANT]
34-
> Limitations and known issues:- For device migrations (reonboarding): Offboarding is not required to switch over to streamlined connectivity method. Once the updated onboarding package is run, a full device reboot is required for Windows devices and a service restart for macOS and Linux. For more information, see the details included in this article.
35-
- Windows 10 versions 1607, 1703, 1709, and 1803 do not support reonboarding. Offboard first and then onboard using the updated package. These versions also require a longer URL list.
36-
- Devices running the MMA agent are not supported and must continue using the MMA onboarding method.
34+
> Limitations and known issues:- For device migrations (reonboarding): Offboarding isn't required to switch over to streamlined connectivity method. Once the updated onboarding package is run, a full device reboot is required for Windows devices and a service restart for macOS and Linux. For more information, see the details included in this article.
35+
- Windows 10 versions 1607, 1703, 1709, and 1803 don't support reonboarding. Offboard first and then onboard using the updated package. These versions also require a longer URL list.
36+
- Devices running the MMA agent aren't supported and must continue using the MMA onboarding method.
3737

3838

3939
## Migrating devices using the streamlined method
@@ -66,7 +66,7 @@ The following table lists migration instructions for the available onboarding to
6666
### Windows 10 and 11
6767

6868
> [!IMPORTANT]
69-
> Windows 10 version 1607, 1703, 1709, and 1803 do not support reonboarding. To migrate existing devices, you will need to fully offboard and onboard using the streamlined onboarding package.
69+
> Windows 10 versions 1607, 1703, 1709, and 1803 don't support reonboarding. To migrate existing devices, you need to fully offboard and onboard using the streamlined onboarding package.
7070
7171
For general information on onboarding Windows client devices, see [Onboarding Windows Client](onboard-windows-client.md).
7272

@@ -220,7 +220,7 @@ Once a device is migrated to use the streamlined method and the device establish
220220

221221
If you move the device back to the regular method, the value is "standard".
222222

223-
For devices that haven't yet attempted reonboard, the value remains blank.
223+
For devices that have not attempted to reonboard, the value remains empty.
224224

225225
### Tracking locally on a device through Windows Event Viewer
226226

@@ -252,7 +252,7 @@ Open the Defender for Endpoint service event log using the following steps:
252252

253253
> [!NOTE]
254254
> SENSE is the internal name used to refer to the behavioral sensor that powers Microsoft Defender for Endpoint. <br>
255-
> Events recorded by the service will appear in the log. <br>
255+
> Events recorded by the service appear in the log. <br>
256256
> For more information, see [Review events and error using Event Viewer](event-error-codes.md).
257257
258258
### Run tests to confirm connectivity with Defender for Endpoint services
@@ -286,7 +286,7 @@ For Auto-IR testing labs, navigate to **Microsoft Defender XDR** \> **Evaluation
286286
```
287287

288288
> [!NOTE]
289-
> This command will only work on Windows 10, version 1703 or higher, or Windows 11.
289+
> This command only works on Windows 10, version 1703 or higher, or Windows 11.
290290
> For more information, see [Manage Microsoft Defender Antivirus with the mpcmdrun.exe commandline tool](command-line-arguments-microsoft-defender-antivirus.md).
291291
292292
#### Test Block at First Sight
@@ -319,9 +319,7 @@ For macOS and Linux, you can use the following methods:
319319

320320
### MDATP connectivity test (macOS and Linux)
321321

322-
Run `mdatp health -details features` to confirm simplified_connectivity: "enabled".
323-
324-
Run `mdatp health -details edr` to confirm `edr_partner_geo_location` is available. The value should be `GW_<geo>` where 'geo' is your tenant's geo-location.
322+
Run `mdatp health --details edr` to confirm `edr_partner_geo_location` is available. The value should be `GW_<geo>` where 'geo' is your tenant's geo-location.
325323

326324
Run mdatp connectivity test. Ensure the streamlined URL pattern is present. You should expect two for '\storage', one for '\mdav', one for '\xplat', and one for '/packages'.
327325

0 commit comments

Comments
 (0)