Azure Search supports a subset of the OData expression syntax for $filter and $orderby expressions.
Logical operators (and, or, not).
Comparison expressions (
eq, ne, gt, lt, ge, le). String comparisons are case-sensitive.
Constants of the supported EDM types (see Supported data types (Azure Search) for a list of supported types). Constants of collection types are not supported.
References to field names. Only
filterablefields can be used in filter expressions.
anywith no parameters. This tests whether a field of type
Collection(Edm.String)contains any elements.
allwith limited lambda expression support.
any/allare supported on fields of type
anycan only be used with simple equality expressions, and
allcan only be used with simple inequality expressions. Simple expressions consist of a comparison between a single field and a literal value, e.g.
Title eq 'Magna Carta'.
geo.distancefunction returns the distance in kilometers between two points, one being a field and one being a constant passed as part of the filter. The
geo.intersectsfunction returns true if a given point is within a given polygon, where the point is a field and the polygon is specified as a constant passed as part of the filter.
The polygon is a two-dimensional surface stored as a sequence of points defining a bounding ring (see the example below). The polygon needs to be closed, meaning the first and last point sets must be the same. Points in a polygon must be in counterclockwise order.
geo.distancereturns distance in kilometers in Azure Search. This differs from other services that support OData geospatial operations, which typically return distances in meters.
For the result of the
geo.distance function only the
lt, le, gt, ge operators are supported. Operators
ne cannot be used.
Geospatial queries and polygons spanning the 180th meridian
For many geospatial query libraries formulating a query that includes the 180th meridian (near the dateline) is either off-limits or requires a workaround, such as splitting the polygon into two, one on either side of the meridian.
In Azure Search, geospatial queries that include 180-degree longitude will work as expected if the query shape is rectangular and your coordinates align to a grid layout along longitude and latitude (for example,
geo.intersects(location, geography'POLYGON((179 65,179 66,-179 66,-179 65,179 65))'). Otherwise, for non-rectangular or unaligned shapes, consider the split polygon approach.
Functions (except the distance and intersects geospatial functions)
any/allwith arbitrary lambda expressions
There are limits to the size and complexity of filter expressions that you can send to Azure Search. The limits are based roughly on the number of clauses in your filter expression. A good rule of thumb is that if you have hundreds of clauses, you are at risk of running into the limit. We recommend designing your application in such a way that it does not generate filters of unbounded size.
The $orderby parameter accepts a comma-separated list of up to 32 expressions of the form
sort-criteria [asc|desc]. The sort criteria can either be the name of a
sortable field or a call to the
geo.distance function. You can use either
desc to explicitly specify the sort order. The default order is ascending.
If multiple documents have the same sort criteria (for example, if you sort by a numeric
rating field and three documents all have a rating of 4), ties will be broken by document score in descending order. When document scores are the same (for example, when there is no full-text search query specified in the request), then the relative ordering of the tied documents is indeterminate.
The syntax for
geo.distance in $orderby is the same as it is in $filter. When using
geo.distance in $orderby, the field to which it applies must be of type
Edm.GeographyPoint and it must also be
For more details on OData expressions and URI conventions, see OData.org.
Find all hotels with a base rate less than $100 that are rated at or above 4:
$filter=baseRate lt 100.0 and rating ge 4
Find all hotels other than "Roach Motel" that have been renovated since 2010:
$filter=hotelName ne 'Roach Motel' and lastRenovationDate ge 2010-01-01T00:00:00Z
Find all hotels with a base rate less than $200 that have been renovated since 2012, with a datetime literal that includes time zone information for Pacific Standard Time:
$filter=baseRate lt 200 and lastRenovationDate ge 2012-01-01T00:00:00-08:00
Find all hotels that have parking included and do not allow smoking:
$filter=parkingIncluded and not smokingAllowed
- OR -
$filter=parkingIncluded eq true and smokingAllowed eq false
Find all hotels that are Luxury or include parking and have a rating of 5:
$filter=(category eq 'Luxury' or parkingIncluded eq true) and rating eq 5
Find all hotels with the tag "wifi" (where each hotel has tags stored in a Collection(Edm.String) field):
$filter=tags/any(t: t eq 'wifi')
Find all hotels without the tag "motel":
$filter=tags/all(t: t ne 'motel')
Find all hotels with any tags:
Find all hotels within 10 kilometers of a given reference point (where location is a field of type Edm.GeographyPoint):
$filter=geo.distance(location, geography'POINT(-122.131577 47.678581)') le 10
Find all hotels within a given viewport described as a polygon (where location is a field of type Edm.GeographyPoint). Note that the polygon is closed (the first and last point sets must be the same) and the points must be listed in counterclockwise order.
$filter=geo.intersects(location, geography'POLYGON((-122.031577 47.578581, -122.031577 47.678581, -122.131577 47.678581, -122.031577 47.578581))')
Find all hotels that either have no value in "description" field, or that value is explicitly set to null:
$filter=description eq null
Sort hotels ascending by base rate:
Sort hotels descending by rating, then ascending by base rate (remember that ascending is the default):
Sort hotels descending by rating, then ascending by distance from the given co-ordinates:
$orderby=rating desc,geo.distance(location, geography'POINT(-122.131577 47.678581)') asc