The [Azure Search docs](https://learn.microsoft.com/en-us/azure/search/search-performance-optimization#scaling-for-slow-individual-queries) state that:

> 
> A high cardinality field consists of a facetable or filterable field that has a significant number of unique values, and as a result, consumes significant resources when computing results
> 
> 
> 

But it's not clear on whether this poor performance is limited to when the fields are specifically used in a filter/facet query, or whether it also affects performance when the field is queried against using search terms.

Can anyone with some deeper Azure Search knowledge weigh in?