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
-[RHEL and variants (CentOS, Fedora, Oracle Linux, Amazon Linux 2, Rocky and Alma)](#rhel-and-variants-centos-fedora-oracle-linux-amazon-linux-2-rocky-and-alma)
45
+
-[RHEL and variants (CentOS, Fedora, Oracle Linux, Amazon Linux 2, Rocky, and Alma)](#rhel-and-variants-centos-fedora-oracle-linux-amazon-linux-2-rocky-and-alma)
46
46
-[SLES and variants](#sles-and-variants)
47
47
-[Ubuntu and Debian systems](#ubuntu-and-debian-systems)
48
48
-[Mariner](#mariner-1)
@@ -58,9 +58,9 @@ Before you get started, see [Microsoft Defender for Endpoint on Linux](microsoft
58
58
59
59
## Configure the Linux software repository
60
60
61
-
Defender for Endpoint on Linux can be deployed from one of the following channels (denoted below as *[channel]*): *insiders-fast*, *insiders-slow*, or *prod*. Each of these channels corresponds to a Linux software repository. The instructions in this article describe configuring your device to use one of these repositories.
61
+
Defender for Endpoint on Linux can be deployed from one of the following channels (denoted as *[channel]*): *insiders-fast*, *insiders-slow*, or `prod`. Each of these channels corresponds to a Linux software repository. The instructions in this article describe configuring your device to use one of these repositories.
62
62
63
-
The choice of the channel determines the type and frequency of updates that are offered to your device. Devices in *insiders-fast* are the first ones to receive updates and new features, followed later by *insiders-slow* and lastly by *prod*.
63
+
The choice of the channel determines the type and frequency of updates that are offered to your device. Devices in *insiders-fast* are the first ones to receive updates and new features, followed later by *insiders-slow* and lastly by `prod`.
64
64
65
65
In order to preview new features and provide early feedback, it's recommended that you configure some devices in your enterprise to use either *insiders-fast* or *insiders-slow*.
66
66
@@ -91,7 +91,7 @@ Options:
91
91
92
92
Read more [here](https://github.com/microsoft/mdatp-xplat/tree/master/linux/installation).
93
93
94
-
### RHEL and variants (CentOS, Fedora, Oracle Linux, Amazon Linux 2, Rocky and Alma)
94
+
### RHEL and variants (CentOS, Fedora, Oracle Linux, Amazon Linux 2, Rocky, and Alma)
95
95
96
96
- Install `yum-utils` if it isn't installed yet:
97
97
@@ -128,7 +128,7 @@ Read more [here](https://github.com/microsoft/mdatp-xplat/tree/master/linux/inst
128
128
> [!TIP]
129
129
> Use hostnamectl command to identify system related information including release *[version]*.
130
130
131
-
For example, if you're running CentOS 7 and want to deploy Defender for Endpoint on Linux from the *prod* channel:
131
+
For example, if you're running CentOS 7 and want to deploy Defender for Endpoint on Linux from the `prod` channel:
@@ -493,7 +493,7 @@ Download the onboarding package from Microsoft Defender portal.
493
493
494
494
- Verify that the onboarded Linux server appears in Microsoft Defender XDR. If this is the first onboarding of the machine, it can take up to 20 minutes until it appears.
495
495
496
-
- Download and extract the [script file](https://aka.ms/LinuxDIY) to an onboarded Linux server and run the following command: `./mde_linux_edr_diy.sh`
496
+
- Download and extract the [script file](https://aka.ms/MDE-Linux-EDR-DIY) to an onboarded Linux server and run the following command: `./mde_linux_edr_diy.sh`
497
497
498
498
- After a few minutes, a detection should be raised in Microsoft Defender XDR.
499
499
@@ -503,16 +503,16 @@ Download the onboarding package from Microsoft Defender portal.
503
503
504
504
The following external package dependencies exist for the mdatp package:
Copy file name to clipboardExpand all lines: defender-endpoint/mac-install-with-intune.md
+16-33Lines changed: 16 additions & 33 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.topic: conceptual
15
15
ms.subservice: macos
16
16
search.appverid: met150
17
-
ms.date: 05/20/2024
17
+
ms.date: 08/01/2024
18
18
---
19
19
20
20
# Deploy Microsoft Defender for Endpoint on macOS with Microsoft Intune
@@ -65,7 +65,7 @@ In the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2
65
65
66
66
1. Under **Configuration profiles**, select **Create Profile**.
67
67
68
-
This profile is needed for Big Sur (11) or later. It is ignored on older versions of macOS, because they use the kernel extension.
68
+
This profile is needed for Big Sur (11) or later. It's ignored on older versions of macOS, because they use the kernel extension.
69
69
70
70
1. On the **Policies** tab, select **Create** > **New Policy**.
71
71
@@ -100,7 +100,7 @@ As part of the Endpoint Detection and Response capabilities, Microsoft Defender
100
100
101
101
Download [netfilter.mobileconfig](https://raw.githubusercontent.com/microsoft/mdatp-xplat/master/macos/mobileconfig/profiles/netfilter.mobileconfig) from [GitHub repository](https://github.com/microsoft/mdatp-xplat/tree/master/macos/mobileconfig/profiles).
102
102
103
-
To configure network filter:
103
+
To configure your network filter:
104
104
105
105
1. Under **Configuration profiles**, select **Create Profile**.
106
106
@@ -160,7 +160,7 @@ To configure Full Disk Access:
160
160
1. Review the configuration profile. Select **Create**.
161
161
162
162
> [!NOTE]
163
-
> Full Disk Access granted through Apple MDM Configuration Profile is not reflected in System Settings => Privacy & Security => Full Disk Access.
163
+
> Full Disk Access granted through Apple MDM Configuration Profile is not reflected in **System Settings** > **Privacy & Security** > **Full Disk Access**.
> macOS 14 (Sonoma) contains new privacy enhancements. Beginning with this version, by default, applications cannot access Bluetooth without explicit consent. Microsoft Defender for Endpoint uses it if you configure Bluetooth policies for Device Control.
270
+
> [!CAUTION]
271
+
> macOS 14 (Sonoma) contains new privacy enhancements. Beginning with this version, by default, applications cannot access Bluetooth without explicit consent. Microsoft Defender for Endpoint uses it if you configure Bluetooth policies for Device Control.
272
272
273
-
Download [bluetooth.mobileconfig](https://github.com/microsoft/mdatp-xplat/blob/master/macos/mobileconfig/profiles/bluetooth.mobileconfig) from [GitHub repository](https://github.com/microsoft/mdatp-xplat/tree/master/macos/mobileconfig/profiles) and use the same workflow as for the Accessibility settings above to enable Bluetooth access.
273
+
Download [bluetooth.mobileconfig](https://github.com/microsoft/mdatp-xplat/blob/master/macos/mobileconfig/profiles/bluetooth.mobileconfig) from [GitHub repository](https://github.com/microsoft/mdatp-xplat/tree/master/macos/mobileconfig/profiles) and use the same workflow as for the Accessibility settings mentioned earlier in this article to enable Bluetooth access.
274
274
275
275
> [!NOTE]
276
276
> Bluetooth granted through Apple MDM Configuration Profile is not reflected in System Settings => Privacy & Security => Bluetooth.
@@ -288,7 +288,7 @@ For more information, see [Deploy updates for Microsoft Defender for Endpoint on
288
288
Download [AutoUpdate2.mobileconfig](https://github.com/microsoft/mdatp-xplat/blob/master/macos/settings/microsoft_auto_update/com.microsoft.autoupdate2.mobileconfig) from [GitHub repository](https://github.com/microsoft/mdatp-xplat/tree/master/macos/settings/microsoft_auto_update).
289
289
290
290
> [!NOTE]
291
-
> The sample AutoUpdate2.mobileconfig from the GitHub repository has it set to Current Channel (Production).
291
+
> The sample `AutoUpdate2.mobileconfig` from the GitHub repository has it set to Current Channel (Production).
292
292
293
293
1. Under **Configuration profiles**, select **Create Profile**.
### Step 9: Microsoft Defender for Endpoint configuration settings
318
318
319
-
In this step, we go over *Preferences* that enables you to configure anti-malware and EDR policies using Microsoft Defender XDR portal ([https://security.microsoft.com](https://security.microsoft.com)) **or** Microsoft Intune ([https://intune.microsoft.com](https://intune.microsoft.com)).
319
+
In this step, we go over *Preferences* that enables you to configure anti-malware and EDR policies using Microsoft Intune ([https://intune.microsoft.com](https://intune.microsoft.com)).
320
320
321
-
#### 9a. Set policies using Microsoft Defender portal
322
-
323
-
1. Go through [Configure Microsoft Defender for Endpoint in Intune](/mem/intune/protect/advanced-threat-protection-configure) before setting the security policies using Microsoft Defender for Endpoint Security Settings Management.
324
-
325
-
2. In the [Microsoft Defender portal](https://sip.security.microsoft.com/homepage?tid=72f988bf-86f1-41af-91ab-2d7cd011db47), go to **Configuration management** > **Endpoint security policies** > **Mac policies** > **Create new policy**.
326
-
327
-
3. Under **Select Platform**, select **macOS**.
328
-
329
-
4. Under **Select Template**, choose a template and select **Create Policy**.
330
-
331
-
5. Specify a name and description for the policy, and then select **Next**.
332
-
333
-
6. On the **Assignments** tab, assign the profile to a group where the macOS devices and/or users are located, or **All Users** and **All devices**.
334
-
335
-
For more information about managing security settings, see:
336
-
337
-
-[Manage Microsoft Defender for Endpoint on devices with Microsoft Intune](/mem/intune/protect/mde-security-integration?pivots=mdssc-ga)
338
-
-[Manage security settings for Windows, macOS, and Linux natively in Defender for Endpoint](https://techcommunity.microsoft.com/t5/microsoft-defender-for-endpoint/manage-security-settings-for-windows-macos-and-linux-natively-in/ba-p/3870617)
321
+
> [!NOTE]
322
+
> If managed via Intune, it will not allow for the device to register via the Microsoft Defender for Endpoint Security Settings Management ([Microsoft Defender XDR portal (https://security.microsoft.com)](Microsoft Defender XDR portal (https://security.microsoft.com) or)).
339
323
340
324
> [!IMPORTANT]
341
-
> The policies set via Intune will take precedence over the Microsoft Defender for Endpoint Security Settings Management.
342
-
343
-
#### Set policies using Microsoft Intune
325
+
> Important
326
+
> Only the policies set via Intune will take effect, and the Microsoft Defender for Endpoint Security Settings Management will not be used.
327
+
#### **Set policies using Microsoft Intune**
344
328
345
329
You can manage the security settings for Microsoft Defender for Endpoint on macOS under **Setting Preferences** in Microsoft Intune.
346
330
@@ -372,9 +356,8 @@ In the [Microsoft Defender portal](https://sip.security.microsoft.com/homepage?t
372
356
373
357
1. Review the policy in **Review+Create** and select **Save**.
374
358
375
-
376
359
> [!TIP]
377
-
> You can also configure network protection by appending the information from [**Network protection to help prevent macOS connections to bad sites**](network-protection-macos.md) to the .mobileconig from step 8.
360
+
> You can also configure network protection by appending the information from [**Network protection to help prevent macOS connections to bad sites**](network-protection-macos.md) to the `.mobileconfig` from step 8.
378
361
379
362
### Step 11: Device Control for Microsoft Defender for Endpoint on macOS
380
363
@@ -463,7 +446,7 @@ You can visit **Apps** > **By platform** > **macOS** to see it on the list of al
463
446
For more information, see [Add Microsoft Defender for Endpoint to macOS devices using Microsoft Intune](/mem/intune/apps/apps-advanced-threat-protection-macos).
464
447
465
448
> [!IMPORTANT]
466
-
> You should create and deploy the configuration profiles in the above order (step 1-13) for a successful system configuration.
449
+
> You should create and deploy the configuration profiles in the order specified (steps 1-13) for a successful system configuration.
0 commit comments