Mosyle Manager
Device management integration
Connect Mosyle Manager user lifecycles, Apple device assignments, and inventory data to your NIM processes.
At a glanceDirect link to At a glance
The PowerShell connector connects to the Mosyle Manager education API at https://managerapi.mosyle.com/v2. It imports users, devices, classes, group relationships, compliance results, and custom attributes. Supported actions include user creation, updates, and deletion; device assignment and management; and device group membership changes.
You need a Mosyle account with API access, its Username (email) and Password, and an Access Token. The connector requires Windows PowerShell 5.1 or later. See Configure connection for setup and validation.
This connector targets Mosyle Manager, not the Mosyle Business API. The capabilities below were reviewed against connector package 2.0.0 on November 4, 2026; that package version is separate from the NIM service baseline above. Source review does not establish runtime acceptance in your tenant.
Solutions this integration supportsDirect link to Solutions this integration supports
User lifecycle provisioning
Create, update, and delete Mosyle Manager users from trusted student and staff identity data.
- Keeps user records aligned with source data
- Reduces manual account administration
Device assignment and administration
Assign devices to users, update supported device details, move devices to Limbo, and send lock commands through NIM.
- Makes approved device changes repeatable
- Connects device assignments to identity processes
Device group membership changes
Add and remove devices in supported dynamic and shared device groups using NIM actions.
- Aligns assignments with approved changes
- Reduces manual device group administration
Device and classroom visibility
Collect devices, classes, class relationships, compliance results, and custom attributes for NIM filters and reports.
- Makes inventory and relationships available for review
- Reduces manual data collection
GuidesDirect link to Guides
Connector repository
Browse the Mosyle Manager connector repository on GitHub.
Review the Mosyle Manager PowerShell source for the function definitions and request parameters.
Supported operationsDirect link to Supported operations
Filter tables by supported operation
Showing 14 of 14 tables| Table | Read | Create | Update | Delete |
|---|---|---|---|---|
| Accounts | ||||
| ClassCoordinators | ||||
| Classes | ||||
| ClassStudents | ||||
| ClassTeachers | ||||
| CustomDeviceAttributes | ||||
| DeviceCustomAttributeValues | ||||
| DeviceGroupDevices | ||||
| Devices | ||||
| DynamicDeviceGroups | ||||
| DynamicGroupDevices | ||||
| IOSSecurityCompliance | ||||
| SharedDeviceGroups | ||||
| Users |
The table summarizes read collections and their related write capabilities. Group membership actions modify assignments; they do not create or delete group definitions. Classes and class relationships are read-only.
Available actionsDirect link to Available actions
| Area | Connector functions | Behavior |
|---|---|---|
| Users | UserCreate, UserUpdate, UserDelete | Create, update, or delete a Mosyle user. |
| User device assignment | UserAssignDevice | Assign a device using the user id and device serial_number. |
| Device details | DeviceUpdate | Update supported asset_tag, tags, name, or lock fields using serialnumber. |
| Device unassignment | DeviceUnassign, DeviceUpdateLimboLocation | Move selected devices or groups to Limbo and update the location of selected Limbo devices. |
| Device lock | DeviceLock | Send a lock command for selected devices, with optional PIN, phone number, and message. |
| Dynamic group membership | DynamicDeviceGroupAdd, DynamicDeviceGroupRemove | Add or remove device assignments using idgroup. |
| Shared group membership | SharedDeviceGroupAdd, SharedDeviceGroupRemove | Add or remove device assignments using idshareddevicegroup. |
| Custom device attributes | CustomDeviceAttributeUpdate | Update an attribute definition/value using the required OS, identifiers, name, and value. |
A successful command response does not establish that the device has completed the command. Confirm the result in Mosyle and on the device where applicable.