Wednesday, 15 July 2026

macOS custom-compliance scripts and Delete status get more precise Intune guidance

All eight changes on 15 July were Intune documentation updates; there were no new items, retirements, or Message Center announcements. The meaningful updates cluster around custom compliance guidance that now covers macOS and a clarification of what a completed device Delete action means. Other edits propagate macOS references through policy, JSON, and overview pages or repeat the Delete clarification in reporting guidance.

• Intune · Device security

  Custom compliance guidance now documents macOS discovery scripts

  The discovery-script guidance expands the documented platforms from Linux and Windows to Linux, macOS, and Windows. For macOS, it specifies a Bash script that runs in 10 minutes or less, includes a valid shebang such as #!/bin/bash, uses UTF-8 encoding without BOM, and returns exit code 0 for success and a non-zero code for failure. The procedure also adds macOS settings for logged-on credentials, signature checking, and hiding script notifications. This is a documentation expansion; the supplied evidence does not,

• Intune · Device security

  Custom-compliance scope and platform instructions are broadened to include macOS

  The main custom-compliance guidance changes its title and description from a Linux-and-Windows focus to managed devices generally, identifies macOS alongside Linux and Windows, and says Linux and macOS use a POSIX-compliant shell script. Related policy guidance now presents the discovery-script and rules-file steps for Linux and macOS, while the JSON guidance adds a macOS reference. These edits clarify the documented workflow and should not be treated as proof of a new service rollout or changed availability.

• Intune · General

  Delete action completion is clarified as server-side for MDM devices

  The updated Delete action guidance says the device is immediately hidden from the admin center and a Retire is initiated for MDM devices. In the Device actions report, Delete shows Action Status as Completed when processing is complete on the server; that status does not confirm that the client device has finished Retire. Administrators should avoid treating Completed as proof of endpoint-side retirement.

This period briefing was generated by AI from the tracked Microsoft Learn and Message Center changes.