Continued work 2

Author: yelevin

articles/sentinel/hunting.md

@@ -200,7 +200,7 @@ For more information, see:
 
 ## Useful operators and functions
 
-Hunting queries are built in [Kusto Query Language (KQL)](/azure/data-explorer/kusto/query/), a powerful query language with IntelliSense language that gives you the power and flexibility you need to take hunting to the next level.
+Hunting queries are built in [Kusto Query Language (KQL)](/kusto/query/?view=microsoft-sentinel&preserve-view=true), a powerful query language with IntelliSense language that gives you the power and flexibility you need to take hunting to the next level.
 
 It's the same language used by the queries in your analytics rules and elsewhere in Microsoft Sentinel. For more information, see [Query Language Reference](/azure/azure-monitor/logs/get-started-queries).
 

articles/sentinel/hunts-custom-queries.md

@@ -75,7 +75,7 @@ Only queries that from a custom content source can be edited. Other content sour
 
 ## Related content
 
-- [KQL quick reference](/azure/data-explorer/kusto/query/kql-quick-reference?toc=%2Fazure%2Fsentinel%2FTOC.json&bc=%2Fazure%2Fsentinel%2Fbreadcrumb%2Ftoc.json)
+- [KQL quick reference](/kusto/query/kql-quick-reference?view=microsoft-sentinel&preserve-view=true&toc=%2Fazure%2Fsentinel%2FTOC.json&bc=%2Fazure%2Fsentinel%2Fbreadcrumb%2Ftoc.json)
 - [Advanced Security Information Model (ASIM) parser](normalization-about-parsers.md)
 - [Threat hunting in Microsoft Sentinel](hunting.md)
 - [Conduct end-to-end proactive threat hunting in Microsoft Sentinel](hunts.md)

articles/sentinel/identify-threats-with-entity-behavior-analytics.md

@@ -77,7 +77,7 @@ Information about **entity pages** can now be found at [Entity pages in Microsof
 
 ## Querying behavior analytics data
 
-Using [KQL](/azure/data-explorer/kusto/query/), we can query the **BehaviorAnalytics** table.
+Using [KQL](/kusto/query/?view=microsoft-sentinel&preserve-view=true), we can query the **BehaviorAnalytics** table.
 
 For example – if we want to find all the cases of a user that failed to sign in to an Azure resource, where it was the user's first attempt to connect from a given country/region, and connections from that country/region are uncommon even for the user's peers, we can use the following query: