> 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/unified-mdm-device-management.md).

# Unified MDM Device Management

Harmony now provides a unified API for managing devices across multiple Mobile Device Management (MDM) platforms. Instead of switching between vendor-specific consoles or building separate integrations for each provider, you can interact with all your connected MDM platforms through a single, consistent interface.

This unified approach abstracts away the differences between MDM vendors, so you can focus on managing your devices rather than navigating platform-specific quirks.

### Supported MDM Platforms

The unified MDM API currently supports the following providers:

* **Kandji**
* **JumpCloud**

Additional MDM platforms may be added over time as integrations are expanded.

### What You Can Do

Through the unified MDM API, you can perform the following actions across all your connected platforms from one place:

#### Send Device Commands

Issue commands to managed devices without logging into each vendor console separately. Commands are routed to the appropriate MDM provider automatically based on which platform manages the target device.

#### Upload and Deploy Custom Applications

Package and deploy custom applications to managed devices across your MDM providers. You no longer need to repeat the upload and deployment process in each vendor's interface - a single operation handles distribution to all targeted devices regardless of which MDM manages them.

#### Deploy Custom Scripts

Push and execute custom scripts on devices across all supported MDM platforms simultaneously. This makes it straightforward to enforce configurations, run diagnostics, or automate remediation tasks at scale without duplicating effort per provider.

#### Interact with Multiple MDM Providers

The API presents a consistent interface regardless of which underlying MDM platform manages a given device. This means your workflows, automations, and integrations remain uniform even as you add or change MDM providers over time.

### Benefits

* **Reduced operational overhead** - Manage all your MDM platforms from one place instead of maintaining separate processes for each vendor.
* **Consistent automation** - Build scripts and workflows once and apply them across every connected MDM provider.
* **Faster response times** - Send commands or deploy content to devices on any platform without switching contexts.
* **Scalability** - As your device fleet grows across different MDM providers, the unified API scales with you without requiring additional integrations.

### Getting Started

To begin using the unified MDM API, ensure that your MDM providers are connected to Harmony and that the relevant integrations are configured. Once your platforms are connected, you can use the unified API endpoints to send commands, deploy applications, and run scripts across all supported MDM providers in your environment.

For details on connecting specific MDM providers, refer to the integration guides for Kandji and JumpCloud in the Integrations section of this documentation.


---

# 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/unified-mdm-device-management.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.