> 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/microsoft-azure-manual-onboarding/azure-manual-onboarding-guide/azure-manual-onboarding-subscription-scope/phase-5-complete-the-azure-onboarding-wizard-in-cortex.md).

# Phase 5: Complete the Azure onboarding wizard in Cortex

## Phase 5: Complete the Azure onboarding wizard in Cortex

To complete the onboarding process, return to the Azure onboarding wizard in Cortex. Provide the following mandatory and optional values back to Cortex in the Azure onboarding wizard.

### 5.1 Enter the Azure details in Cortex

After you have completed phases 2-4 to create the required Azure resources, you return to the Azure onboarding wizard in Cortex. To connect your Azure environment to Cortex, you must provide your Azure details. You can complete this using one of the two methods below:

* Automated upload: Quickly populate all required fields by dragging and dropping your JSON identifiers file directly into the wizard.
* Manual configuration: Manually input your Azure IDs into the corresponding text fields.

#### 5.1.2 Automated upload

To use the automated upload option, you must first populate the fields in the "manual\_details" section of the identifiers JSON file with the values from your Azure environment.

Locate the azure-identifiers-.json file that you downloaded in step 1.2. Open the file in a local text editor and populate the fields in the "manual\_details" section. Drag and drop the file directly into the Azure onboarding wizard. Verify that the fields in the Global Identifiers and Managed Identity sections are populated.

#### 5.1.3 Manual configuration

If you have not populated your JSON identifiers file, or prefer to enter details manually, follow these steps:

1. In the Azure onboarding wizard, in Global Identifiers, enter the relevant Azure IDs.
2. In Managed Identity, enter the required details.

### 5.2 Azure value reference guide

Core account details (all configurations)

| Field            | Value               |
| ---------------- | ------------------- |
| tenant\_id       | `<TENANT_ID>`       |
| subscription\_id | `<SUBSCRIPTION_ID>` |

ADS details (if ADS is enabled). Provide the value obtained during Phase 3.2:

| Field                             | Value                             |
| --------------------------------- | --------------------------------- |
| ads\_image\_gallery\_resource\_id | `<ADS_IMAGE_GALLERY_RESOURCE_ID>` |

ADS / DSPM details (if ADS or DSPM is enabled). Provide the values obtained during Phase 3:

| Field                     | Value        |
| ------------------------- | ------------ |
| resource\_group\_name     | `<RG_NAME>`  |
| resource\_group\_location | `<LOCATION>` |

Audit Logs details (if Audit Logs is enabled). Provide the values obtained during Phase 4:

| Field                                         | Value                    |
| --------------------------------------------- | ------------------------ |
| eventhub\_audit\_client\_id                   | `<AUDIT_UAMI_CLIENT_ID>` |
| namespace                                     | `<EH_NAMESPACE>`         |
| eventhub\_name                                | `<EH_NAME>`              |
| eventhub\_resource\_group\_name               | `<RG_NAME>`              |
| azure\_audit\_eventhub\_consumer\_group\_name | `<EH_CONSUMER_GROUP>`    |
| storage\_account\_name                        | `<STORAGE_ACCOUNT_NAME>` |

### 5.3 Complete onboarding

In the Azure onboarding wizard in Cortex, click Save. The new Azure cloud instance is created and is connected to Azure. You can view the Azure cloud instance status in Data Sources & Integrations. The initial discovery scan is started. When the scan is complete, you can view your cloud assets in Asset Inventory.

## Reference: Summary of resources created

### Identities

| Identity                                                             | Phase         | Required                      |
| -------------------------------------------------------------------- | ------------- | ----------------------------- |
| Cortex service principal (already in your tenant from admin consent) | Prerequisites | Yes                           |
| User-Assigned Managed Identity (UAMI) for Audit Logs                 | Phase 4       | Only if Audit Logs is enabled |

### Custom roles

| Custom Role          | Phase       | Module     | Scope          | Bound To                 |
| -------------------- | ----------- | ---------- | -------------- | ------------------------ |
| Cortex-Platform-Base | Phase 2     | BASE       | Subscription   | Cortex service principal |
| Cortex-DSPM          | Phase 3.1.1 | DSPM       | Subscription   | Cortex service principal |
| Cortex-DSPM-RG       | Phase 3.1.2 | DSPM       | Resource Group | Cortex service principal |
| Cortex-ADS           | Phase 3.2.2 | ADS        | Subscription   | Cortex service principal |
| Cortex-ADS-RG        | Phase 3.2.3 | ADS        | Resource Group | Cortex service principal |
| Cortex-Registry      | Phase 3.3.1 | REGISTRY   | Subscription   | Cortex service principal |
| Cortex-Automation    | Phase 3.4.1 | AUTOMATION | Subscription   | Cortex service principal |
| Cortex-KSPM          | Phase 3.6.1 | KSPM       | Subscription   | Cortex service principal |

### Role assignments (built-in Azure roles)

| Role                                     | Phase       | Module     | Scope                | Bound To                 |
| ---------------------------------------- | ----------- | ---------- | -------------------- | ------------------------ |
| Key Vault Crypto Service Encryption User | Phase 3.1.3 | DSPM       | Subscription         | Cortex service principal |
| Storage Blob Data Contributor            | Phase 4.4   | AUDIT LOGS | Storage Account      | UAMI                     |
| Azure Event Hubs Data Receiver           | Phase 4.9   | AUDIT LOGS | Event Hubs Namespace | UAMI                     |

### Federated credentials (workload identity federation)

| On   | Granted To                              | Phase     | Module     |
| ---- | --------------------------------------- | --------- | ---------- |
| UAMI | Cortex Collector Google Service Account | Phase 4.2 | AUDIT LOGS |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/microsoft-azure-manual-onboarding/azure-manual-onboarding-guide/azure-manual-onboarding-subscription-scope/phase-5-complete-the-azure-onboarding-wizard-in-cortex.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.