A cloud-native SIEM solution that provides intelligent security analytics and threat detection across systems
Hello @Arthur Williams
Thank you for reporting this issue.
Based on your screenshot, you have already configured Log Analytics to open in KQL mode by default. Therefore, the behavior you are experiencing is not expected when opening a new Log Analytics session.
Microsoft documentation confirms that the default query mode can be configured through Log Analytics settings.
However, there are a few things worth checking to identify why the setting is not being respected.
- Check whether the issue is specific to Microsoft Sentinel.
Navigate directly to:
Azure Portal > Log Analytics workspaces > Your workspace > Logs
Verify whether Log Analytics opens in KQL mode.
Next, open Logs through Microsoft Sentinel and compare the behavior.
If the issue occurs only when accessing Logs through Sentinel, this may indicate an issue with how the portal initializes the Log Analytics experience.
- Check browser session persistence.
Microsoft Log Analytics includes an autosave feature that stores the current query session state in the browser's local storage.
This includes the selected query mode, tabs, query scope, and time range.
The saved state is maintained per browser, device, and resource for up to 30 days of inactivity.
Consequently, an existing session saved in Simple mode could potentially be restored even when KQL is configured as the default.
Try opening Log Analytics in a private browser session and verify whether KQL mode is selected automatically.
- Verify whether the issue affects specific navigation paths.
There has been another community report describing similar behavior when opening Log Analytics through Microsoft Sentinel alert links, even though KQL mode was already configured as the default.
This suggests the behavior may be associated with particular navigation paths rather than the default preference itself.
However, I could not confirm an officially acknowledged Microsoft product issue or a published fix.
- Recommended next steps.
If KQL mode remains selected in your settings but Log Analytics consistently opens in Simple mode, I recommend submitting feedback through the Azure portal or opening a Microsoft support request.
Include the browser version, affected workspace, navigation path, and screenshots demonstrating the configured default and the actual behavior.
Related community discussion:
In summary, your configuration appears correct. The next step is to determine whether an existing browser session is being restored or whether Microsoft Sentinel is overriding the configured preference during navigation.
I hope this helps! If my answer helps resolve your question, please consider marking it as "Accepted Answer" so other community members experiencing similar behavior can benefit from it.