👉 Note: MDM integrations are available on the Standard and Pro billing plans, and currently require activation by request. For more information, please contact Velory Support.
Connecting your MDM system to Velory gives you a unified view of your devices — and now also enables automated device releases at end-of-lifecycle, reducing manual work and keeping your data consistent.
🧠In this guide:
- Benefits of connecting your MDM system
- Where to see MDM data in Velory
- Automated MDM device release
- Flagged devices and admin review
-
Good to know
Benefits of connecting your MDM system
If your organization already uses an MDM solution to manage and secure devices, integrating it with Velory unlocks a unified and enriched asset management experience.
By connecting your MDM platform to Velory, we automatically enhance your Velory Asset data with relevant MDM insights, giving you a complete view of your devices across systems—without duplication or manual reconciliation.
Proactive alerts for expiring tokens and certificates
To ensure uninterrupted device management, Velory continuously monitors your connected MDM services and:
- Notifies IT admins with signs in Velory when critical tokens or certificates are about to expire
- Helps prevent downtime by enabling proactive renewals
- Reduces the risk of disruptions to device access or control
These automated alerts keep your MDM systems fully operational and give your IT team peace of mind to focus on strategic work.
Where to see MDM data in Velory
Once your MDM integration is active, the synchronized data will appear in multiple parts of the Velory platform, including:
-
Hardware Overview
-
Device Details pages
-
MDM Insights Report
You can also filter for MDM-connected devices directly in the interface. The MDM Insights Report allows you to:
- Compare and validate data between Velory Assets and your MDM system
- Identify discrepancies or missing information
- Gain visibility into device compliance, status, and data quality
- Take corrective action where needed
Automated MDM device release
👉 Note: Automated MDM device release requires an active MDM integration.
When a device reaches end-of-lifecycle — whether through a buyout or a return — Velory can automatically detect its removal from your MDM system and trigger the release process, without requiring manual intervention from an admin.
How it works:
Velory monitors your connected MDM system and automatically releases a device in Velory when all of the following conditions are met:
- The device has been removed from your MDM system
- The device status in Velory is either "Active – Bought out by employee" or "Active – Pending return"
This eliminates the need for admins to manually release devices at end-of-lifecycle or during offboarding, reducing errors and keeping your asset data consistent.
Flagged devices and admin review
If a device is removed from the MDM system but does not meet the approved status criteria, Velory will flag it for admin review instead of releasing it automatically.
Where to find flagged devices:
Flagged devices appear in a dedicated view within the standard Hardware table. This gives admins a clear overview of devices that need attention.
What admins can do:
- Review the flagged device and its current status
- Confirm the release manually if appropriate
When an admin confirms a release, Velory logs the following in the event log on the device details page:
- Admin name
- Device identifier
- Timestamp of the confirmation
- A note confirming the admin's release action
💡 If a device was incorrectly released, admins can follow the standard process to restore it — for example, by moving it to a repair flow.
Good to know
|
What happens if my MDM is not connected?
|
The automated release flow requires an active MDM integration. Without it, the standard manual release process applies. |
|
Which device statuses trigger the automatic release?
|
Currently, the auto-release is triggered for devices with the status "Active – Bought out by employee" or "Active – Pending return." Additional criteria may be added over time. |
|
What if a device is released by mistake?
|
Admins can restore the device through the standard process, for example by moving it into a repair flow. |
|
Can I see a history of release actions?
|
Yes. When an admin confirms a release for a flagged device, a timestamped event is recorded on the device details page. |