iOS DEP/ABM blueprint assignment: how default blueprints apply during seamless enrollment

iOS

Title: iOS Seamless (DEP) enrollment — blueprint not assigned after device appears in Esper

When an iOS device enrolls through Apple Business Manager (ABM) using Seamless (DEP) enrollment, the device may appear in the Esper Console in a Registered state with no blueprint applied, even though it was correctly assigned to Esper in ABM.

Why this happens

Esper does not apply a global default blueprint to all enrolling devices. A blueprint is only assigned to an iOS device if it is explicitly linked to the device's group before provisioning, or if a blueprint was specified when the device was pre-registered. If neither condition is met when Esper auto-discovers the device during an ABM sync, the device appears without a blueprint and will not progress past Registered until one is assigned.

Before you begin

• Confirm the device is assigned to Esper in Apple Business Manager.
• Confirm the blueprint you want to apply has a status of Active or Published — blueprints in Draft state cannot be assigned.
• Confirm you have access to the Esper Console with sufficient permissions to edit groups or upload device registrations.

Option 1: Link a blueprint to a device group (recommended)

Use this approach when your iOS devices will enroll into a known group. Any device provisioned into the group automatically receives the linked blueprint during enrollment.

1. Navigate to Devices & Groups in the Esper Console and select the group your iOS devices will enroll into.
2. Click + Link Blueprint.
3. Select the blueprint from the list and click Link Blueprint to confirm. This ensures every device that enrolls into this group receives the blueprint automatically — no per-device action needed.
4. If the device is already in a Registered state without a blueprint, trigger a manual ABM sync by navigating to Apple MDM Management → Sync after linking the blueprint. This pushes the DEP profile to devices that were discovered but not yet configured.

Verify: Provision a test iOS DEP device into the group. The device should transition from Onboarding in Progress to Active with the correct blueprint shown under the device's Blueprint tab within a few minutes of completing Setup Assistant on the device.

Option 2: Bulk register devices with blueprint assignment via CSV (recommended for large fleets)

Use this approach when you need to assign specific blueprints to specific devices across a large fleet before they enroll.

1. Prepare a CSV file containing each device's serial number and the corresponding blueprint name or ID you want assigned.
2. Navigate to Provisioning Methods in the Esper Console and select the Bulk Upload option.
3. Import your CSV file. Esper registers each device and stores the blueprint assignment so it is applied automatically when the device enrolls.
4. Trigger an ABM sync by navigating to Apple MDM Management → Sync, or wait for the automatic sync cycle (approximately every 30 minutes). This ensures Esper pushes the DEP profile to all newly registered devices promptly.

Verify: Devices should appear in Registered state immediately after upload. After the ABM sync, they should transition to Onboarding in Progress and then to Active with the correct blueprint applied once the user completes Setup Assistant on the device.

Understanding auto-discovery for devices not pre-registered

If a device is assigned to Esper in ABM but was never pre-registered in the Esper Console, Esper will auto-discover it during the next ABM sync (approximately every 30 minutes). The device will appear in Registered state with no blueprint. To move it forward, link a blueprint to its group (Option 1) or manually assign a blueprint to the individual device record, then trigger a sync from Apple MDM Management → Sync.

If this doesn't resolve it

If the device remains in Registered state and does not transition to Onboarding in Progress after an ABM sync, collect the following before contacting Esper Support:

• The device serial number and its current state in the Esper Console.
• A screenshot of the device's record in Apple Business Manager confirming it is assigned to Esper's MDM server.
• The name and status of the blueprint you are attempting to assign.
• A screenshot of the Activity Feed for the device showing recent enrollment events.

Contact Esper Support with the above information.

Still need help?

If the steps above don't resolve the issue, submit a support ticket with your device model, Android version, Esper Agent version, and a description of what you've already tried — this helps the support team investigate without a follow-up.