LM SaaS M365 monitoring
Anyone using LM SaaS-based Office365 monitoring and can check something for me? With the legacy/deprecated Office365 checks, LM would collect many of the stats by using the GraphAPI. This works by downloading a CSV file from M365 which provides 7 days of data. The problem is that this CSV file, at best, is atleast one day behind but frequently even more behind than that. I covered that issue in an old post about it here. Can someone confirm if the newer SaaS method has the same problem? I don't currently have it but looking at the DataSources it says it uses a method of "SAAS OFFICE365 CSV REPORT" and there is still a "Data Offset" datapoint, so I assume it will have the same problem. As far as I know, that is the only way to get this information from M365 so it's kinda understandable. But I guess it's possible LM can do some special backend thing to backdate the data, since they control the whole process, but seems unlikely. You can likely tell by looking at the "Office365 Email Activity" graph with a 30-day change, and check if weekday spikes are offset into the weekend. Assuming most email activity will be M-F for your environment(s). Thanks!172Views0likes0Comments