Please note that MDM integrations are only available with the Lifecycle billing plan / Standard and are currently accessible by request only. For more information, reach out to support.
This article includes the following topics
- How to connect Google MDM with Velory
- How it works
- Additional reports
- Disconnect
- Questions and answers
How to connect Google MDM with Velory
- Go to your profile in the navigation bar and click on Settings, then under Integrations click on Connections.
- Here, you can view the available MDM solutions for connection. To link an MDM solution to Velory, simply click Connect next to your chosen option.
- By clicking Connect, you'll be asked to authorize Velory to read device data from your Google Account. Clicking the Read more link will take you to the MDM provider's page, where you'll find detailed instructions on how to retrieve the required information. It's super simple, we promise!
- Once the connection is established, Velory will start fetching device data for you. It may take about 2 minutes for all devices to be fetched and matched from Google. After that, devices will be automatically synced every night. So easy!
How it works
Once your Google Devices MDM solution is connected, you can access the connection details and view a dedicated dashboard filled with valuable insights such as devices enrolled and unmatched devices.
Enrolled & Unmatched Devices
You can view Enrolled Devices and Unmatched Devices by clicking on the respective sections within the connection page. This will redirect you to the Hardware Table, with relevant filters applied for better viewing.
In the hardware view, you can filter devices by their status—whether they are enrolled or unmatched—to quickly get an overview.
Data Import
You can edit the Data Import section by simply checking or unchecking the boxes to select which data should be included or excluded during synchronization, default synchronization is done at 6.30am (Stockholm time). By default, all fields are enabled. If you deactivate any field, it will be excluded from future imports starting with the next scheduled sync.
Here’s some extra explanations of them:
Model | The model description of the device |
Device OS | The operating system’s version in use on the device |
Last check in | The last time the device connected with the MDM system |
User full name | The assigned user name from the MDM system |
On a device’s detail page, you’ll find lots of useful information. What you see depends on which data points you've chosen to enable or disable in the connection settings. If nothing is turned off, all the data will be displayed right on the device page.
Additional reports
Along with the information available in Velory for the MDM integration, you can also access a customizable report dashboard. This dashboard provides valuable insights, including asset and MDM comparisons as well as enrollment statistics. If you enable the connection and would like the additional report, please contact support@velory.com, and we’ll assist you in setting it up.
Disconnect
To disconnect the MDM solution, simply click the Disconnect Google button on the details page.
When the connection is disabled, all MDM information is removed from Velory, including on the connection page, hardware overview, device details, and CSV export. If you need a record of the data before disconnecting, you can perform a CSV export to capture which devices were linked to which MDM system.
Questions and answers
Question | Answer |
How does Velory read information from the customer’s tenant? | Velory registers an OAuth app allowing it to exchange for a refreshToken after the user authenticates against the OAuth app. |
How does Velory store the information from the customer’s tenant? |
The information is stored in Velory’s database and the customer can control what fields allow us to save from the Google Device connection page. |
How does Velory authenticate against the customer’s tenant? | The refresh token is used to generate an access token allowing us to call Google on the customer’s behalf and get data where Velory is allowed. |
How does Velory store authentication details? | We encrypt the refresh token and store it in the Velory database. |