> For the complete documentation index, see [llms.txt](https://docs.harmony.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.harmony.io/asset-management/resilient-mdm-device-data-processing.md). # Resilient MDM Device Data Processing Harmony now processes device data from Mobile Device Management (MDM) integrations in a more resilient and reliable way. Two focused improvements work together to reduce the chance of sync failures, incomplete asset records, or devices appearing as unrecognised - even when MDM-provided data contains minor inconsistencies or unexpected formatting. ### What Changed #### More Permissive Data Parsing Harmony previously used a stricter approach when parsing records from MDM integrations. Minor variations in data formatting, unexpected field values, or edge cases in individual data points could cause processing failures that resulted in: * Devices failing to sync correctly * Assets appearing as unrecognised in your account * Incomplete device data being written to asset records * Inconsistent handling of end-of-life events for managed devices Harmony now uses a more permissive parsing approach. This means that when MDM-provided data contains minor inconsistencies or malformed individual data points, the platform can still process the record successfully rather than failing or skipping it entirely. #### More Consistent End-of-Life Event Handling End-of-life event processing for managed devices has been made more consistent and reliable as part of these improvements. Devices reaching end-of-life status through your MDM integration are now handled in a more predictable way, reducing gaps in your asset records during those transitions. #### Streamlined Error Logging Error logging for MDM integration data processing has been streamlined. When issues do occur, the improved logging makes it faster and easier to identify and resolve them - reducing the time between a problem appearing and a fix being delivered. ### Benefits for Your Asset Records These changes combine to give you a more accurate and complete view of your managed device inventory in Harmony: * Fewer devices appearing as unrecognised due to formatting quirks in MDM data * More complete device information written to asset records during syncing * Reduced risk of processing gaps caused by individual malformed data points * More reliable overall sync behaviour between your MDM integration and Harmony ### Supported Integrations These improvements apply to all MDM integrations connected to Harmony. No configuration changes are required on your part - the more resilient processing behaviour is applied automatically. --- # 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://docs.harmony.io/asset-management/resilient-mdm-device-data-processing.md?ask=&goal= ``` `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.