> 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/troubleshoot/deployments/why-is-the-deploy-button-greyed-out-in-cloud.md).

# Why is the “Deploy” button greyed out in Patch My PC Cloud?

*Applies to: Patch My PC Cloud*

### SYMPTOMS

Why when I try to deploy an app, is the **Deploy** button greyed out?

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2Fjr9OK3LdL3Yc1GWbNDty%2Fimage.png?alt=media&amp;token=4c253d1b-93b0-45d1-87f7-e203f249348c" alt="“Deploy” button greyed out."><figcaption></figcaption></figure>

### CAUSE

This can be caused if you add the **UpdateOnly** assignment type to a deployment that is configured to use an [ESP Profile](/patch-my-pc-cloud/deployments/deploy-app/configurations-tab/additional-tools/esp-profiles.md) which is unsupported in Intune. If you look at the **Configurations** tab it will show a read "**X**" highlighting the configuration conflict.

### RESOLUTION

To resolve this issue:

1. Click the **Configurations** page of the deployment.<br>

   <figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FJE4ZLKfFelf28xLFYvio%2Fimage.png?alt=media&amp;token=13c8adaf-8618-446a-89fe-17ad2432b9c4" alt="Clicking the “Configurations” page"><figcaption></figcaption></figure>

   \
   If the problem is caused by an ESP Profile being configured, the **ESP Profiles** tab will be automatically opened.<br>

   <figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2F41nphZYKM3RbsNrGYWpO%2Fimage.png?alt=media&amp;token=85e41deb-ed58-42c2-816d-c886a83206f6" alt="“ESP Profile” tab automatically opened"><figcaption></figcaption></figure>
2. Scroll down to the **ESP Profiles** section, under which you will see the following message:<br>

   **ESP profiles should be empty when the assignments list contains only UpdateOnly assignments.**<br>

   <figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FkczjrzuFgMdfLpeZrhMx%2Fimage.png?alt=media&amp;token=deabe02a-99e2-425e-b3e0-bc2d622f6bc3" alt="“ESP profiles should be empty when the assignments list contains only UpdateOnly assignments.” message"><figcaption></figcaption></figure>
3. You now need to decide whether you:

   a. Remove the **UpdateOnly** assignment

   b. Change this deployment to not use any ESP Profiles.\
   \
   Either of these options will enable the **Deploy** button.


---

# 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/troubleshoot/deployments/why-is-the-deploy-button-greyed-out-in-cloud.md?ask=<question>&goal=<user_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.
