Dashboard issues with the "[Logs o365] Audit Dashboard" as provided by integration "Microsoft 365" version 2.1.1

[eriroley]

1. The panel size or font fort the "count" panel is poorly set (confirmed that I am at standard 100% zoom in Chrome)
   

Also, there appears to be a missing filter in at least the "Top users by authentication outcome" panel
There's no way I should have over 3,000,000 events, with only 2411 events as shown in the previous screenshot

I suggest adding the following filter for that (and all other panels in this dashboard)
data_stream.dataset:"o365.audit"
which then gives much more reasonable results

[elasticmachine]

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

[jamiehynds]

Thanks for flagging this with us @eriroley.

@chrisberkhout would you mind taking a look at this one, please?

[eriroley]

Similar workaround as in #8969 is possible - add a filter to the dashboard for data_stream.dataset: 0365.audit

[chrisberkhout]

@eriroley I opened #8983 to fix the missing filter.

The count panel font size initially looked good on my machine. It's not explicitly set in the dashboard config, so an issue there would be a general Lens visualization issue. I was able to reproduce the problem in your screenshot by changing my operating system display scaling factor from 1.0 to 2.0, as shown below.

As a workaround, adjusting your operating system display scaling settings may help. I believe the underlying issue is being addressed in elastic/kibana#154414

---

Here's normal 1.0 scaling:

And here it is at 2.0 scaling:

[eriroley]

Interesting - as you can see in this screenshot, my OS display is scaled to 100% as is my Chrome scaling, but the issue persists

[chrisberkhout]

Okay, yes, that is interesting. I wonder if there are some other related settings, like "Accessibility > Text/Font size"?

Someone describes a similar issue on Windows 11 here that went away after increasing font size then setting it back to 100%.

[eriroley]

no change after changing the font size in accessibility, and then changing it back

[eriroley]

However, after changing the display scaling to 125% and then back to 100% it now shows correctly
and yes, I am on windows 11

[chrisberkhout]

Okay, great. Thanks for all the info. Hopefully when elastic/kibana#154414 is resolved it'll work on higher settings as well.