> 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/environments/intune-connection-with-the-same-id-found-in-another-environment-error-in-cloud.md).

# “Intune connection with the same Id found in another environment” error in Patch My PC Cloud

*Applies to: Patch My PC Intune Apps*

### SYMPTOMS

When I click **Connect** in the **Environments** node to connect my Patch My PC (PMPC) Cloud portal to Intune, after accepting the permissions, I see the following:

**Error**

**Intune connection with the same Id found in another environment**

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FYgmqC0hhBpPKHx1aDsuJ%2Fimage.png?alt=media&amp;token=77666a22-6197-4b2f-aa6d-67cc9c949651" alt="&#x22;Intune connection with the same Id found in another environment&#x22;"><figcaption></figcaption></figure>

### CAUSE

This error is telling you that this Intune tenant is already connected to a different PMPC Cloud Company.

At present, you can only have an Intune tenant connected to one PMPC Cloud.

### RESOLUTION

You need to decide which PMPC Company you want to be connected to this Intune tenant.

Then either disconnect Intune from the other PMPC company so you can use it with this one or setup a new Intune tenant to use with this company.


---

# 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/environments/intune-connection-with-the-same-id-found-in-another-environment-error-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.