> For the complete documentation index, see [llms.txt](https://docs.patchmypc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.patchmypc.com/patch-my-pc-publisher/customizations-right-click-options/manage-esp-profiles.md).

# Manage ESP Profiles

*Applies to: Patch My PC Publisher V2.x*\
*Available at level: All Custom Products, All Products, Vendor, Product*\
*Available on tab: Intune Apps*

## Overview

The **Manage ESP Profiles** option allows you to associate Intune applications created by the Publisher with one or more Enrollment Status Page (ESP) profiles.

<figure><img src="/files/b0PB0LA2a5LQj9BTOtL7" alt="Manage ESP Profiles" width="520"><figcaption></figcaption></figure>

This configuration controls which applications are tracked as blocking apps during Windows Autopilot enrollment.

Only classic Enrollment Status Page (ESP) profiles are supported by this feature. It does not apply to the newer Autopilot device preparation policies found in the modern Windows Autopilot configuration experience.

The example below highlights the difference in the Intune admin center between classic **Enrollment Status Page** profiles, which are supported, and **Device preparation policies**, which are not supported for ESP association by the Publisher.

<figure><img src="/files/MRs6m3SWrAuRGwPE9dhD" alt="Classic Enrollment Status Page versus Autopilot device preparation policies" width="563"><figcaption></figcaption></figure>

## Configuration

The ESP profile association is applied during the next Publisher synchronization.

If a new version of the application is published, the Publisher automatically removes the previous version it created from the ESP profile(s) and adds the newly published version instead. This ensures Autopilot always tracks the most recent version of an application published.

{% hint style="warning" %}
**Important**

Associating an app with an ESP profile does not install the app by itself. The application must also have a Required Intune assignment targeting the device or user for it to be installed during Autopilot.
{% endhint %}

The available ESP profiles are retrieved from your Intune tenant. To appear in the list, an ESP profile must have **Show app and profile configuration progress** set to **Yes**.

<figure><img src="/files/xuZa4FKP19jGGH5Plhgt" alt="Show app and profile configuration progress" width="563"><figcaption></figcaption></figure>

Use the Select ESPs window to associate an Intune application with one or more classic Enrollment Status Page profiles.

<figure><img src="/files/Qi9JKZmU9M9jj5LXcyk2" alt="Select ESP Profiles" width="465"><figcaption></figcaption></figure>

To configure ESP profiles for an application:

1. Right-Click the **Manage ESP Profiles** option for the product, vendor, or product group where you want the setting applied.
2. The Select ESPs window opens and displays all eligible classic ESP profiles from your Intune tenant.
3. Use the Filter items field to quickly locate the required ESP profile.
4. Select one or more ESP profiles by checking the box next to each profile.
5. Select **OK** to save the configuration.

Products selected will added to the ESP profile as a Blocking app when the Intune application is published.

<figure><img src="/files/jYvYrXGCVmsrrwvXCev4" alt="Block device use until required apps are installed if they are assigned to the user/device" width="563"><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.patchmypc.com/patch-my-pc-publisher/customizations-right-click-options/manage-esp-profiles.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
