You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: defender-endpoint/configure-device-connectivity.md
+3-17Lines changed: 3 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ ms.collection:
14
14
ms.reviewer: pahuijbr
15
15
search.appverid: MET150
16
16
audience: ITPro
17
-
ms.date: 05/13/2024
17
+
ms.date: 06/14/2024
18
18
---
19
19
20
20
# Onboarding devices using streamlined connectivity for Microsoft Defender for Endpoint
@@ -154,7 +154,7 @@ With streamlined connectivity, IP-based solutions can be used as an alternative
154
154
- Defender for Endpoint Command and Control
155
155
156
156
> [!IMPORTANT]
157
-
> The EDR Cyber data service must be configured separately if you are using the IP method (this service is only consolidated on a URL level).You must also maintain connectivity with other required services including SmartScreen, CRL, Windows Update, and other services.<br/>
157
+
> The EDR Cyber data service (OneDsCollector) *must* be configured separately if you are using the IP method (this service is only consolidated on a URL level).You must also maintain connectivity with other required services including SmartScreen, CRL, Windows Update, and other services.<br/>
158
158
159
159
In order to stay up to date on IP ranges, it's recommended to refer to the following Azure service tags for Microsoft Defender for Endpoint services. The latest IP ranges are found in the service tag. For more information, see [Azure IP ranges](https://azureipranges.azurewebsites.net/).
160
160
@@ -163,7 +163,7 @@ In order to stay up to date on IP ranges, it's recommended to refer to the follo
| OneDsCollector | EDR Cyberdata <br/><br/> Note: The traffic under this service tag isn't limited to Defender for Endpoint and can include diagnostic data traffic for other Microsoft services. |
165
165
166
-
The following table lists the current static IP ranges. For latest list, refer to the Azure service tags.
166
+
The following table lists the current static IP ranges covered by the MicrosoftDefenderForEndpoint service tag. For latest list, refer to the Azure service tags.
167
167
168
168
169
169
|Geo|IP Ranges|
@@ -221,18 +221,4 @@ Before proceeding, confirm devices meet the [prerequisites](#prerequisites) and
221
221
222
222
For migrating devices already onboarded to Defender for Endpoint, see [Migrating devices to the streamlined connectivity](migrate-devices-streamlined.md). You must reboot your device and follow specific guidance here.
223
223
224
-
### Stage 5. Set the default onboarding package to streamlined connectivity
225
-
226
-
When you're ready to set the default onboarding package to streamlined, you can turn on the following Advanced Feature setting in the Microsoft Defender portal (**Settings > Endpoints > Advanced Features**).
This setting sets the default onboarding package to 'streamlined' for applicable operating systems. You can still use the standard onboarding package within the onboarding page but you must specifically select it in the drop-down.
231
-
232
-
For onboarding through Intune & Microsoft Defender for Cloud, you need to activate the relevant option. Devices already onboarded don't automatically reonboard; you need to create a new policy in Intune, where it's recommended to first assign the policy to a set of test devices to verify connectivity is successful, before expanding the audience. Devices in Defender for Cloud can be reonboarded using the relevant onboarding script.
233
-
234
-
> [!NOTE]
235
-
> - Only tenants created on or before May 8th, 2024 have the option to switch between standard and streamlined connectivity. Newer tenants will only support streamlined connectivity.
236
-
> - Before moving forward with this option, validate that your environment is ready and all devices meet prerequisites.
Copy file name to clipboardExpand all lines: defender-endpoint/configure-environment.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ search.appverid: met150
5
5
ms.service: defender-endpoint
6
6
ms.author: siosulli
7
7
author: siosulli
8
-
ms.reviewer: mkaminska
8
+
ms.reviewer: pahuijbr
9
9
ms.localizationpriority: medium
10
10
manager: deniseb
11
11
audience: ITPro
@@ -14,7 +14,7 @@ ms.collection:
14
14
- tier1
15
15
ms.topic: how-to
16
16
ms.subservice: onboard
17
-
ms.date: 06/06/2024
17
+
ms.date: 06/14/2024
18
18
---
19
19
20
20
# STEP 1: Configure your network environment to ensure connectivity with Defender for Endpoint service
@@ -59,6 +59,8 @@ The following destinations are required to allow Defender for Endpoint communica
59
59
|`*.blob.core.windows.net`|Port 443|Outbound|Yes|
60
60
|`*.azure-automation.net`|Port 443|Outbound|Yes|
61
61
62
+
To determine the exact destinations in use for your subscription within the domains listed above, see [Microsoft Monitoring Agent (MMA) Service URL connections](verify-connectivity.md#microsoft-monitoring-agent-mma-service-url-connections).
63
+
62
64
> [!NOTE]
63
65
> Services using MMA-based solutions are not able to leverage the new streamlined connectivity solution (consolidated URL and option to use static IPs). For Windows Server 2016 and Windows Server 2012 R2, you will need to update to the new unified solution. Instructions to onboard these operating systems with the new unified solution are at [Onboard Windows servers](configure-server-endpoints.md), or migrate already onboarded devices to the new unified solution at [Server migration scenarios in Microsoft Defender for Endpoint](server-migration.md).
Copy file name to clipboardExpand all lines: defender-endpoint/elam-on-mdav.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Early Launch Antimalware (ELAM) and Microsoft Defender Antivirus
3
3
description: How Microsoft Defender Antivirus incorporates Early Launch Antimalware (ELAM) for preventing rootkit and drivers with malware from loading before the antivirus service and drivers are loaded.
0 commit comments