Mosyle MDM
Visualize Mosyle MDM devices, groups, and users, and monitor changes through queries and alerts.
- Installation
- Authorization
- Data Model
- Types
- Release Notes
Installation
You will need your Mosyle MDM email, password, and an access token to set up this integration. Access tokens can be created in the integrations settings of your Mosyle MDM console.
Configuration in Mosyle MDM
- Log in to your Mosyle MDM console.
- Navigate to the integrations settings page.
- Create a new Access Token for JupiterOne integration.
- Keep your email and password credentials ready, as they are required for authentication along with the access token.
Configuration in JupiterOne
To install the Mosyle MDM integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select Mosyle MDM. Click New Instance to begin configuring your integration.
Creating an instance requires the following:
-
The Account Name used to identify the Mosyle MDM account in JupiterOne. Ingested entities will have this value stored in
tag.AccountNamewhen theAccountNametoggle is enabled. -
Description to assist in identifying the integration instance, if desired.
-
Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as
DISABLEDand manually execute the integration. -
Your Mosyle MDM Email address that you use to log in.
-
Your Mosyle MDM Password that you use to log in.
-
Your Mosyle MDM Access Token created in the integrations settings.
-
Optionally, enable Use Manager API if you want to use the Manager API (https://managerapi.mosyle.com/v2) instead of the Business API (https://businessapi.mosyle.com/v1).
Click Create once all values are provided to finalize the integration.
Next steps
Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.
Entities
The following entities are created:
| Resources | Entity _type | Entity _class |
|---|---|---|
| Device | mosyle_device | Device |
| Device Group | mosyle_device_group | Group |
| User | mosyle_user | User |
| User Group | mosyle_user_group | UserGroup |
Relationships
The following relationships are created:
Source Entity _type | Relationship _class | Target Entity _type |
|---|---|---|
mosyle_device_group | HAS | mosyle_device |
mosyle_user | ASSIGNED | mosyle_device |
mosyle_user_group | HAS | mosyle_user |
Mosyle Device
mosyle_device inherits from Device
| Property | Type | Description | Specifications |
|---|---|---|---|
AssetTag | string | deprecated: true | |
deviceStatus | string | ||
DeviceStatus | string | deprecated: true |
Mosyle User
mosyle_user inherits from User
| Property | Type | Description | Specifications |
|---|---|---|---|
name | string |
Release Notes
- 2026-04-08 — Improved OS name accuracy for Mosyle MDM device entities, using human-readable names for macOS, iOS, iPadOS, and tvOS devices.
- 2025-04-29 — Added normalized email, short login ID, and email domain properties to Mosyle MDM user entities.