> 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-agent-ios-guide/8.3/configuration-for-installation-by-mdm-administrator-task.md).

# Configuration for Installation by MDM (Administrator Task)

Using an MDM solution you can manage and control the installation of the iOS Cortex XDR App across all managed corporate or personally-owned iOS devices.

These instructions are supplied by Palo Alto Networks to assist our customers. Support with third party vendor tools (with the exception of JAMF) is out of the scope of Palo Alto Networks.

1. [Create the iOS App installation package](/cortex-xdr-agent-ios-guide/8.3/install-and-connect-cortex-xdr-agent-app-for-ios/prepare-for-installation-administrator-task.md) using the Cortex XDR or Cortex XSIAM tenant, and then extract the app link and Distribution ID.
2. In the iOS MDM, create a mobile device app for Cortex XDR. The app is not publicly visible in the App Store. You must enter the app link that you got from the installation package manually. Searching the App Store won't return any results.
   1. Set a display name, such as Cortex XDR.
   2. Set the short version that you see in the app store.
   3. Set the bundle identifier "com.paloaltonetworks.cortex.ios"
   4. Set the app as Free.
   5. If available, set the distribution method to **Install Automatically**.
   6. If available, set **Automatically Force App Updates** if you intend to always keep the app up to date.
   7. If available, set **Convert Unmanaged App to Managed**.
   8. If available, set **Allow Users to Remove The App** to False.
3. Create the managed app configuration:
   1. Download our app configuration spec file [Download](https://docs-cortex.paloaltonetworks.com/v/u/NtjJYhxDwQ5K8Q4FmzvmNA):
      * App Config Spec File Name: iOSCortexXDR\_AppConfigSpec\_V1.xml
      * SHA-256: 8f0001398937f0b0ad6eeb72cfd022641557c112bb87e4c466fbffdc2b96c612
   2. There are three options, depending on the MDM provider:

      | MDM Provided Solution                                                                                                 | Actions                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
      | --------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
      | The provider allows the app configuration spec file to be uploaded and has a built-in editor for the required fields. | Upload the App Config Spec File to your MDM solution and follow the instructions to fill in the required fields.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
      | The provider allows the generated app configuration Plist file to be uploaded.                                        | <p>The AppConfig Generator is a third party tool which assists in the generation of configuration plist for a mobile app on a device enrolled in an MDM solution.</p><p>1. Go to <https://appconfig.jamfresearch.com/generator>.</p><p>2. Select <strong>Browse</strong> and upload the App Config Spec File.</p><p>3. Select <strong>Configure</strong>, and follow the instructions to fill in the required fields. <strong>Submit</strong>.</p><p>4. Select <strong>Download Plist</strong> and pass the generated Plist file in the app configuration tab of newly created mobile app.</p>   |
      | The provider allows the generated app to be entered or pasted into the configuration dictionary.                      | <p>The AppConfig Generator is a third party tool which assists in the generation of configuration plist for a mobile app on a device enrolled in an MDM solution.</p><p>1. Go to <https://appconfig.jamfresearch.com/generator>.</p><p>2. Select <strong>Browse</strong> and upload the App Config Spec File.</p><p>3. Select <strong>Configure</strong>, and follow the instructions to fill in the required fields. <strong>Submit</strong>.</p><p>4. Select <strong>Copy Dictionary</strong> and paste the generated dictionary in the app configuration tab of newly created mobile app.</p> |

These images are given for example only, they may differ from the application you are using.

![AppConfigGenerator01.png](/files/7EOmrkO5dLbAvyj3wJik)

![AppConfigGenerator02.png](/files/VscmnTuWaWqa0WDRrawS)

![AppConfigGenerator03.png](/files/Co6E4ZSOm4Gd4144C4cT)


---

# 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/cortex-xdr-agent-ios-guide/8.3/configuration-for-installation-by-mdm-administrator-task.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.
