Azure Search Query causes a bad response 400 when it contains an apostrophe
The solution was simple, an apostrophe can be escaped simply by putting another one behind it. So in my example changing the string from "Revit's" to "Revit''s" did the trick.RFC 3986 encoding technique doesn't encode some characters including the apostrophe.