Skip to main content

Install Solr as an Azure App Service

After Sitecore 9.0.2, Solr is a supported search technology for Sitecore Azure PAAS deployments. In this article, we will install SOLR service 8.4.0 in Azure App Service for Sitecore 10.

1. Create Azure App Service

Login to Azure and create Azure App service.

Make sure Runtime stack should be Java.

2. Download Solr

Download Solr 8.4.0 from

Extract the files and add the below web.config file in the Solr package.

<?xml version="1.0" encoding="UTF-8"?>




     <add  name="httpPlatformHandler"




           resourceType="Unspecified" />


   <httpPlatform processPath="%HOME%\site\wwwroot\bin\solr.cmd"

       arguments="start -p %HTTP_PLATFORM_PORT%"







3. Deployment

You can use FTP to copy the local Solr files to the web root of the App Service. 

Go to Deployment Center and copy the FTPS endpoint, Username & Password.

Then you can use any FTP tool such as FileZilla to copy the local Solr files to /site/wwwroot folder of App service.

Once all the files will be copied, restart the App Service.

Browse the App Service URL, you will see the Solr Dashboard & you can use this Solr in Sitecore instances for indexing


  1. Its not working. even after following all steps i still see the default start page!

    1. Please share the error message. Try to navigate this url "App Service URL"/solr

  2. Really helpful. Thank you so much.

  3. Hi Ashish, how you will deal with "all indexes are locked on disk" as it is very common issue now with Solr as Azure app service

  4. This blog post is a plagiarism of Dan Cruickshank's post. No additional value added, and no reference given to Dan Cruickshank.

  5. Thanks I follow the above step and able to host Solr on window app service, Thanks to share .

  6. You've shared some excellent material. I'm grateful for this post custom erp solutions


Post a Comment

Thanks for your comment. In case of any concerns, please contact me at

Popular posts from this blog

Comparison between Azure Application Gateway V1 and V2

Microsoft has announced new version of Azure Application Gateway and its Web Application Firewall module (WAF). In this article, we will discuss about the enhancements and new highlights that are available in the new SKUs i.e. Standard_v2 and WAF_v2. Enhancements and new features: Scalability: It allows you to perform scaling of the number of instances on the traffic. Static VIP: The VIP assigned to the Application Gateway can be static which will not change over its lifecycle. Header Rewrite: It allows you to add, remove or update HTTP request and response headers on application gateway. Zone redundancy: It enables application gateway to survive zonal failures which allows increasing the resilience of applications. Improved Performance: Improvement in performance during the provisioning and during the configuration update activities. Cost: V2 SKU may work out to be overall cheaper for you relative to V1 SKU. For more information, refer Microsoft prici

Difference between Azure Front Door Service and Traffic Manager

Azure Front Door Service is Microsoft’s highly available and scalable web application acceleration platform and global HTTP(s) load balancer. Azure Front Door Service supports Dynamic Site Acceleration (DSA), SSL offloading and end to end SSL, Web Application Firewall, cookie-based session affinity, URL path-based routing, free certificates and multiple domain management. In this article, I will compare Azure Front Door to Azure Traffic Manager in terms of performance and functionality. Similarity: Azure Front Door service can be compared to Azure Traffic Manager in a way that this also provides global HTTP load balancing to distribute traffic across different Azure regions, cloud providers or even with your on-premises. Both AFD & Traffic Manager support: Multi-geo redundancy: If one region goes down, traffic routes to the closest region without any intervention. Closest region routing: Traffic is automatically routed to the closest region. Differences: Azu

Export BACPAC file of SQL database

When you need to create an archive of an Azure SQL database, you can export the database schema and data to a BACPAC file. A BACPAC file can be stored in Azure blob storage or in local storage in an on-premises location and later imported back into Azure SQL Database or into a SQL Server on-premises installation. Let's learn some of the ways to export BACPAC file. Export BACPAC using Azure Portal Open your SQL Database and select Export. Fill the parameters as shown below. Select your storage account container & enter your SQL Server admin login. To check the status of your database export. Open your SQL Database server containing the database being exported. Go to Settings and then click Import/Export history Export BACPAC using SSMS Login Azure SQL Database by SSMS. Right-click the database -> Tasks -> Export Data-tier Application Save the .bacpac file into local disk. Export BACPAC using SQLPackage There is a command line tool that you can also choose to

Azure Machine Learning public preview announcement //Build, May 2021

Azure service updates Azure Machine Learning public preview announcement //Build, May 2021 New feature: Prebuilt Docker images for Inferencing, now in public preview. Click here for more information.