> 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-xdr/configure-cortex-xdr/cortex-xdr-data-sources/cloud-service-provider-csp-onboarding/ibm-cloud-cloud-onboarding/how-to-onboard-ibm-cloud.md).

# How to onboard IBM Cloud

Run the IBM Cloud onboarding wizard in Cortex XDR to create a pending cloud instance and download the Terraform authentication template.

{% hint style="info" %}
**License type:** This feature is included with a Cortex XDR license that has the Cloud Posture Security or Cloud Runtime Security add-on.
{% endhint %}

After you complete the prerequisites, run the IBM Cloud onboarding wizard in Cortex XDR. The wizard creates a cloud instance in Pending status and generates the Terraform authentication template that you deploy in IBM Cloud.

## Open the IBM Cloud onboarding wizard

Open the wizard from the **Data Sources & Integrations** page.

1. In Cortex XDR, select **Settings → Data Sources & Integrations**.
2. On the **Data Sources & Integrations** page, click **+ Add New**.
3. On the **Add Data Sources or Integrations** page, search for **IBM Cloud**, then hover over it and click **Add**.

## Review the scope and enter an instance name

The **Scope** field is set to **Account** and you can't change it. Each cloud instance represents one IBM Cloud account.

In **Instance Name**, enter a unique name for the cloud instance, or leave it empty to have Cortex XDR populate it automatically. Cortex XDR doesn't prevent you from reusing instance names, but it's best practice to use a unique name for every cloud instance.

## Configure advanced settings (optional)

Click **Show advanced settings** to define the following settings:

* **Scope Modifications:**
  * **Modify Scope by Regions:** Turn on to limit discovery to specific IBM Cloud regions. Select **Exclude** or **Include**, and then choose the regions. For the list of supported regions, see [IBM Cloud security capabilities and deployment planning](https://cortex-docs.paloaltonetworks.com/cortex-xdr/configure-cortex-xdr/cortex-xdr-data-sources/cloud-service-provider-csp-onboarding/ibm-cloud-cloud-onboarding/ibm-cloud-security-capabilities-and-deployment-planning.md).
  * **Disable environment scanning:** Select to onboard the account with environment scanning turned off. Environment scanning is available for all cloud service providers and all scope types. When you onboard an account with environment scanning turned off, Cortex XDR creates the cloud instance and you can deploy the template to grant permissions, but Cortex XDR doesn't run permission checks, asset discovery, or security capability scans for the instance. The cloud instance shows a **Connected** status, and its security capabilities show a **Disabled** status. Use this option to grant permissions first and start scanning later, for example during a phased rollout.

    <div data-gb-custom-block data-tag="hint" data-style="warning" class="hint hint-warning"><p><strong>Important:</strong> After you turn on environment scanning, either during onboarding or later by editing the cloud instance, you can't turn it off again. When you clear <strong>Disable environment scanning</strong>, you can't select it again.</p></div>
* **Cloud Tags:** Define tags and tag values that Cortex XDR attaches to the service ID it creates in your IBM Cloud account. IBM Cloud applies each tag as a `key:value` user tag.

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Note:</strong> The <code>managed_by:paloaltonetworks</code> tag is added automatically and is mandatory. You can't edit or remove it.</p></div>

## Save the configuration and download the template

Save your settings to create the pending cloud instance and the Terraform authentication template.

1. Click **Save**. Cortex XDR creates a cloud instance in Pending status and generates a Terraform authentication template based on your settings.
2. Click **Download Terraform** to download the Terraform authentication template, and then click **Close**.

The cloud instance stays in Pending status until you deploy the template and manually connect the instance. To continue, [deploy the Terraform authentication template in IBM Cloud](https://cortex-docs.paloaltonetworks.com/cortex-xdr/configure-cortex-xdr/cortex-xdr-data-sources/cloud-service-provider-csp-onboarding/ibm-cloud-cloud-onboarding/deploy-the-terraform-authentication-template-in-ibm-cloud.md).

{% hint style="info" %}
**Note:** If you close the wizard without downloading the template, you can download it later. On the **Cloud Instances** page, remove the filter that hides pending instances, right-click the pending instance, and select **Re-download Connection Template**.
{% 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://cortex-docs.paloaltonetworks.com/cortex-xdr/configure-cortex-xdr/cortex-xdr-data-sources/cloud-service-provider-csp-onboarding/ibm-cloud-cloud-onboarding/how-to-onboard-ibm-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.
