Device shows "Template Provisioning" — migrate to Blueprints

Android

When a device was provisioned using a legacy provisioning template, the Esper Console displays a Template Provisioning status instead of an applied Blueprint name. The device continues to function, but it cannot be managed through Blueprints until you complete the migration.

Why this happens

Blueprints replaced legacy provisioning templates as the primary device configuration system. Devices provisioned before or during this transition retain their original template-based management status and must be individually upgraded. The upgrade does not happen automatically — it requires a deliberate action from the Console to replace the legacy template with a blueprint.

Before you begin

Confirm the device is online and visible in Devices & Groups.
Identify the blueprint you want to apply. If you have not created one yet, go to Blueprints and create or review your blueprint before proceeding — the legacy template configuration is fully replaced during migration, so the blueprint must contain all required policies.
Confirm your Esper Agent is up to date via Esper Software Updates. Outdated agent versions may not surface the upgrade option.

Steps

Log in to the Esper Console and go to Devices & Groups.
Locate and select the device showing Template Provisioning status. Use the search bar or group filters if you have a large fleet.
On the device detail page, confirm the management status reads Template Provisioning. This confirms the device is eligible for the migration.
Click Upgrade Now. This button appears only when the device is online and the Esper Agent version supports Blueprints.
In the prompt that appears, select the blueprint you want to apply to this device from the dropdown list.
Confirm the upgrade action. The Console will begin applying the selected blueprint to the device and replacing the legacy template configuration.

Verify: Within a few minutes of completing the upgrade, the device detail page should no longer show Template Provisioning. The name of the applied blueprint should appear in the management configuration section, and the blueprint status should read Converged. If the status shows Syncing, wait up to 5 minutes and refresh the page.

If this doesn't resolve it

Upgrade Now button is not visible

Confirm the device is online. Offline devices do not display the upgrade option reliably — bring the device online and reload the device detail page.
Verify the Esper Agent version is current via Esper Software Updates. An outdated agent may suppress the button.

Blueprint fails to apply after upgrade

Open the blueprint in Blueprints and check for policy conflicts or missing required fields.
Confirm all policies in the blueprint are compatible with the device's Android version and OEM. Incompatible policies prevent the blueprint from converging.
Review the device's Activity Feed for specific error codes or policy rejection messages that can help pinpoint the conflict.

Device reverts to Template Provisioning after upgrade

If the device returns to Template Provisioning status after a completed upgrade, collect the following before contacting Esper Support:

Device serial number or Esper device ID
Name of the blueprint applied
A screenshot of the device detail page showing the reverted status
The relevant entries from the device's Activity Feed

Note: The Upgrade Now migration applies to Android devices only and moves one device at a time. For large fleets, use the Esper API to perform bulk migrations programmatically.

Still need help?

If your device remains stuck in "Template Provisioning" after migrating to Blueprints, submit a support ticket and include your device serial number, the Blueprint name you're using, and when the provisioning process started.