> 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-cloud/technical-references/intune-reference/check-esp-profiles-in-intune.md). # Check ESP Profiles in Intune *Applies to: Microsoft Intune* If a Patch My PC (PMPC) Cloud deployment has been configured to use [ESP Profiles](/patch-my-pc-cloud/deployments/deploy-app/configurations-tab/additional-tools/esp-profiles.md), this is how you can check the deployment(s) has been added to the correct ESP Profile in Intune: 1. Sign in to the **Intune admin center** 2. Navigate to **Devices**
Navigating to “Devices”
3. Navigate to **Enrollment**
Navigating to “Enrollment”
4. Scroll down and select **Enrollment Status Page**
Scrolling down and selecting “Enrollment Status Page”
5. On the **Enrollment Status Page** click the relevant profile the PMPC Cloud deployment has been added to.
Clicking the relevant profile the PMPC Cloud deployment has been added to
6. On the ***\*** page, navigate to **Manage | Properties**
Navigating to “Manage | Properties”
7. Scroll down to the **Block device use until required apps are installed if they are assigned to the user/device** field. This shows the apps that must be installed before the user can use the device and will include the PMPC Cloud deployment if it was configured correctly.
Scrolling down to the “Block device use until required apps are installed if they are assigned to the user/device field”, which shows the apps that must be installed before a user can use the device
--- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.patchmypc.com/patch-my-pc-cloud/technical-references/intune-reference/check-esp-profiles-in-intune.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.