From b6cd93d489b323fa1f81168d9e08f28d91f7e6a6 Mon Sep 17 00:00:00 2001 From: Kinshuk-s Date: Sat, 17 Aug 2024 00:50:56 +0530 Subject: [PATCH 1/2] Update backup-restore-ios.md Requesting to add a note calling out the possible management state issues customers can face if they restore backup from an Unmanaged device once the ADE enrollment is complete. --- memdocs/intune/enrollment/backup-restore-ios.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/memdocs/intune/enrollment/backup-restore-ios.md b/memdocs/intune/enrollment/backup-restore-ios.md index 2f9dff1fb95..2510d0133f5 100644 --- a/memdocs/intune/enrollment/backup-restore-ios.md +++ b/memdocs/intune/enrollment/backup-restore-ios.md @@ -99,6 +99,9 @@ Other details to consider when migrating a device without wiping it: * The Apple Activation Lock bypass code is only generated when the device is erased, so Activation Lock can't be managed on these devices once they migrate MDM vendors. * The new Intune management profile can't be *locked*, meaning the user must be able to remove the management profile via device settings. +>[!NOTE] +>After an ADE device completes the setup assistant phase if a backup is then restored on the device which was taken from an unmanaged device it can affect the current management state of the device once the backup restore is complete. + ### Corporate identifiers Devices enroll into Intune as personal devices, rather than corporate-owned devices. This condition has an impact on the device details, such as app inventory and phone number, gathered from the device. For more information that you can share with end users about what's visible on enrolled devices, see [What can my organization see on my enrolled device?](../user-help/what-info-can-your-company-see-when-you-enroll-your-device-in-intune.md) From 184e93802ac5555d9bce05c14cec3f4e0cf4618c Mon Sep 17 00:00:00 2001 From: Laura Newsad Date: Wed, 28 Aug 2024 15:34:03 -0400 Subject: [PATCH 2/2] Update backup-restore-ios.md Style/product team edits --- memdocs/intune/enrollment/backup-restore-ios.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/memdocs/intune/enrollment/backup-restore-ios.md b/memdocs/intune/enrollment/backup-restore-ios.md index 2510d0133f5..636ddfe631c 100644 --- a/memdocs/intune/enrollment/backup-restore-ios.md +++ b/memdocs/intune/enrollment/backup-restore-ios.md @@ -8,7 +8,7 @@ keywords: author: Lenewsad ms.author: lanewsad manager: dougeby -ms.date: 01/12/2024 +ms.date: 08/28/2024 ms.topic: how-to ms.service: microsoft-intune ms.subservice: enrollment @@ -100,7 +100,7 @@ Other details to consider when migrating a device without wiping it: * The new Intune management profile can't be *locked*, meaning the user must be able to remove the management profile via device settings. >[!NOTE] ->After an ADE device completes the setup assistant phase if a backup is then restored on the device which was taken from an unmanaged device it can affect the current management state of the device once the backup restore is complete. +> After a device completes the Setup Assistant phase of the automated device enrollment process, we don't recommend restoring a backup on the device if the backup is from a time when the device was unmanaged. Doing so could affect the current management state of the device. ### Corporate identifiers Devices enroll into Intune as personal devices, rather than corporate-owned devices. This condition has an impact on the device details, such as app inventory and phone number, gathered from the device. For more information that you can share with end users about what's visible on enrolled devices, see [What can my organization see on my enrolled device?](../user-help/what-info-can-your-company-see-when-you-enroll-your-device-in-intune.md)