Let’s build an SCCM Report Office 365 Client Upgrade Readiness Dashboard. This post is a continuation of Part1 and Part2, in my previous posts we imported two raw data reports that gave us information about different Microsoft Office versions.
We also understood a few more details got added after enabling the ‘Office365 ProPlusConfigurations‘ information on Office 365 Inventory. These details are visible only after enabling the Hardware class.
Let’s also learn how to manage the settings regarding OfficeMgmtCOM and Auto upgrade. In this post, we will see how we can get information on the readiness of the client ready for the O365 upgrade.
Starting with Configuration Manager version 1902, we can use the dashboard to identify devices with high confidence that are ready to upgrade to Microsoft 365 Apps.
This integration provides insights into potential compatibility issues with add-ins and macros in your environment. Then we can use Configuration Manager to deploy Microsoft 365 Apps to the ready devices.
The new Office 365 client management dashboard includes a new tile, Office 365 ProPlus Upgrade Readiness. This tile is a bar chart of devices in the following states:
- Not assessed
- Ready to upgrade
- Needs review
Prerequisites – Office 365 Client Upgrade Readiness
Enable hardware inventory in client settings. There are a few features that have been added in the Configuration Manager 1906 version also. Enabling this hardware inventory will start providing you with the data in the Configuration Manager Console.
The device needs connectivity to the Office content delivery network (CDN) to download an add-in readiness file. For more information, see Content delivery networks.
Microsoft 365 Apps readiness
After verifying you have the, browse to the below path to see the Upgrade Readiness Dashboard.
- In the Configuration Manager console, go to the Software Library workspace, and expand Office 365 Client Management.
- Select the Microsoft 365 Apps Upgrade Readiness node.
- Change the Collection and Target Office Architecture to change the information relayed in the dashboard.
Microsoft 365 Apps Upgrade Readiness dashboard.
Microsoft 365 Apps – Device Readiness Information
With the above dashboard, you can click on each individual state for example clicking on ‘Ready to Upgrade’ to get the detailed information of devices and then review it. You can also create a collection of them on which you can deploy the Office 365 application and monitor the Upgrade.
The most important part of upgrading to Office 365 is an add-in and Macro readiness, by default after enabling the required hardware Inventory the configuration manager scanning agent analyzes both this information and compares it with the information Microsoft has then grouped it accordingly in the dashboard.
To get detailed information on Macro compatibility you can deploy Readiness Toolkit for Office and analyze the code.
Office 365 Macro Readiness SQL Query
You can use the below SQL query to get the Raw data of Macro readiness.
select distinct OPR.name, CASE WHEN OPR.MacroInventory = '3' THEN 'Macro Present' WHEN OPR.MacroInventory = '1' THEN 'No Macro Present' WHEN OPR.MacroInventory = '4' THEN 'Needs Review' ELSE 'Other / Unknown' END as 'Macro Readiness' from vSMS_OfficeProplusReadiness OPR group by OPR.MacroInventory,OPR.Name
Office 365 Add-in Readiness SQL Query
You can use the vSMS_OfficeAddinReadiness view to get more information on add-in Readiness data. This view provides you information on different add-ins present in the environment with the count of devices having that particular add-in.
You can view different add-in Versions and their readiness.
select distinct OAR.AddinVersion as 'Addin Version',
OAR.FriendlyName as 'Addin Name',
OAR.AdoptionStatus as 'Adoption Status',
OAR.AddinReadiness as 'Addin Readiness'
from vSMS_OfficeAddinReadiness OAR
|Highly adopted||This add-in is being widely used on Microsoft 365 Apps in other organizations and is ready for use with Microsoft 365 Apps. But, the software provider doesn’t officially support the add-in on Microsoft 365 Apps.|
|Adopted||This add-in is being used on Microsoft 365 Apps in other organizations, but the software provider doesn’t officially support the add-in on Microsoft 365 Apps.|
|Adopted version available||A different version of this add-in is either “Adopted” or “Highly Adopted” on Microsoft 365 Apps.|
|Contact software provider||This add-in might have issues with Microsoft 365 Apps. You need to decide if this add-in is business-critical and then contact the software provider for guidance.|
|Supported version available||A supported version of this add-in for Microsoft 365 Apps is available from the software provider.|
|Unknown||This add-in is unknown to Microsoft. For example, it could be a line-of-business add-in that your in-house application development team created.|
If you create a basic report, the readiness status for all add-ins is listed as Unknown. It’s only when you create an advanced report that the Readiness Report Creator contacts Microsoft to try to get the readiness status of add-ins.
|Insufficient data||Microsoft has seen this add-in but not enough information has been collected to provide a readiness status for this add-in.|
O365 Readiness Upgrade Dashboard
I have tried to collate all the different information which is available as a part of the Office 365 upgrade readiness dashboard as a custom report.
The rdl file O365 Upgrade Readiness Dashboard will provide you information on a graph representation of Office365, Add-in, and Macro readiness.
This report also provides you Top 5 add-ins present in your environment.
References – SCCM Report Office 365 Client Upgrade Readiness Dashboard | Part 3
Hi, My Name is Ankit Shukla, and I have been working in IT since 2012. For the last 7 years, I have been working on SCCM/MECM. In these years have worked on different features of this tool, including Migration/designing the infrastructure/OSD/Custom SQL Reporting/Client-Side troubleshooting, and others. With my Blog Posts, you will find my experience on the issues which I have faced and solutions for them. The major objective of these posts is to reach out to the audience who are working as Support team members as SCCM Admins in their organizations.