Onboarding and Inventory Deep Dive

Time to take a deeper look at how Inventory and onboarding works under the hood! Inventory in the Microsoft 365 Apps admin center is the best cloud-first solution for managing and reporting on the Office apps across your environment. But how do you set up this feature? How do you prepare your environment to use Inventory? Join Bob and Martin (Microsoft 365 Apps Rangers) as they walk you through the onboarding process and how to get started with Inventory.

NOTE: Since we released this video, a number of changes went into inventory. Your UI might look slightly different as well as on the devices, the COM object is no longer registered, as it is no longer needed.

========== CHAPTERS ==========
0:00 - Introduction
1:02 - Onboarding through auto provisioning
1:32 - Local device signatures for inventory
1:50 - Local device signature #1 - TAK
3:23 - Local device signature #2 - Scheduled Task
4:04 - Local device signature #3 - COM Objects
5:36 - Validating devices in inventory
6:59 - Reviewing security update status
7:21 - Troubleshooting onboarding #1 - TAK
10:16 - Automatic cleanup of stale devices
11:12 - Troubleshooting onboarding #2 - Local Agent
12:53 - Troubleshooting onboarding #3 - Security Approvals
14:35 - Wrap Up - Feedback - Get Connected

========== RESOURCES ==========

========== GET CONNECTED ==========

[OfficeDeploymentInsiders]

NOTE: Since we released this video, a number of changes went into inventory:
- The UI might look slightly different from what you see in the video.
- The COM object is no longer needed for inventory to work, so you will not see such being registered on the device.

[UrbyTuesday]

I have nearly 500 machines under my servicing profile and for the life of me there are about 20 that simply refuse to check in with the app portal. I went thru this video with such high hopes but to no avail. Checked the TAK, registry entries, dcom, scheduled task etc. All of it is on point. They are all showing 'last contact' dates. The build numbers are accurate. Only thing I haven't done is disjoin/rejoin AAD or reinstall Office Apps. I ran the update check manually on a couple of machines (one of which did require updates and which i did manually install them) but again...no update in the portal. I'm at a loss on this one.

[TheRealShrike]

Two comments.
1. I've been spinning my wheels for over a month now trying to figure out why my machines did not have the com object any longer. I have found zero documentation on this change other than this video which I re-watched today by coincidence. Extremely frustrating.

2. Just recently in the portal my machines are showing up and seem to be updating properly but for some reason about 5% of the machines are not showing the last user field and last user email. I've checked documentation, chat gpt, co-pilot etc and have found no useful information. Why would the last user not show up?

[puissance]

How can we identify all add-ins installed on a particular set of devices? When will this data be available via Graph?

[richardberry]

I have successfully on-boarded the device laptop-v730, which is an azure ad registered device. I checked the TAK, which is there, but when I checked in Component Services OfficeSBCManagerAddons is not present.

The device is showing in the Inventory but no stated COM+ component, any ideas why?

[shadywhiteguy]

We enabled the inventory feature 2-3 weeks ago. We have many devices that show in the Azure Active Directory admin portal under the "Devices" section, but do not show up in the O365 Config Inventory. Any idea what could be causing this. The missing PCs all have recently used O365 apps.

[superclips]

None of these suggestions are working to resolve problems. Especially the connection being established when a user signs in. The registry key doesn't get created. Why does Microsoft make it so hard to get anything done?