Tag Archive for: AzureSearchTool

AzureSearchTool: Suggestions, please!

06 Jul 2015
July 6, 2015

Suggestions are a killer feature for search – same applies to Azure Search!
Performance for the lookup of the possible options in combination with a large index is a key here – scale scale scale!

I released version of the AzureSearchTool today.


I added all of the possible suggestion options – it’s a different search type so it needed a while to add it to my current implementation. But as the version number indicates, I am close to catching up with the main features. Did I mention that I added search as you type? And it generates this super verbose REST Url for you, too.

As of now all of the 12 query options for suggestions are implemented:



Maybe I will change the layout for suggestions soon – most of the times this feature will be used as type ahead – see this codeplex code as example:

Video – Suggestions in Action

Watch it in action, first without fuzzy then with it:

Next version – “facet all the things”

Before I release version 1.0 I will add facets support, that’s for sure! Maybe I will change the UX to support the facets visually – I will figure that one out while I implement it. Maybe I tackle the “Test Data” tab, too.

Do you have suggestions?

If so, please leave a comment or open an issue at the AzureSearchTool github page.

AzureSearchTool – More Options, More Fun

08 Jun 2015
June 8, 2015

Today I released the next version of the AzureSearchTool (v.
If you have not read about the tool at all, please see the introduction here.

In the very first version the tool was quite simple and most of the search parameters were not handled. That has changed now:


I implemented the schema overview (actually that was not that much but looks great):

Index Schema and Statistics

Index Schema and Statistics

So now you can see what fields of what type you have – and how those fields are specified.

Below of the Schema you get the two available statistics – the count of documents you have indexed and how many storage you currently consume. Not that much to show here.


The query side was more work, but it is definitely worth it. Currently there are 16 query parameters available (see specification) and the AzureSearchTool now assists you entering them. Some of the fields should be Url-Encoded so I handled that one, too.

The picture shows a rather basic query for the token “dsds”:

All options are handled now

All query options are handled now

That query results in a nice REST url that you can copy to your application:

Create that by hand or with Postman? Rather not.

If you managed to enter invalid values in the search query parameters, the AzureSearchTool now shows the error that is returned by Azure Search:

That error is really helpful!

That error is really helpful!


I think the feature set almost doubled in this release. Next on I will work on Facets & Suggestions.

AzureSearchTool – the easiest option to query Azure Search!

04 Jun 2015
June 4, 2015

Today I released my first Open Source tool to support the development, testing, debugging of Azure Search – the AzureSearchTool.

AzureSearchTool – v.

The tool lets you connect to different indexes and assists you crafting search queries.
As a byproduct it generates a REST URL for you to use in your application or website.

With this it should be easier to develop against the Azure Search REST API – and should speed up the testing time enormously. When I started fiddling with the Azure Search API I was not aware what query options I have and how they play together (even tho the documentation is quite good!).

Download is free of charge: here


In this very early release the tool covers the following areas:

Security / Access

Provide your Azure Search Service and your API Key (currently only Admin or Secondary) work. After connecting the tool will resolve all available indexes.

The tool from now then takes care of the api-key header.


As of now, the tool will show you all available indexes. The schema / fields and types will be visible soon in the “Index” tab. If you want to change the index after you selected one, click in the menu on “Connection” and then on “Index”.

In the flyout menu you can select one of your available indexes.

In the flyout menu you can select one of your available indexes.


In the Search section of the tool you have the option to craft queries and test them against the selected index. The tool supports you to create a query that uses the important options with an easy interface (try that with Postman – not as convenient, right?).

By now $top, $skip, $filter and api-version are implemented – the rest of the options will follow soon. Maybe I add validation and some examples, too.

Once you have changed the parameters, the URL in the top will be changed so that you can use it in your application.


You need the raw JSON data that is returned by Azure Search? You want it pretty? Click on “Raw” to get the results as it is returned by Azure Search.

You want it raw? You get it RAW!

You want it raw? You get it RAW!


As you can see not all options are implemented – I released it early to get early feedback. In the near future I will implement the Search view and all the nice options you have there. Then I will add Suggestions and Facets – because they rock.

Lastly I will develop a nice view where you can upload test data according to the schema of the selected index. Maybe, but right now I doubt it, I will add support of Index operations to create and update an index – but the Azure Portal does that pretty well and the code operations are not too complex – but well, lets see.

Scoring Profiles? Index Statistics – they are on the list, too.


So you read until down here? If so, I would be happy to get some feedback from you. Something does not work? Something missing?

By continuing to use the site, you agree to the use of cookies. more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.