> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-cloud-posture-management/onboard-and-configure/deployment-steps-and-checklist/upgrade-from-prisma-cloud-to-cortex-cloud/link-cortex-cloud-to-prisma-cloud.md).

# Link Cortex Cloud to Prisma Cloud

Link your Cortex Cloud and Prisma Cloud tenants before migrating.

To link your Cortex Cloud tenant to a Prisma Cloud tenant, first obtain the **Access Key** from Prisma Cloud, and then paste it in the **Link Tenant** section of the Upgrade Helper to establish the link.

### Obtain the Prisma Cloud tenant access key

1. Log in to your Prisma Cloud tenant as an administrator.
2. Go to **Settings** → **Enterprise Settings** .
3. Click **Generate Token** in the **Cortex Cloud Tenant Linking** section.
4. Copy the **Access Key**.

### Link from Cortex Cloud

1. Log in to Cortex Cloud as an administrator.
2. Navigate to **Settings** → **Configurations** → **Upgrade Helper**.
3. Click **Create Link** in the **Link Tenant** section.
4. Enter the Prisma Cloud **Access Key**.
5. Review the details of the Prisma Cloud tenant, such as Tenant Name, Tenant ID, and Region.
6. Click **Connect**.


---

# 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://cortex-docs.paloaltonetworks.com/cortex-cloud-posture-management/onboard-and-configure/deployment-steps-and-checklist/upgrade-from-prisma-cloud-to-cortex-cloud/link-cortex-cloud-to-prisma-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.