> 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/outpost-onboarding/working-with-custom-outposts/plan-your-custom-outpost.md).

# Plan your custom outpost

Make the decisions for your custom outpost before you start the wizard: the Outpost networking option, your own Azure app registration (BYOA), the regions, the deployment tool, and the Terraform runne

Before you start the Create Outpost wizard, make the decisions listed in this topic.

## Decide on the Outpost networking option

The **Outpost networking** option defines how the outpost's scanner VMs reach the internet, and what you enter for each region. Choose one of the following options:

* **Default:** Cortex XDR creates the network and manages outbound access through its own egress proxy. Choose this option unless you have a requirement that it does not meet, such as a policy that requires your own network or corporate proxy, or a policy that forbids outbound internet access from the outpost.
* **Custom:** You bring your own network (BYON), and, optionally, your own forward proxy. Choose this option only if your organization requires it, for example:
  * A security or governance policy forbids workloads in a network that a cloud vendor creates or controls.
  * All outbound traffic must go through an existing corporate egress path, such as a forward proxy, a TLS-inspecting proxy, or a central firewall.
  * Your network team must own and audit subnet-level security controls, such as network security groups, firewall rules, and security groups.
* **Egress routing off:** Cortex XDR creates the network, and scanner VMs have no outbound internet access. Choose this option only if the outpost must not reach the internet, and you accept that some capabilities do not work.

For details, see [Outpost networking options](https://cortex-docs.paloaltonetworks.com/cortex-xdr/configure-cortex-xdr/cortex-xdr-data-sources/cloud-service-provider-csp-onboarding/outpost-onboarding/working-with-custom-outposts/custom-outpost-concepts/outpost-networking-options.md).

{% hint style="warning" %}
**Important:** Custom networking transfers responsibility for the outpost's network layer to you for the life of the outpost. Cortex XDR does not create, monitor, or repair your network resources. Before you choose **Custom**, review [Custom networking (BYON)](https://cortex-docs.paloaltonetworks.com/cortex-xdr/configure-cortex-xdr/cortex-xdr-data-sources/cloud-service-provider-csp-onboarding/outpost-onboarding/working-with-custom-outposts/custom-networking-byon.md).
{% endhint %}

## Decide on outbound access for custom networking

If you set **Outpost networking** to **Custom**, decide how the scanner VMs reach the internet. Your choice defines the security group or firewall rules that you own, and the proxy settings that you enter in the wizard.

* **Direct outbound:** The scanner VMs reach the internet and the required cloud service endpoints directly, through your NAT gateway or firewall. This is the simplest configuration.
* **Outbound proxy without TLS inspection:** The scanner VMs send outbound traffic through your forward proxy. If the proxy requires authentication, you provide the proxy username and password when you deploy the template.
* **Outbound proxy with TLS inspection:** The scanner VMs send outbound traffic through your TLS-inspecting proxy. You provide the CA certificate that the scanner VMs must trust, in PEM format.

For the destinations that the scanner VMs must reach, see the [Outbound allow-list reference](https://cortex-docs.paloaltonetworks.com/cortex-xdr/configure-cortex-xdr/cortex-xdr-data-sources/cloud-service-provider-csp-onboarding/outpost-onboarding/working-with-custom-outposts/custom-networking-byon/outbound-allow-list-reference.md).

## Decide whether to bring your own app registration (Azure)

By default, Cortex XDR creates the Microsoft Entra ID app registration and the scanner managed identities for an Azure outpost. If your organization does not allow a third party to create app registrations or grant admin consent in your tenant, you can bring your own app registration (BYOA), and, optionally, your own scanner managed identities.

Use the following table to decide which option fits your requirements.

| If your requirement is                                                                                                                                                                                                         | Choose                                                                   |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------ |
| The simplest deployment, and you can grant the Terraform runner identity the `Application.ReadWrite.All` permission in Entra ID, for example through the Cloud Application Administrator or Application Administrator role.    | Let Cortex XDR create the app registration (default).                    |
| No tenant-wide Microsoft Graph permission for the Terraform runner identity, or your governance policies require that you create and own every app registration in your tenant.                                                | Bring your own app registration.                                         |
| The requirements for your own app registration, and also control over the scanner managed identities, such as your own naming conventions, a resource group that you own, or identities that remain if you remove the outpost. | Bring your own app registration and your own scanner managed identities. |

You cannot bring your own scanner managed identities without your own app registration. You can bring your own app registration together with any **Outpost networking** option. For details, see [Bring your own Azure app registration (BYOA)](https://cortex-docs.paloaltonetworks.com/cortex-xdr/configure-cortex-xdr/cortex-xdr-data-sources/cloud-service-provider-csp-onboarding/outpost-onboarding/working-with-custom-outposts/bring-your-own-azure-app-registration-byoa.md).

## Choose the regions

Decide which regions the outpost operates in. How you add them depends on the **Outpost networking** option:

* **Default** or **Egress routing off:** You select the regions from a list.
* **Custom:** You add each region separately, and enter the IDs of your network resources in that region. Only the regions that you add are enabled. You cannot combine regions that use your network and regions that use a network that Cortex XDR creates in the same outpost.

## Choose the deployment tool

The wizard generates a template that you deploy in your CSP. Choose the tool to use:

* **(AWS) CloudFormation, automated:** Cortex XDR opens the AWS console and runs the template for you.
* **(AWS) CloudFormation, manual:** You download the template and create the stack yourself.
* **Terraform:** You download the Terraform bundle and run it yourself. Terraform is available for AWS, Azure, and GCP.

If you set **Outpost networking** to **Custom** and you deploy with Terraform, you can [validate your network and proxy values](https://cortex-docs.paloaltonetworks.com/cortex-xdr/configure-cortex-xdr/cortex-xdr-data-sources/cloud-service-provider-csp-onboarding/outpost-onboarding/working-with-custom-outposts/custom-networking-byon/validate-your-network-and-proxy-values.md) before you deploy.

## Identify the Terraform runner identity

If you deploy with Terraform, identify the identity that runs Terraform. The Terraform runner runs `terraform apply` for the first deployment and for every future upgrade. In production, the Terraform runner is usually a service principal or service account, not a person.

The Terraform runner needs permissions to create the outpost resources. If you set **Outpost networking** to **Custom**, it also needs permissions to grant the scanner identity access to your network. These permissions must stay in place for the life of the outpost, so that you can apply upgrades.

{% hint style="info" %}
**Note:** If your network is in a different account, project, or subscription than the outpost, confirm which permissions the Terraform runner needs in each one. Mixing them up is the most common cause of deployment failures in this setup.
{% endhint %}

## What's next?

If you set **Outpost networking** to **Custom**, complete the [custom networking prerequisites](https://cortex-docs.paloaltonetworks.com/cortex-xdr/configure-cortex-xdr/cortex-xdr-data-sources/cloud-service-provider-csp-onboarding/outpost-onboarding/working-with-custom-outposts/custom-networking-byon/custom-networking-prerequisites.md). If you bring your own Azure app registration, complete the [prerequisites for bringing your own app registration](https://cortex-docs.paloaltonetworks.com/cortex-xdr/configure-cortex-xdr/cortex-xdr-data-sources/cloud-service-provider-csp-onboarding/outpost-onboarding/working-with-custom-outposts/bring-your-own-azure-app-registration-byoa/prerequisites-for-bringing-your-own-app-registration.md). Then [create a custom outpost](https://cortex-docs.paloaltonetworks.com/cortex-xdr/configure-cortex-xdr/cortex-xdr-data-sources/cloud-service-provider-csp-onboarding/outpost-onboarding/working-with-custom-outposts/create-a-custom-outpost.md).


---

# 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/outpost-onboarding/working-with-custom-outposts/plan-your-custom-outpost.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.
