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: articles/defender-for-cloud/integration-defender-for-endpoint.md
+35-30Lines changed: 35 additions & 30 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -95,7 +95,7 @@ Before you can enable the Microsoft Defender for Endpoint integration with Defen
95
95
96
96
#### Windows
97
97
98
-
[The MDE unified solution](/microsoft-365/security/defender-endpoint/configure-server-endpoints#new-windows-server-2012-r2-and-2016-functionality-in-the-modern-unified-solution) doesn't use or require installation of the Log Analytics agent. The unified solution is automatically deployed for Windows servers connected through Azure Arc and multicloud servers connected through the multicloud connectors. However, the unified solution isn't automatically deployed for Azure Windows 2012 R2 and 2016 servers that are protected by Defender for Servers Plan 2. You can choose to deploy the MDE unified solution to those machines.
98
+
[The MDE unified solution](/microsoft-365/security/defender-endpoint/configure-server-endpoints#new-windows-server-2012-r2-and-2016-functionality-in-the-modern-unified-solution) doesn't use or require installation of the Log Analytics agent. The unified solution is automatically deployed for Azure Windows 2012 R2 and 2016 servers, Windows servers connected through Azure Arc, and Windows multicloud servers connected through the multicloud connectors.
99
99
100
100
You'll deploy Defender for Endpoint to your Windows machines in one of two ways - depending on whether you've already deployed it to your Windows machines:
101
101
@@ -110,43 +110,45 @@ To deploy the MDE unified solution, you'll need to use the [REST API call](#enab
110
110
111
111
1. From Defender for Cloud's menu, select **Environment settings** and select the subscription with the Windows machines that you want to receive Defender for Endpoint.
112
112
113
-
1.Select **Integrations**. You'll know that the integration is enabled if the checkbox for **Allow Microsoft Defender for Endpoint to access my data** is selected as shown:
113
+
1.In the Monitoring coverage column of the Defender for Servers plan, select **Settings**.
114
114
115
-
:::image type="content" source="media/integration-defender-for-endpoint/unified-solution-enabled.png" alt-text="The integration between Microsoft Defender for Cloud and Microsoft's EDR solution, Microsoft Defender for Endpoint, is enabled." lightbox="media/integration-defender-for-endpoint/unified-solution-enabled.png":::
115
+
The status of the Endpoint protections component is **Partial**, meaning that not all parts of the component are enabled.
116
116
117
117
> [!NOTE]
118
-
> If it isn't selected, use the instructions in [Users who've never enabled the integration with Microsoft Defender for Endpoint for Windows](#users-who-never-enabled-the-integration-with-microsoft-defender-for-endpoint-for-windows).
118
+
> If the status is **Off**, use the instructions in [Users who've never enabled the integration with Microsoft Defender for Endpoint for Windows](#users-who-never-enabled-the-integration-with-microsoft-defender-for-endpoint-for-windows).
119
119
120
-
1.To deploy the MDE unified solution to your Windows Server 2012 R2 and 2016 machines:
120
+
1.Select **Fix**to see the components that are not enabled.
121
121
122
-
1. Select **Enable unified solution**.
123
-
1. Select **Save**.
124
-
1. In the confirmation prompt, verify the information and select **Enable** to continue.
125
122
126
-
:::image type="content" source="./media/integration-defender-for-endpoint/enable-unified-solution-result.png" alt-text="Confirming the use of the MDE unified solution for Windows Server 2012 R2 and 2016 machines":::
123
+
:::image type="content" source="./media/integration-defender-for-endpoint/fix-defender-for-endpoint.png" alt-text="Screenshot of Fix button that enables Microsoft Defender for Endpoint support.":::
127
124
128
-
Microsoft Defender for Cloud will:
125
+
1. To enable the Unified solution for Windows Server 2012 R2 and 2016 machines, select **Enable**.
129
126
130
-
- Stop the existing MDE process in the Log Analytics agent that collects data for Defender for Servers.
131
-
- Install the MDE unified solution for all existing and new Windows Server 2012 R2 and 2016 machines.
132
-
- Remove the **Enable unified solution** from the Integrations options.
127
+
:::image type="content" source="./media/integration-defender-for-endpoint/enable-defender-for-endpoint-unified.png" alt-text="Screenshot of enabling the use of the MDE unified solution for Windows Server 2012 R2 and 2016 machines.":::
133
128
134
-
Microsoft Defender for Cloud will automatically onboard your machines to Microsoft Defender for Endpoint. Onboarding might take up to 12 hours. For new machines created after the integration has been enabled, onboarding takes up to an hour.
129
+
1. To save the changes, select **Save** at the top of the page and then select **Continue** in the Settings and monitoring page.
135
130
136
-
> [!NOTE]
137
-
> If you choose not to deploy the MDE unified solution to your Windows 2012 R2 and 2016 servers in Defender for Servers Plan 2 and then downgrade Defender for Servers to Plan 1, the MDE unified solution is not deployed to those servers so that your existing deployment is not changed without your explicit consent.
131
+
Microsoft Defender for Cloud will:
132
+
133
+
- Stop the existing MDE process in the Log Analytics agent that collects data for Defender for Servers.
134
+
- Install the MDE unified solution for all existing and new Windows Server 2012 R2 and 2016 machines.
135
+
136
+
Microsoft Defender for Cloud will automatically onboard your machines to Microsoft Defender for Endpoint. Onboarding might take up to 12 hours. For new machines created after the integration has been enabled, onboarding takes up to an hour.
137
+
138
+
> [!NOTE]
139
+
> If you choose not to deploy the MDE unified solution to your Windows 2012 R2 and 2016 servers in Defender for Servers Plan 2 and then downgrade Defender for Servers to Plan 1, the MDE unified solution is not deployed to those servers so that your existing deployment is not changed without your explicit consent.
138
140
139
141
##### Users who never enabled the integration with Microsoft Defender for Endpoint for Windows
140
142
141
-
If you've never enabled the integration for Windows, the **Allow Microsoft Defender for Endpoint to access my data** option will enable Defender for Cloud to deploy Defender for Endpoint to *both* your Windows and Linux machines.
143
+
If you've never enabled the integration for Windows, Endpoint protection enables Defender for Cloud to deploy Defender for Endpoint to *both* your Windows and Linux machines.
142
144
143
145
To deploy the MDE unified solution, you'll need to use the [REST API call](#enable-the-mde-unified-solution-at-scale) or the Azure portal:
144
146
145
147
1. From Defender for Cloud's menu, select **Environment settings** and select the subscription with the machines that you want to receive Defender for Endpoint.
146
148
147
-
1.Select **Integrations**.
149
+
1.In the status of the Endpoint protection component, select **On** to enable the integration with Microsoft Defender for Endpoint.
148
150
149
-
1. Select **Allow Microsoft Defender for Endpoint to access my data**, and select **Save**.
151
+
:::image type="content" source="media/integration-defender-for-endpoint/enable-defender-for-endpoint.png" alt-text="Screenshot of Status toggle that enables Microsoft Defender for Endpoint." lightbox="media/integration-defender-for-endpoint/enable-defender-for-endpoint.png":::
150
152
151
153
The MDE agent unified solution is deployed to all of the machines in the selected subscription.
152
154
@@ -163,20 +165,23 @@ If you've already enabled the integration with **Defender for Endpoint for Windo
163
165
164
166
1. From Defender for Cloud's menu, select **Environment settings** and select the subscription with the Linux machines that you want to receive Defender for Endpoint.
165
167
166
-
1.Select **Integrations**. You'll know that the integration is enabled, if the checkbox for **Allow Microsoft Defender for Endpoint to access my data** is selected as shown:
168
+
1.In the Monitoring coverage column of the Defender for Server plan, select **Settings**.
167
169
168
-
:::image type="content" source="./media/integration-defender-for-endpoint/integration-enabled.png" alt-text="The integration between Microsoft Defender for Cloud and Microsoft's EDR solution, Microsoft Defender for Endpoint is enabled":::
170
+
The status of the Endpoint protections component is **Partial**, meaning that not all parts of the component are enabled.
169
171
170
172
> [!NOTE]
171
-
> If it isn't selected, use the instructions in [New users who've never enabled the integration with Microsoft Defender for Endpoint for Windows](#new-users-who-never-enabled-the-integration-with-microsoft-defender-for-endpoint-for-windows).
173
+
> If the status is **Off**isn't selected, use the instructions in [Users who've never enabled the integration with Microsoft Defender for Endpoint for Windows](#users-who-never-enabled-the-integration-with-microsoft-defender-for-endpoint-for-windows).
172
174
173
-
1.To add your Linux machines to your integration:
175
+
1.Select **Fix** to see the components that are not enabled.
174
176
175
-
1. Select **Enable for Linux machines**.
176
-
1. Select **Save**.
177
-
1. In the confirmation prompt, verify the information and select **Enable** to continue.
178
177
179
-
:::image type="content" source="./media/integration-defender-for-endpoint/enable-for-linux-result.png" alt-text="Confirming the integration between Defender for Cloud and Microsoft's EDR solution, Microsoft Defender for Endpoint for Linux":::
178
+
:::image type="content" source="./media/integration-defender-for-endpoint/fix-defender-for-endpoint.png" alt-text="Screenshot of Fix button that enables Microsoft Defender for Endpoint support.":::
179
+
180
+
1. To enable deployment to Linux machines, select **Enable**.
181
+
182
+
:::image type="content" source="./media/integration-defender-for-endpoint/enable-defender-for-endpoint-linux.png" alt-text="Screenshot of enabling the integration between Defender for Cloud and Microsoft's EDR solution, Microsoft Defender for Endpoint for Linux.":::
183
+
184
+
1. To save the changes, select **Save** at the top of the page and then select **Continue** in the Settings and monitoring page.
180
185
181
186
Microsoft Defender for Cloud will:
182
187
@@ -204,13 +209,13 @@ If you've already enabled the integration with **Defender for Endpoint for Windo
204
209
205
210
##### New users who never enabled the integration with Microsoft Defender for Endpoint for Windows
206
211
207
-
If you've never enabled the integration for Windows, the **Allow Microsoft Defender for Endpoint to access my data** option will enable Defender for Cloud to deploy Defender for Endpoint to *both* your Windows and Linux machines.
212
+
If you've never enabled the integration for Windows, endpoint protection enables Defender for Cloud to deploy Defender for Endpoint to *both* your Windows and Linux machines.
208
213
209
214
1. From Defender for Cloud's menu, select **Environment settings** and select the subscription with the Linux machines that you want to receive Defender for Endpoint.
210
215
211
-
1.Select **Integrations**.
216
+
1.In the status of the Endpoint protection component, select **On** to enable the integration with Microsoft Defender for Endpoint.
212
217
213
-
1. Select **Allow Microsoft Defender for Endpoint to access my data**, and select **Save**.
218
+
:::image type="content" source="media/integration-defender-for-endpoint/enable-defender-for-endpoint.png" alt-text="Screenshot of Status toggle that enables Microsoft Defender for Endpoint." lightbox="media/integration-defender-for-endpoint/enable-defender-for-endpoint.png":::
0 commit comments