It seems like this is related to a change from Microsoft to anonymize user data.
Check this page for instructions on how to enable the correct values in reports: https://techcommunity.microsoft.com/t5/microsoft-365-blog/privacy-changes-to-microsoft-365-usage-analytics/ba-p/2694137