Adoption Score – Implementing and Managing a Microsoft 365 Tenant

Formerly known as Productivity Score, Adoption Score is a metric that is used to help measure the success of an organization’s use of the Microsoft 365 platform. Before Adoption Score can be used, it must be enabled in the Microsoft 365 admin center underReports, as shown in Figure 1.31:

Figure 1.31 – Enabling Adoption Score

Adoption Score provides insights that are broken up into three categories: people experiences, technology experiences, and special reports. When enabling the score, you can select how to calculate insights into people experiences:

  • Include all users
  • Exclude specific users by group
  • Don’t calculate for any users

Insights into technology experiences are shown automatically when you enable Adoption Score. If you don’t want to collect that data, you can disable Endpoint analytics scope in the Intune data collection policy,

If you are performing a staged rollout of services using a pilot program, it may be beneficial to limit the reporting scope to groups of users that are part of the pilot.

People Experiences

The insights into people experiences focus on five categories that show how your users and organization are using the tools in the Microsoft 365 platform. These insight areas are as follows:

  • Communication: This area measures how people are communicating with each other, such as sending emails or instant messages or posting on communities in Viva Engage (or Yammer). This area highlights important practices such as using@mentions in emails and marking responses as answers in Yammer. Users need to be licensed for Yammer, Exchange Online, or Teams to be counted in this metric.
  • Content collaboration: This area measures how people use files in your organization, such as creating or sharing files in OneDrive for Business and SharePoint Online or how email attachments are being used (attached files versus a cloud attachment—a link to a file shared in OneDrive or SharePoint). It also captures data about the number of files shared and whether the collaborators are internal or external to the organization. Users need to be licensed for OneDrive for Business, SharePoint, or Exchange Online to be counted in this metric.
  • Mobility: This measures what devices and interfaces people are using to accomplish their work. For example, a user sending an email from the Outlook desktop app and the Outlook mobile app would be regarded as an individual using the Microsoft 365 apps across multiple platforms. This measurement area also reports on what locations people are working from—whether they are onsite in one of your organization’s offices or remotely. In order to be counted in this metric, users need to be licensed for Teams, Exchange Online, or Microsoft 365 apps.
  • Meetings: This area measures how effectively meetings are used across your organization. Meetings are evaluated against practices such as scheduling meetings at least 24 hours in advance, sharing agendas, and the percentage of invitees that actually show up to the meetings. Other features include measuring interactivity (hand-raising, chat, reactions, or sharing content) during the meeting as well as whether or not attendees are participating via audio or video. Users must be licensed for Microsoft Teams to be included in this metric.
  • Teamwork: This area is used to measure how people are collaborating in Teams and using shared workspaces (such as teams, channels, Microsoft 365 groups, and SharePoint sites). In order to be counted for this metric, users must be licensed for Exchange Online, SharePoint, or Microsoft Teams.

In addition to users requiring licenses to be assigned, they also need to be active in a service at least once every 28 days to get counted for that service. You can use Adoption Score to review how people are using the Microsoft 365 service and provide coaching on best practices to get the most out of the platform.

About the Author

Leave a Reply

Your email address will not be published. Required fields are marked *

You may also like these