Allowed team Identifiers: team identifier UBF8T346G9 #1: KERNEL EXTENSION (KEXT) - FYI: KEXT requires macOS 10.13.2+ The UEM profiles will be used for #A: OS specific policy configurations (KEXT, SEXT, Provacy Prefences) and #B: pre-configuration of Microsoft WDAV and ATP settings (2x Custom Settings).

You can put all required payloads into a single device-based macOS profile. The use case was successfully tested end-to-end with a macOS Fusion VM. => Deploy Microsoft WDAV/ATP client on macOS 10.15 and higher - users with lower OS need to upgrade Step 1: WS1 UEM – Required Profiles Using UEM SEXT payload policies is the best practice from Microsoft System Extension are the current way to go for security app developers in order to gain required permissions and execute their background task Configuring apps utilizing System Extensions (SEXT) requires macOS 10.15+ Microsoft Defender ATP client uses macOS System Extensions + Kernel Extensions # macOS 10.15 and higher required on devices

Oliver Kluenter - Vita URL here - Contact me to discuss on LinkedIn here Good to know before # Good to know before Index & Version Info # Index Good to know before Step 1: WS1 UEM - Required Profiles Step 2: macOS Client - Tests Before App Deployment Step 3: WS1 UEM - App Configuration Step 4: macOS Client - Tests After App Deployment Helpful URLs # Version Info The tests have been done in 2020-05 time. In my customer scenario I was asked to deploy and pre-configure the Microsoft ATP client for macOS Catalina 10.15.4 with VMware Workspace ONE (WS1) UEM solution. As a result more and more enterprises want or have to use Microsoft Defender for Endpoint ATP (Advanced Threat Protection). Microsoft is good in positioning and selling their products & suites. Hands-on how to deploy Microsoft Defender for Endpoint ATP for macOS with VMware Workspace ONE UEM (AirWatch).

Defender atp mac