Update MDM commands documentation with usage details (#49657)

Added note about MDM command limitations and usage of fleetctl. --------- Co-authored-by: Noah Talerman <47070608+noahtalerman@users.noreply.github.com> Co-authored-by: Mike Thomas <78363703+mike-j-thomas@users.noreply.github.com>
2026-07-29 11:23:29 -06:00
parent 43b8a27950
commit daed574428
2 changed files with 3 additions and 0 deletions
@@ -91,6 +91,9 @@ A `.plist` with the `CommandUUID` key / value added will look something like thi
 </plist>
 ```

+> If you're trying to remove macOS configuration profiles via the `RemoveProfile` command, note that this endpoint (and `fleetctl run mdm command`) sends commands on the device channel only. User-scoped profiles installed via the user channel cannot be removed this way. In Fleet, in **host details > OS settings** profiles will have an icon indicator <img src="../website/assets/images/articles/user-scope-icon-16x16@2x.png" alt="user-scope-icon" style="display:inline; margin:0; height:16px; width:16px;"> when it is user-scoped.
+
+
 ### Step 2: Choose a target host

 Run the `fleetctl get hosts --mdm` command to get a list of hosts that are enrolled in Fleet and have MDM enabled. This may not be practical in Fleet environments with a large number of hosts without using command line tools to parse the output, e.g.,