# search

Use <mark style="color:red;">**search**</mark> when you know what are looking for, but don't know from where.

For example, I know I have a device name that starts with **THINK**, I can't remember what exact name it is and I just want to see what data do I get

{% hint style="info" %}
A faster way to filter the data that you are looking for is to \*\*\*\* use "**where".**
{% endhint %}

{% content-ref url="/pages/JqzuL0eJai7ScvfZf2zE" %}
[where](/kql/kql-quick-guide/my-favorites/where.md)
{% endcontent-ref %}

### 🔍Search everything and not case sensitive

```
search "*think*"
```

This will return all the results that contain think (not case sensitive) from all columns and all tables

![search anything and not case sensitive](/files/Fzo42Z4ayc93zolyVAkZ)

### 🔍Search matched words with case sensitive

```
search kind=case_sensitive "THINK460"
```

![Search matched words with case sensitive](/files/Sh0wGa2O3cuWNAGB8dKD)

### 🔍Search from specific tables

```
search in (IntuneDevices, UCClient) "THINK460"
```

![Search from specific tables](/files/NUK3Xh2P8eodwLz7XzHD)

### 🔍Search the value from the specified columnIntu

```
// Some code
IntuneDevices
| search DeviceName: "THINK"
```

```
```

### 🔍Search begins with and starts with

```
// Search startswith
IntuneDevices
| search * startswith "THINK" 

//Search endswith
IntuneDevices
| search * endswith "01" 
```

### 🔍Search combined logically

```
IntuneDevices
| search * endswith "01" and ("Windows" or "iOS")
```

### 🔍Search with regex

```
IntuneDevices
| search DeviceName matches regex "[A-Z]-"
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://sandyzeng.gitbook.io/kql/kql-quick-guide/my-favorites/search.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
