Microsoft Secure Tech Accelerator
Apr 03 2024, 07:00 AM - 11:00 AM (PDT)
Microsoft Tech Community

AIP LogAnalytics not containing Outlook Events with latest UL Client

Copper Contributor


We do have a serious issue with AIP LogAnalytics data. Office-Outlook does not send AIP telemetry to AIP LogAnalytics workspace. Metrics we look at is the count of new assigned labels by application and by label assigned. This gives us approximately an idea of how our users apply labels. The distribution of labels assigned is an indicator of whether we have to plan an awareness campaign or just observe further. We observe the flow about every month retrospective 31d. During the past year this gave us a pretty smooth idea what's going on. We simply use a LogAnalytics Query to sum up the values required, so no magic.


By end of February we shipped the latest UL Client. Hurray,  one month later the outlook label count over all labels is not close to where it should be. Our observation showed that some clients still send telemetry data. However most, say 98% of Outlook Clients do not! 


Remove client, native office outlook experience does not send telemetry data as well. Install the older version of the client fixes the issue.


Regarding native, web and mobile clients will become an issue soon. We are rolling out MS Teams  including web and mobile access. Those label usage telemetry data is even important to us.


What is though interesting is that I can see an approx. valid count in compliance center --> activity explorer, filtered by outlook - here I see expected figures while in the Azure Portal->LogAnalytics-->Query I cannot get close this figures using similar parameters.


Now - what is the recommended approach generating such simple stats a) with the UL Client and b) cross platform? 


Or is there an issue we should be aware of?


Any hint is highly appreciated.


Kind regards



1 Reply
Well, well - further observation showed that the latest versions of UL Client of Outlook does send all AIP Events (except those grabbing attachments) as "Access".
As mentioned in the request above, an earlier version does not show this behaving. The only solution at this point is a fall-back. Ticket opened.
Another one: Excel open a csv file (*.txt) --> save as xlsx --> no label enforced even configured properly.

Will come back as soon as the issue is resolved in a next version of the UL client.

Regards Max