> 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/bring-your-own-azure-app-registration-byoa.md).

# Bring your own Azure app registration (BYOA)

For Azure outposts with your own app registration (BYOA): deploy a standard or custom Azure outpost with your own pre-created Entra ID app registration and, optionally, your own scanner managed identi

{% 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 %}

## What Cortex XDR creates without your own app registration

By default, when you do not turn on **Bring Your Own App Registration**, Cortex XDR creates the following identity resources in your Entra ID tenant and Azure subscription when you deploy the Terraform template:

* **Outpost app registration and service principal:** The identity that Cortex XDR uses to operate the outpost.
* **Microsoft Graph API permission requests:** Cortex XDR requests these permissions on the app registration. They become active only after an administrator grants admin consent during onboarding.
* **Federated identity credentials:** The trust between the app registration and the scanner managed identities.
* **Scanner managed identities:** The user-assigned managed identities for agentless disk scanning, DSPM, registry scanning, serverless scanning, and the egress proxy.

To create the app registration, the Terraform runner identity needs the `Application.ReadWrite.All` permission in Microsoft Entra ID, for example through the Cloud Application Administrator or Application Administrator role. For the permissions that each role includes, see [Microsoft Entra built-in roles](https://learn.microsoft.com/en-us/entra/identity/role-based-access-control/permissions-reference). The Terraform runner identity also needs the Azure roles on the subscription that any outpost deployment requires. For the full list, see [Create a standard outpost](https://cortex-docs.paloaltonetworks.com/cortex-xdr/configure-cortex-xdr/cortex-xdr-data-sources/cloud-service-provider-csp-onboarding/outpost-onboarding/working-with-standard-outposts/create-a-standard-outpost.md).

This default is the simplest option. Choose it unless your organization does not allow a third party to create app registrations in your tenant.

You can bring your own app registration (BYOA) to deploy a Cortex XDR Azure outpost with your own pre-created Microsoft Entra ID app registration, instead of having Cortex XDR create one. You can also bring your own scanner managed identities. This option is for organizations with strict governance policies that require control over Entra ID tenant-level resources. It is available for both standard and custom Azure outposts.

{% hint style="info" %}
**Note:** You can bring your own app registration only for Azure outposts, that is, when you scan with an outpost. It does not apply to Cloud Scan.
{% endhint %}

{% hint style="warning" %}
**Important:** After you deploy the outpost, you cannot change whether it uses your own app registration. Changing an existing outpost from a Cortex-created app registration to your own app registration is not supported. To use your own app registration, create a new outpost. Decide before you deploy.
{% endhint %}

## How your own app registration differs

The following table compares an Azure outpost where Cortex XDR creates the app registration with an outpost where you bring your own.

| Area                                                   | Cortex XDR creates the app registration (default)                                                                                      | You bring your own app registration                                                                                                                                                                                                                                                                                                                                                                            |
| ------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Who creates the app registration and service principal | Cortex XDR, during the Terraform deployment.                                                                                           | You, once, before you create the outpost.                                                                                                                                                                                                                                                                                                                                                                      |
| Entra ID permission for the Terraform runner identity  | The `Application.ReadWrite.All` permission, for example through the Cloud Application Administrator or Application Administrator role. | No Entra ID directory role. The Terraform runner identity is an owner of your app registration only.                                                                                                                                                                                                                                                                                                           |
| Scope of write access in your tenant                   | Any app registration in the tenant.                                                                                                    | Only your app registration. Cortex XDR does not write to your tenant beyond it.                                                                                                                                                                                                                                                                                                                                |
| Federated identity credentials                         | Cortex XDR creates them.                                                                                                               | Cortex XDR creates them on your app registration.                                                                                                                                                                                                                                                                                                                                                              |
| Scanner managed identities                             | Cortex XDR creates them.                                                                                                               | <p>Cortex XDR creates them, unless you also bring your own scanner managed identities.</p><p>If you bring your own scanner managed identities, grant the service principal of your app registration the Managed Identity Operator role on the resource group of the identities. The shell script grants this role for you. Without it, scans fail with a 403 <code>LinkedAuthorizationFailed</code> error.</p> |
| What you maintain after deployment                     | Nothing beyond the outpost.                                                                                                            | Your app registration and its service principal, the Terraform runner ownership, and your scanner managed identities if you bring your own. Do not delete or disable them while the outpost exists.                                                                                                                                                                                                            |
| Security considerations                                | The deployment requires a privileged Entra ID role for the duration of the deployment and of each upgrade.                             | Least privilege. No tenant-wide Microsoft Graph permission is needed, and you keep full control of the identity that Cortex XDR uses.                                                                                                                                                                                                                                                                          |

## Who provides what

The following table shows what you create and what Cortex XDR creates when you deploy the outpost.

| You create once                                                     | Cortex XDR creates during the deployment                                 |
| ------------------------------------------------------------------- | ------------------------------------------------------------------------ |
| The Entra ID app registration and its service principal             | All federated identity credentials on your app registration              |
| Ownership of the app registration for the Terraform runner identity | All outpost infrastructure, such as storage, networking, and scanner VMs |
| (Optional) The scanner managed identities                           | The scanner managed identities, unless you provide your own              |

## Workflow for your own app registration

Follow these steps to deploy an Azure outpost with your own app registration:

1. 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).
2. [Create the Azure 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/create-the-azure-app-registration.md) and its service principal in your Entra ID tenant, with [the shell script for Azure 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/the-shell-script-for-azure-app-registration.md) or in the Azure portal. Save the IDs.
3. Create the outpost, and enter the IDs in the wizard:
   * **Custom outpost:** See [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). You turn on **Bring Your Own App Registration** on the Global Settings page.
   * **Standard outpost:** See [Use your own app registration with a standard outpost](#use-your-own-app-registration-with-a-standard-outpost).
4. Deploy the Terraform template, and verify the outpost. Cortex XDR creates the federated identity credentials on your app registration, and everything else that the outpost needs.

## Use your own app registration with a standard outpost

You can bring your own app registration to a standard Azure outpost, without the other custom outpost options. In the outpost creation wizard, click **Show advanced settings**, and turn on **Bring Your Own App Registration**. The fields are the same as in the custom outpost wizard. For the procedure, see the Azure steps in [Create a standard outpost](https://cortex-docs.paloaltonetworks.com/cortex-xdr/configure-cortex-xdr/cortex-xdr-data-sources/cloud-service-provider-csp-onboarding/outpost-onboarding/working-with-standard-outposts/create-a-standard-outpost.md#step-2-define-the-outpost-with-the-outpost-creation-wizard).

You deploy the Terraform template with the same steps as any standard Azure outpost. The Terraform runner identity must be an owner of your app registration.

## What's next?

Continue with the following topics:

* [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)
* [Create the Azure 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/create-the-azure-app-registration.md)
* [The shell script for Azure 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/the-shell-script-for-azure-app-registration.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/bring-your-own-azure-app-registration-byoa.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.
