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

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

*Applies to: Patch My PC Cloud*

### SYMPTOMS

I am trying to create a child Patch My PC (PMPC) Cloud company using the Managed Service Provider (MSP) feature.

However, after clicking **Connect** and authenticating, I get the following error:

**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%2FlVFz1AWhSqpax0y1qRKw%2Fimage.png?alt=media&amp;token=fb73691a-4470-4722-ba66-35bfa1c316d9" alt="“Intune connection with the same Id found in another environment!” error" width="538"><figcaption></figcaption></figure>

### CAUSE

This is because the Intune tenant you are trying to connect is already in use by another company, probably because the child company already exists.

We do not support sharing an Intune tenant between multiple PMPC Cloud companies.

### RESOLUTION

Sign in to the child company and navigate to **Settings | Environments** and if Intune is already connected, delete the connection.

{% hint style="info" %}
**Note**

See [Deleting an Intune tenant connection](broken://pages/RoXhXa1jcXhIcPcKJk05#deleting-an-intune-tenant-connection) for more information.
{% endhint %}


---

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