> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/configuring_nexthink/bringing-data-into-your-nexthink-instance/connecting-mobile-devices-to-nexthink/nexthink-mobile-data-collection-faq.md). # Nexthink Mobile data collection FAQ Use the following answers to verify that your mobile devices meet the requirements for Nexthink Mobile data collection before you deploy the app.
Does Nexthink Mobile support bring your own device (BYOD) devices? Nexthink Mobile supports BYOD devices on Android only: * **Android**: Nexthink Mobile supports BYOD devices enrolled in a Unified Endpoint Management (UEM) solution with an Android work profile. Data collection on these devices may be more limited than on fully managed corporate devices. * **iOS and iPadOS**: Nexthink Mobile supports corporate-owned devices only. BYOD devices are not supported.
Do iOS and iPadOS devices need to be supervised? Only in Microsoft Intune. Intune distinguishes between managed and supervised iOS and iPadOS devices. Devices must be supervised to receive the Nexthink Mobile content filter. Refer to [Deploying on iOS and iPadOS devices](/configuring_nexthink/bringing-data-into-your-nexthink-instance/connecting-mobile-devices-to-nexthink/deploying-nexthink-mobile-in-intune/nexthink-mobile-for-ios.md) for more information. Supervision does not apply to other UEM platforms, such as Jamf or Omnissa Workspace ONE.
Does enrolling devices in Microsoft Intune, Jamf, or another UEM solution make them eligible for Nexthink Mobile data collection? No. UEM enrollment alone does not guarantee that a device supports Nexthink Mobile data collection. On iOS and iPadOS, data collection requires the Nexthink Mobile content filter. Whether you can deploy it depends on the following factors: * UEM platform * enrollment type * device ownership * supervision status, for devices in Microsoft Intune * existing content filter configuration Validate these prerequisites before you deploy Nexthink Mobile.
Can Nexthink Mobile coexist with Microsoft Defender, Zscaler, or other network and security apps on iOS and iPadOS? Coexistence depends on how each app and Nexthink Mobile are configured. On iOS and iPadOS, Nexthink Mobile collects data through an Apple content filter network extension. Security, VPN, web-filtering, and other network apps may also use network extensions or content filters. If an existing app uses a content filter configuration that conflicts with the one Nexthink Mobile requires, you cannot enable data collection in that configuration. For example, if Microsoft Defender already uses the device-wide content filter, Nexthink Mobile cannot use a conflicting device-wide content filter. Deployment options depend on the UEM platform, and some platforms offer more flexible content filter configuration than others. For example, Microsoft Intune supports only one device-wide content filter per device. Refer to [Deploying on iOS and iPadOS devices](/configuring_nexthink/bringing-data-into-your-nexthink-instance/connecting-mobile-devices-to-nexthink/deploying-nexthink-mobile-in-intune/nexthink-mobile-for-ios.md) for more information. Review your network and security configuration before deployment to identify content filter conflicts.
What happens if I cannot deploy the Nexthink Mobile content filter on iOS and iPadOS devices? Nexthink Mobile cannot collect data on the device. The content filter is a prerequisite for data collection on iOS and iPadOS. The device is not supported if you cannot deploy the required content filter configuration because of any of the following: * the device management model * UEM capabilities * a conflict with another content filter Nexthink does not bypass Apple platform restrictions or use private or unsupported APIs to collect data another way. To collect inventory and compliance data from devices without Nexthink Mobile data collection, configure the connector for your UEM platform: * [Intune: Mobile devices connector](/configuring_nexthink/bringing-data-into-your-nexthink-instance/integrating-nexthink-with-third-party-tools/inbound-connectors/connector-for-intune-mobile-devices.md) * [Jamf: iOS Mobile devices connector](/configuring_nexthink/bringing-data-into-your-nexthink-instance/integrating-nexthink-with-third-party-tools/inbound-connectors/jamf-ios-mobile-devices-connector.md)
Can Nexthink Mobile collect the same data on Android and iOS or iPadOS devices? No. Android and iOS or iPadOS give third-party apps significantly different levels of access. Android generally gives broader access to device health, performance, and connectivity information. Apple restricts third-party access to many device-level signals. As a result, Nexthink Mobile cannot collect some Android data on iOS and iPadOS, even when the device meets all deployment requirements. These differences come from operating system restrictions, not from Nexthink Mobile.
What should I validate before deploying Nexthink Mobile? Before deployment, validate the following: * whether devices are corporate-owned or BYOD * the device enrollment and management model * for Android BYOD devices, whether an Android work profile is deployed * for iOS and iPadOS devices, whether you can deploy the Nexthink Mobile content filter * for iOS and iPadOS devices in Microsoft Intune, whether the devices are supervised * which UEM platform manages the devices * whether Microsoft Defender, Zscaler, VPN, web-filtering, security, or other apps use network extensions or content filters * whether your UEM solution supports the content filter configuration that Nexthink Mobile requires Nexthink recommends validating these prerequisites before a large-scale deployment, particularly for iOS and iPadOS devices.
--- # 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://docs.nexthink.com/configuring_nexthink/bringing-data-into-your-nexthink-instance/connecting-mobile-devices-to-nexthink/nexthink-mobile-data-collection-faq.md?ask=&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.