Currently the Office Analytics runs every 7 days. This can be seen in c:\windows\ccm\logs\officeanalytics.log.
The frequency is configured in the c:\windows\ccm\OfficeAnalytics.mof file. Shown below:

instance of CCMSchedulerScheduledMessage

               {

                   ScheduledMessageID          = "{3C3D7A92-7971-4D35-ABBE-3DBA77126143}";

                   TargetEndpoint              = "direct:OfficeAnalyticsEndpoint";

                   TriggerMessage              = "<DAMessage MessageType='CollectOfficeData'/>";

                   Triggers                    = {"SimpleInterval;Minutes=10080"};                        // 1 week = 7 * 24 * 60

               };

This populates the table "OFFICEPRODUCTINFODATA"
and the view "vGSOFFICE_PRODUCTINFO "

The issue is if you configure inventory to be less than 7 days, the data does not match in the "vGSOFFICE365PROPLUSCONFIGURATIONS" view until the OfficeAnalytics inventory has run. For example version.

Please can the Office Analytics inventory run as part of hardware inventory so data will match.

Currently the Office Analytics runs every 7 days. This can be seen in c:\windows\ccm\logs\officeanalytics.log.
The frequency is configured in the c:\windows\ccm\OfficeAnalytics.mof file. Shown below:

instance of CCMSchedulerScheduledMessage

               {

                   ScheduledMessageID          = "{3C3D7A92-7971-4D35-ABBE-3DBA77126143}";

                   TargetEndpoint              = "direct:OfficeAnalyticsEndpoint";

                   TriggerMessage              = "<DAMessage MessageType='CollectOfficeData'/>";

                   Triggers                    = {"SimpleInterval;Minutes=10080"};                        // 1 week = 7 * 24 * 60

               };

This populates the table OFFICEPRODUCTINFODATA
and the view vGSOFFICE_PRODUCTINFO

The issue is if you configure inventory to be less than 7 days, the data does not match in the vGSOFFICE365PROPLUSCONFIGURATIONS view until the OfficeAnalytics inventory has run. For example version.

Please can the Office Analytics inventory run as part of hardware inventory so data will match.

It'll be better if we have this support in the DA portal where we can see the device name and other details as well...

currently,

DA is not supporting this level of reports unfortunately, for SCCM you can use Hardware Inventory: https://docs.microsoft.com/en-us/mem/configmgr/desktop-analytics/about-assets#apps The product is designed to make sure we are not listing all the device to review but to review the app common within device. The App versions details setting is off by default, so this tab combines all versions of apps with the same name and publisher. The default behavior helps reduce the total number of apps that you see, which helps reduce your efforts to annotate the apps. The count of apps in the Noteworthy Apps tile also reflects this setting. For example, instead of listing hundreds of instances of Microsoft Edge, there's one instance for all versions. You can make decisions once for all versions. If you need to make decisions about specific versions of an app, turn on this setting. You can also configure this setting when working with a deployment plan. For more information, see Plan assets.
‹1(current)›

Can you please add a filter that allows us to show more per page on Desktop Analytics? If I could choose between showing 10, 50, 100, 200, etc. per page it would make my life much easier when I am just trying to scroll and search through. It would also help when clicking the select all button. That button in particular annoys me because it only selects all on a single page. So, I have to click next page and click select all, over and over. Please just let us adjust the amount shown per page and it will fix multiple issues. Thanks!

Identifying devices for the pilot phase is great, however it would be perfect if we could find out why a machine is included.

For example if we tag app "A" as critical it would be good to be able to see that "Device123" was included because it had critical app "A" installed.

We can then also be confident that when we deploy a new FU we have app "A" covered but also that we dont have hundreds of devices with app "A" installed too - if we break app "A" during pilot we dont really want hundreds of devices to fix.

So giving us the reason a device is included would give us all vital information to make better decisions.