Backup and restore scenarios for iOS/iPadOS

Applies to iOS/iPadOS

This article describes the backup and restore scenarios for Intune-managed iOS/iPadOS devices, and includes best practices for how to maintain the device's enrollment status when, for example:

• A device is factory reset and needs to be restored from a previous backup.
• A user receives a new device and wants to migrate the data from the old device.
• A device is migrating to Intune from another EMM vendor.

The backup and restore scenarios are specific to enrollments via Apple Automated Device Enrollment. For information about how to back up, restore, and transfer data for an Apple device, see the following Apple Support documentation:

• How to back up your iPhone, iPad, and iPod touch
• Restore your iPhone, iPad, or iPod touch from a backup
• Use iCloud to transfer data from your previous iOS device to your new iPhone, iPad, or iPod touch

Note

Device-to-device migration, an option that appears on the Quick Start screen after resetting an iOS device, isn't supported with Apple Business Manager. Quick Start occurs before a Wi-Fi connection is established on the device and before the Apple Business Manager profile downloads. As a result, the Quick Start screen can't be hidden via Apple Business Manager.

Back up Microsoft Authenticator

If you're using the Microsoft Authenticator app, it's also important to back up your credentials and accounts. For more information, see Back up and recover account credentials in the Authenticator app.

Restoring a backup to an iOS/iPadOS device

Restoring a backup is only possible during Apple Setup Assistant. This backup is a one-time opportunity. Consider the information in this section to help you prepare and support device users restoring their content from an iCloud or iTunes backup.

Restore options and workflow

The workflow for the restore process is different depending on where you restore the backup. Your options are:

• Restore backup on different device than the one on which the backup was performed: After the backup is successfully restored, Setup Assistant continues with the enrollment process starting on the Remote management screen. The result is that you enroll in the MDM vendor and maintain the content that's restored from your iCloud account.
• Restore backup on same device the backup was performed: After the backup is successfully restored, Setup Assistant ends and you land on the device's home screen. The result is that you don't go through the subsequent enrollment steps. Your device keeps the management state and management profile that you had at the time the backup was done. This result is typically the desired outcome, unless you're migrating to a different EMM vendor.

Note

Linking an Apple ID in device settings post-setup isn't the same as restoring a backup. While linking the Apple ID does link files and documents, it doesn't typically restore any user data and preferences such as wallpaper, widgets, installed apps, and user preferences. Only a limited set of data, such as iCloud Photo Library and messages, can be restored.

Reset options

There are two ways you can reset a device. Each reset method has a different effect on the device's enrollment state post-restoration:

• If you perform a local reset of the device, the device enrolls after you restore the backup, and shouldn't require any intervention. This behavior is typically the desired outcome.
• If you perform a remote wipe in the Intune admin center, the device unenrolls from Intune before it's wiped. After you restore the backup, the device needs to be re-enrolled in the Company Portal app.

Creating a backup

To avoid enrollment issues, tell device users that they shouldn't back up their device when it's enrolled. It's important to avoid backup and restore activities that could impact the management profile and related certificates.

Time since last backup

Consider the amount of time elapsed since the last backup, and how the device would be impacted if restored to that time. These scenarios might be less common, but they are worth being aware of, especially if the backup being restored isn't recent:

• Has the corresponding device record in Intune been deleted, either by accident or intentionally for retirement or clean-up?
• Has the Microsoft Entra ID record been deleted?
• Has the management certificate been deleted? These certificates are valid for a year for iOS/iPadOS and need to be renewed annually.
• Is the management certificate being restored still valid? Was the management certificate renewed after the backup was done?

Locked management profile

If the prior EMM vendor locked the management profile on the device, the device user can't remove the management profile. To facilitate a migration in this scenario, you can:

• Retire the device from the prior EMM vendor before the user backs up the device.
• Alternatively, if you can't ensure that the device was unenrolled when the backup was created, consider hiding the Setup Assistant restore screen. The setting that lets you hide the screen can be found in the Microsoft Intune admin center in your iOS/iPadOS enrollment profile. For more information, see step 21 in Create an Apple enrollment profile.

Migrating to Intune from another EMM vendor

Typically the MDM enrollment state at the time of backup isn't of any special significance. However, in a migration scenario where you're moving from one MDM vendor to another, it's important to be aware of the device's MDM enrollment state so as not to restore an old management profile. The following steps outline the sequence of events that lead to this scenario and the failed outcome:

1. The device user creates a backup while enrolled in MDM vendor A.
2. The device user restores the backup on the same device. The backup is restored successfully with no apparent errors.
3. The device user attempts to manually enroll the device in Intune via the Intune Company Portal app. However, the backup restored the old management profile from MDM vendor A, so the device can't enroll in Intune.

Company Portal notifies the user of this conflict by explaining that the new MDM payload doesn't match the old payload. To remediate this error, the device user must remove the management profile belonging to MDM vendor A, and then re-enroll in Company Portal. You can expect the same behavior and outcome when migrating from one Intune tenant to another Intune tenant.

Migrating without wiping the device

You can migrate devices to another MDM vendor without wiping the device. If the device migrates from one MDM vendor to another without a device wipe, via a tool such as EBF OnBoarder, there should be no negative impact to the device, as it's never restored. Instead, this option unenrolls and removes the device from the previous MDM vendor. Then it removes the management profile from the device. After the management profile is removed, the device user can manually enroll the device via the Company Portal app. The user's iCloud account remains and no backup is restored, as Setup Assistance isn't involved in this scenario.

Other details to consider when migrating a device without wiping it:

• If the device was supervised under the current EMM vendor, it remains supervised.
• 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 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?

If you want to designate devices as corporate-owned devices, you have two options:

• Add corporate device identifiers. This option is the easier of the two and avoids scripting, provided you can obtain a list of serial numbers from your current EMM vendor. The list must be imported prior to enrolling the devices in Intune.
• Use a script to modify the OwnershipType from personal to corporate-owned. For a sample script that uses an exported list (.csv) of device serial numbers as input, see Set ownership.

Note

If you use enrollment restrictions to block personal devices from enrolling in Intune, you will need to add the devices using corporate device identifiers prior to enrollment.

Next steps

Learn more about using Microsoft Intune and Apple Automated Device Enrollment.