Let’s kick this off with a quick throwback to Endpoint Privilege Management (EPM). Remember when EPM made its debut, and we all got a glimpse of Microsoft’s shiny new platform—MMP-C (Microsoft Managed Platform – Cloud)? Back then, EPM introduced us to the Declared Configuration protocol as the backbone for delivering its policies. Well, that was just the warm-up act. Microsoft had bigger plans for MMP-C, and now it’s taking center stage with Device Inventory.
Buckle up, because we’re diving deep into how the Properties Catalog profile (Device Inventory Policies) flows through MMP-C (Microsoft Management Platform – Cloud), makes its way to the device, and brings all that sweet inventory data back into Resource Explorer.
Table of Contents
What’s MMP-C Again?
For those who skipped the EPM intro, here’s the TL;DR:
- MMP-C is Microsoft’s cloud-based management platform.
- It uses the Declared Configuration protocol, which is more efficient than the old-school SyncML (think “state-based management” rather than “command-and-control”).
- It doesn’t just deliver policies; it ensures the device matches the desired state without redundant back-and-forth chatter.
EPM was the first kid on the block to use this, allowing privilege elevation policies to be delivered cleanly. Now, with Device Inventory, MMP-C takes things up a notch by collecting detailed hardware and software data.
The Journey of a Properties Catalog Profile
Here’s how it all comes together, step by step:
1. Defining the Properties Catalog in Intune
It starts in the Intune admin center. You define a Properties Catalog profile, enabling the exact properties you want to track, like TPM version, CPU specs, and logical drive details. The kicker? All properties are disabled by default, so you need to cherry-pick the ones that matter.
2. Delivery Through the MMP-C Channel
Once you hit “save” and assign the profile, Intune hands it over to MMP-C. The profile gets packaged as a Declared Configuration document (WinDC, for those who love acronyms) and is queued for delivery during the next device sync.
3. Policy Lands on the Device
The device syncs with the MMP-C infra, pulling down the Declared Configuration and applying it.
If the Device Inventory Agent isn’t already installed, it gets deployed as part of this process. This agent is the real MVP—it’s responsible for collecting all the inventory data.
4. Data Collection by the Device Inventory Agent
The Device Inventory Agent fires up and starts harvesting data based on the properties you selected in the catalog. It uses WMI queries to pull details like:
- TPM status (Is it present? Is it version 2.0?).
- CPU specs (cores, clock speed, etc.).
- Logical drive information (capacity, free space).
Please Note: Random Harvesting Time is enabled by default
With the random harvesting enabled, it would pick a “random” time to start the initial harvesting.
Once the Device Inventory Agent collects all the required data for the selected properties, it temporarily stores this information in a local database (SQL Lite.. and yes you can open it) on the device, known as the Harvester DB.
5. Uploading Data to the Service
During the next sync (typically once a day), the harvested data is uploaded to the Intune Data Platform.
When we have Fiddler in place, we can spot this Data upload to manage.microsoft.com
6. Viewing Data in Resource Explorer
Once the data lands in the Intune backend, it shows up in Resource Explorer. This is where the magic happens! You can view the detailed inventory for every device.
Viewing Data with Graph
Besides Resource Explorer in Intune, we can also use Microsoft Graph to view the properties.
The Visual Flow
Troubleshooting: When Things Go South
Not seeing data in Resource Explorer? Here’s what to check:
- Is the Device Enrolled with MMP-C?
- Make sure it’s dual-enrolled in both Intune and MMP-C. To do so you need to check out if the LinkedEnrollment is configured.
- Is the Inventory Agent Installed?
- Confirm the Device Inventory agent is running on the device.
- Is the Inventory Agent service running?
- Are the Declared Policies on the device?
- Sync Issues?
- Check the MDM Diagnostic Logs to see if there’s a communication issue with MMP-C.
- Use the Sync ml tool to find out if the Policies are coming down
Final Thoughts
From EPM’s privilege management to Device Inventory’s detailed insights, MMP-C is redefining modern device management. It’s efficient, reliable, and scalable—everything you need for today’s hybrid environments.
So next time you’re admiring the clean inventory data in Resource Explorer, give a little nod to MMP-C. It’s doing the heavy lifting behind the scenes, one declared configuration at a time.