Note: Blueprint Compliance is currently available as an early access feature. Contact your Esper Technical Account Manager or Support to enable it on your tenant. You may have been introduced to this feature under the name "Granular Drift". We decided to use the term "Blueprint Compliance" to better describe this feature's capabilities.
Use Blueprint Compliance when you need provable compliance, faster troubleshooting, or audit-ready evidence that your fleet policies are actually enforced.
In this article:
- How Drift Detection Works
- Drift Severity Levels
- Viewing Drift on a Device
- Configuring Blueprint Compliance in a Blueprint
- Getting started
How Drift Detection Works
Without Blueprint Compliance, Esper marks a device as "in drift" only when its blueprint ID no longer matches the one assigned in the console. A device can pass that check and still have an outdated app version, an altered Wi-Fi profile, or a silently changed policy.
Blueprint Compliance inspects the device at the field level. It compares the live state of every supported blueprint attribute against the expected value and surfaces any deviation including its severity and the exact value that changed.
Drift Severity Levels
Every drift-aware blueprint attribute is assigned a severity level. The console uses the same three levels in status indicators and filters in Devices & Groups.
The user selects these drift levels while creating or updating a blueprint.
| Severity | Description |
|---|---|
| Critical | A security- or compliance-sensitive deviation that requires immediate remediation. Examples: Kiosk app mode changed to multi-app mode |
| Major | A meaningful deviation that affects fleet behavior or device user experience. Examples: Bluetooth connectivity enabled |
| Minor | A low-impact deviation worth tracking but not urgent. Example: a cosmetic setting change. |
| Log Only | The setting is logged only. Examples: Changes not applicable to the use case or changes that device users control. |
| Coming Soon / Not available | A setting that’s not currently available for drift detection. |
Viewing Drift on a Device
The Drift Analysis tab on a device detail page shows every attribute that has drifted from the assigned blueprint, along with the severity, the current value, and the expected value.
To reach the Drift Analysis tab:
Step 1: In the Esper Console, navigate to Devices and select the device you want to inspect.
Step 2: Click on the Drift Analysis tab.
Step 3: Review the list of drifted attributes. Each entry shows the attribute name, severity level, current value on the device, and expected value from the blueprint.
Step 4: To bring the device back into compliance, click Converge on the device detail page. Converge applies the blueprint and resolves the listed deviations.
Tip: You can also trigger convergence in bulk from the Devices list. Use drift status filters to identify affected devices, then select them and choose Converge from the actions menu.
Configuring Blueprint Compliance in a Blueprint
Blueprint Compliance is enabled per blueprint, so you can turn it on for specific fleets without a fleet-wide commitment.
Step 1: In the Esper Console, navigate to Blueprint Manager and create or edit the blueprint you want to configure.
Step 2: Locate the Blueprint Compliance toggle next to the applicable setting. It is located next to the Apply setting.
Step 3: Once enabled, a Drift Detection setting appears on each supported attribute. Select the severity level — Critical, Major, Minor, or None — that a deviation from that attribute should raise.
Note: Attributes that don't yet support Blueprint Compliance display a "Coming soon" or "Not Available" indicator.
Getting Started
Step 1: Identify your priority policies. Decide which apps and settings you need the most confidence on, for example, Wi-Fi, display settings, kiosk mode, or required app versions.
Step 2: Request access. Ask your Esper Technical Account Manager or Customer Success contact to enable the Blueprint Compliance on your tenant.
Step 3: Tag severity in your blueprints. For each supported attribute, set the Drift Detection severity that matches your operational requirements.
Step 4: Monitor and act. Use drift status filters in the Devices view and the Drift Analysis tab to triage deviations. Converge devices to bring them back individually or in bulk to the blueprint-defined state.