The initial setup is pretty straightforward; it's relatively simple like you would expect from a cloud-based provider. 

Azure Search is a service provided by Azure. You can sign up for it on the Azure portal, and it's just a click away to get it up and running. So, the installation only takes a few seconds of your time, and it's already up and running.

Additionally, you have to set up your index to define the fields and other parameters for what you want to search on.

The solution's initial setup is straightforward. I rate the process an eight out of ten. It takes an hour or two to complete.

The initial setup was pretty smooth. We deployed the tool in phases. Initially, we did a few applications from the lower environment. It took us a couple of months.

The initial setup was quite straightforward; it was very easy.

From my experience, the setup is a little bit complex. Azure seems to be lacking somewhat in the instructions and documentation. They need better instruction for it, mainly. If it was a little bit more intuitive and simpler to install without additional instruction, they would not need better documentation.  

When I first implemented Azure Search, much of the configuration was done via the REST API. This meant I needed to interact with the Azure Search service using standard JSON requests to create my indexes, scoring profiles, and to populate the data. While usable, this method of interaction was not ideal as it required a lot of manual coding and configuration. As the product evolved, a .NET SDK was released, which greatly simplified the process by allowing me to write native C# code from within my application. Additionally, the Azure Portal was enhanced to offer more control over the creation of the indexes and their configuration. Today, the process is extremely straightforward and easily accomplishable with a variety of methods.