From 883efbf33b75975c3556aa3470014267603dbec4 Mon Sep 17 00:00:00 2001 From: Steven Palmesano <3100993+spalmesano0@users.noreply.github.com> Date: Tue, 14 Jul 2026 11:58:41 -0500 Subject: [PATCH] Remove info about DDM not working during Setup Assistant (#46017) Found while testing for #45411. --- .../architecture/mdm/apple-declarative-device-management.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/docs/Contributing/architecture/mdm/apple-declarative-device-management.md b/docs/Contributing/architecture/mdm/apple-declarative-device-management.md index 9613cfbbb6..987e316525 100644 --- a/docs/Contributing/architecture/mdm/apple-declarative-device-management.md +++ b/docs/Contributing/architecture/mdm/apple-declarative-device-management.md @@ -144,9 +144,6 @@ The profiles names must be unique across all platforms and profile types for a g * DDM profiles [must be a configuration type](https://github.com/fleetdm/fleet/blob/bd027dc4210b113983c3133251b51754e7d24c6f/server/fleet/apple_mdm.go#L682-L684). * DDM profiles can be delivered to either the device channel or the user channel (macOS only). A declaration selects its channel via a Fleet-specific top-level `PayloadScope` key (`"System"` — the default — or `"User"`); Fleet parses it at upload and records the channel in the `scope` column. The key is left in the stored `raw_json` (so the declaration round-trips and its content hash still reflects scope changes) and is stripped only when the declaration is served to a device, so the JSON the device receives stays valid Apple DDM. -## Special Cases - -- **Setup assistant**: As of Fleet v4.70.0, DDM profiles are ignored during the setup assistant phase of a macOS device. This is because Apple does not currently support the DDM protocol in this phase, it always returns a "NotNow" response to the `DeclarativeManagement` MDM command, so Fleet cannot wait for DDM profiles to be delivered before releasing the device so we ignore them and wait for after the device is configured to send them. ## Related Resources