> 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/outpost-troubleshooting.md).

# Outpost troubleshooting

Check here for solutions to issues that might occur while configuring, deploying, and operating outposts.

This document provides solutions for issues that might occur while deploying, configuring, and operating Cortex XDR outposts. These troubleshooters can help identify symptoms, locate errors, and suggest how you can remediate.

## General troubleshooting

These general troubleshooters apply to all cloud service providers and outpost deployment modes.

**The template deployment completes successfully but no outpost appears in Cortex XDR**

After the template deployment completes successfully, your cloud environment sends a notification to Cortex XDR to register the new outpost. If the outpost doesn't appear in the Cortex XDR console, verify that outbound internet connectivity is available from the environment where the template was deployed. The notification requires an active connection to reach Cortex XDR. If connectivity is confirmed and the outpost still doesn't appear, contact customer support for a manual workaround.

**Terraform template execution fails on a non-approved tenant, such as after changing the target tenant mid-deployment**

If Terraform execution fails on a non-approved tenant, such as if you change an Azure target tenant after starting outpost creation. Terraform execution fails because the outpost is bound to the originally-approved tenant. Delete the partially-created outpost from the Cortex console, revert to the approved tenant, and re-run the Terraform template.

**An `Update available` indicator appears next to the outpost status**

The outpost template is older than the current template. Hover over the indicator to see the version details. For details, see [View and manage outposts](https://cortex-docs.paloaltonetworks.com/cortex-xdr/configure-cortex-xdr/cortex-xdr-data-sources/cloud-service-provider-csp-onboarding/outpost-onboarding/view-and-manage-outposts.md#outpost-updates).

**(Azure) Serverless scanning fails with an HTTP 403 error when the outpost downloads Azure Function code**

The scan fails with an error similar to `failed to download Azure function code: HTTP 403` and `Error 403 - Forbidden`. This error can occur when the access restrictions of the Azure Function allow only specific IP addresses, and the outpost connects from an IP address that is not on the allow list. In Cortex XDR, edit the Azure cloud instance, turn on **Static IP Access**, select the region, and add the static IP address that Cortex XDR retrieves to the access restrictions of the Azure Function. For details, see [Configure advanced settings](https://cortex-docs.paloaltonetworks.com/cortex-xdr/configure-cortex-xdr/cortex-xdr-data-sources/cloud-service-provider-csp-onboarding/microsoft-azure-cloud-onboarding/how-to-onboard-microsoft-azure.md#configure-advanced-settings-optional). If the function is reachable only over a private network, such as through VNet integration or private endpoints, turn on **Allow connection to private serverless functions** instead, and then download and apply the updated Terraform or ARM template.

## Standard outpost troubleshooting

Standard outposts handle most of the infrastructure and identity provisioning automatically. Issues in this deployment mode might stem, for example, from broad permission gaps, restrictive policy definitions, or quota limits that prevent Cortex from deploying necessary resources.

### AWS CloudFormation deployment troubleshooting

These troubleshooters apply when you deploy an AWS outpost with CloudFormation, either with **Execute in AWS** or by uploading the downloaded CloudFormation template.

**The stack fails because a service-linked role already exists**

The template creates the `AWSServiceRoleForEC2Spot` and `AWSServiceRoleForRedshift` service-linked roles by default. If either role already exists in the account, stack creation fails. Delete the failed stack, deploy the template again, and set the **Create service-linked roles (set to false if they already exist)** parameter to `false`.

**The stack cannot be created because IAM resources were not acknowledged**

The template creates IAM resources with custom names, so AWS requires an explicit acknowledgement. On the create-stack page, select **I acknowledge that AWS CloudFormation might create IAM resources with custom names**, and then create the stack.

**The stack status does not reach CREATE\_COMPLETE after you click Execute in AWS**

The stack might have been created in the wrong AWS account, or it might have failed in the AWS CloudFormation console. Verify that your browser session is logged in to the AWS account that is dedicated to the outpost. In the AWS CloudFormation console, review the stack events for the failure reason, resolve it, and deploy the template again.

**The template cannot be loaded in the AWS CloudFormation console after Execute in AWS was clicked**

The link that **Execute in AWS** opens is valid for a limited time. If the **Quick create stack** page was left open too long, or the link was used later, the template link might have expired. Return to the outpost creation wizard in Cortex XDR and click **Execute in AWS** again to open a new link.

**A stack deployed from a downloaded CloudFormation template completes, but the outpost does not register with Cortex XDR**

The downloaded CloudFormation template contains a registration link that expires 7 days after download. If the template was deployed after the link expired, the outpost cannot notify Cortex XDR. Delete the stack, download a new CloudFormation template from the outpost creation wizard, and deploy the new template.

## Custom outpost troubleshooting

For issues with custom outposts, including custom networking (BYON), your own Azure app registration (BYOA), and **Egress routing off**, see [Custom outpost troubleshooting](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-troubleshooting.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/outpost-troubleshooting.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.
