In last article, I have explained what is Azure search. In this article we will quickly see how to create Azure search instance. If you have not seen my previous article, you can quickly check it at below link:
For following steps in below article, you will need access to Azure Portal. If you do not have access, then you can create free account on Azure.
Login to Azure Portal, and then follow below steps.
Create the instance
In Azure portal, click on “+ Create a resource” button. Then search for “Azure search” and it should open Azure search create panel.
Alternatively, select “Web” from the left side panel and then click on “Azure Search“. This action would open the Azure search create panel.
New Search Service Panel
Once New Search Panel is opened, you can provide below details:
This is the unique URL to identify your Azure search service. This is the service name against which the REST API calls would be issued.
This should be unique under domain name “search.windows.net” namespace. If it is unique and conforms to the naming rules, then Azure provides visual indication (green check mark on right side).
While naming, I would suggest to use below format: companyname.appname.location.environment
That way, you will be able to identify some attributes related to the Azure search service instance.
This is the Azure subscription under which the resource should be created.
Please note that if you are using Push model and indexers, Azure search service would be able to auto-detect Azure table, blob storage, SQL Azure instance, Azure cosmos DB. This auto-detection can work only if they are in the same subscription.
This is for logically organizing the Azure resources. You can either select existing group or can create new one.
This is the Azure region where the Azure search service would be deployed. It is better to keep the service nearer to your applications.
For demo purpose, you can create a free service. Otherwise you can select either Basic or Standard pricing tier. I would strongly recommend to visit the documentation for selecting the pricing tier.
Please note that every tier will have its own limits and SLA support. I have hidden their prices from the above snapshot purposefully. I would recommend to get the pricing details from MSDN pricing page as that should provide most up to date details.
I hope you have got enough details to create the Azure search service using portal. Please comment and let me know your thoughts.