From 64439dd8bf1ac4286fabdfabf87586e02afffc3f Mon Sep 17 00:00:00 2001 From: Dale Ribeiro Date: Tue, 7 Apr 2026 18:01:22 -0400 Subject: [PATCH] Remove MDM migration reassignment warning (#43055) Removed warning about MDM migration reassignment. --- articles/fleet-supports-macos-26-tahoe-ios-26-and-ipados-26.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/articles/fleet-supports-macos-26-tahoe-ios-26-and-ipados-26.md b/articles/fleet-supports-macos-26-tahoe-ios-26-and-ipados-26.md index 2a5f531a67..e28c1e8e86 100644 --- a/articles/fleet-supports-macos-26-tahoe-ios-26-and-ipados-26.md +++ b/articles/fleet-supports-macos-26-tahoe-ios-26-and-ipados-26.md @@ -25,8 +25,6 @@ If you're planning a macOS migration with the Tahoe workflow: - Before the first batch, export a device list with each end user's name. - Group devices into batches in a spreadsheet so stakeholders can plan around travel or other conflicts. -> If the MDM migration fails, don’t reassign the host to your old MDM in Apple Business Manager (ABM). Reassigning makes the host ineligible for migration. The host must stay actively enrolled in the MDM it’s migrating from. Once you change the ABM assignment, ABM treats the host as no longer enrolled, and the migration can’t continue. - ## Declarative device management (DDM) OS updates and profiles Apple continues to expand declarative device management (DDM) across macOS, iOS, and iPadOS. Fleet supports [OS updates](https://fleetdm.com/guides/enforce-os-updates) via DDM and [custom declaration (DDM) profiles](https://fleetdm.com/guides/custom-os-settings).