--- title: "Enrollment of Mobile Device Management App Using Microsoft Intune" canonical: "https://docs.infoblox.com/space/BloxOneThreatDefense/35405259/Enrollment%20of%20Mobile%20Device%20Management%20App%20Using%20Microsoft%20Intune" format: markdown --- This guide provides step-by-step instructions for enrolling **Infoblox Mobile Endpoint (EP)** on iOS and Android devices using Microsoft Intune. The process includes downloading the required MDM configuration file, registering the endpoint with Microsoft Intune, and configuring the Infoblox App for deployment. > 📝 ### **Important Notes** > 📝 > 📝 - **Proxy Mode Warning:** The **proxy mode** feature has not been tested and may not function correctly. > 📝 - **Authorization Changes:** > 📝 - Older app versions will automatically update to the latest version, while new installations require updating the `joinToken` in the app configuration. > 📝 - For existing devices with older version of the app, the update to latest version is automatic. For fresh installations on new devices, the joinToken should be updated in the app configuration settings. > 📝 - Maintain both `customerId` and `joinToken` during the transition period until all devices are updated to 1.0.10 or above. > 📝 - Future versions of the app will **remove** `customerId`; ensure that both `customerId` and `joinToken` are maintained in configurations until all devices are updated. ### **Step 1: Download the MDM Config File from the Infoblox Portal** An **app-config file** is required to update the app’s configuration in the **MDM system**. To download the file: 1. Log into the **Infoblox Portal**. 2. Navigate to **Security **>** Threat Defense **>** Endpoints **>** Endpoint Groups**. 3. Select **Download MDM Configuration**, then click one of the two choices, depending on the device to be configured - **iOS Config File** - **Android Config File** 4. To assign an endpoint to a specific endpoint group: - Click the **three horizontal bars** icon next to the endpoint group name. - Select **Download MDM Configuration > Android Config File** or **iOS Config File**. 5. Save the downloaded configuration file to an easily accessible directory. ### **App Config File Parameters** The downloaded app-config file contains the following parameters: - **joinToken** – The value in the XML file. - **groupName** – The Infoblox Portal group to which the endpoint will be assigned. If the group does not exist, the endpoint will be added to **All Infoblox Endpoints**. - **userId** – A unique name that identifies a mobile device, displayed in **Security **>** Threat Defense **>** Endpoints**. - **allowServiceControl** – By default, this value is `True`. To disable and hide service control, toggle this value to `False`. - **extensionType (iOS only)** – Defaults to `"vpn"`, but can be set to `"dnsproxy"` to intercept DNS traffic via the **DNS Proxy Provider**. In MDM, the app config can be added manually or by uploading the XML file. ### **Step 2: Register a Mobile Endpoint to the Microsoft Intune Server** 1. Install the **Intune Company Portal** app from the **Google Play Store** or **Apple App Store**, depending on the device. 2. Log in to the **Intune Company Portal** using the credentials provided by your administrator. 3. Follow the on-screen instructions in the **Intune Company Portal** to register the device with the **Microsoft Intune Server**. ### **Step 3: Add the Infoblox App in the Microsoft Intune Server** ### **For Android Devices** 1. Navigate to **Home > Apps > Android > + Add > Managed Google Play**. 2. In the **Search** field, type **Infoblox**, then select the app. 3. Find **Infoblox Endpoint** in the list of apps. 4. Open the **Infoblox Endpoint** app, and add the necessary assignments. ### **Step 4: Upload and Add the App-Config File** 1. Navigate to **Home > Apps **>** App Configuration Policies**. 2. Click **+ Add **>** Managed Devices**. 3. Provide details about the platform (**iOS** or **Android**) and select the targeted app. *Image: Creating an app configuration policy.* 4. Using the downloaded **config file** from the **Infoblox Portal**, add the configuration by entering the required keys and values. - You can use the **XML file** or enter the key-value pairs manually. ### For iOS Devices Using the downloaded **config file** from the **Infoblox Portal**, add the configuration by entering the required keys and values. - You can use the **XML file** or enter the key-value pairs manually. > 📝 **Note** > 📝 Infoblox Endpoint version iOS 2.0.7 and above use the joinToken instead of customerId for authorization. For existing devices with older versions of the app the update to the latest version is automatic. Forr fresh installations on new devices, the joinToken should be updated in the configuration settings. ### **For Android Devices** 1. Using the downloaded **config file** from the **Infoblox Portal**, choose each **configuration key** and enter the respective value. 2. Navigate to the device and refresh the **assignments**. > 📝 **Note** > 📝 > 📝 - **Infoblox Endpoint Android version 1.0.9 and below** requires the `customerId` attribute in the app configuration. > 📝 - **Infoblox Endpoint Android version 1.0.10 and above** replaces `customerId` with `joinToken` for authorization. > 📝 - The `customerId` attribute will be removed in future versions of the app. Until all devices are updated to version **1.0.10 or later**, you may need to maintain both `customerId` and `joinToken` in the app configuration. ### **Final Steps** - Once all configurations are applied, go to the registered **device** and refresh the **assignments**. - The **Infoblox Endpoint** app will be automatically installed on the client device. This completes the **enrollment process**. ## Adding additional details related to the userID parameter By default, Infoblox assigns `'Default User ID'` to the `userId` parameter in the App Configuration for mobile endpoints. If this configuration is pushed to multiple devices via MDM, all users will appear with the same username in the Infoblox Portal. To assign a unique username to each mobile endpoint device, configure a user metadata variable using any relevant field based on your requirements. Set the `userId` parameter to a dynamic value using a variable in MDM. Key --> UserID Configuration Value ----> It can be any variable for any device metadata Some of the variables below are just for example: **{{deviceName}}** **{{username}** ![Assigning a configuration key value to the device name and user name. ](media://aa698491-5ea6-41d4-82c2-a1c56219997d)