Single Node Orchestrator Deployment in Azure

Single Node Orchestrator Deployment in Azure

Single Node Orchestrator Deployment in Azure

Introduction- UiPath orchestrator is a web application and can be installed in the Azure WebApp. Create an Azure WebApp and deploy the application in the WebApp. Go through the below link for pre-requisites-
It requires the below components-
  • Azure WebApp with windows server
  • SQL server instance

 Creating a SQL Server instance :  Follow the below steps to create the database in Azure-

  • Open the Azure Portal
  • Select the SQL database from the favorites (you can also search for this after clicking the Create a Resource)
  • Click on Add to create a new database
  • Provide the details requested
Create a new database server or use an existing one
Select an existing resource group or create a new one
Select a subscription
A valid custom database name
  • Creating the DB server- click on the Create a new server and provide the required details
These details will be used to create the DB connection string
  • Click on select, and then click on Create button to create the database
The database has been created. Now copy the connection string from the database properties-
  • Goto the database and from properties click on the Connection String then select the ADO.NET and copy the connection string
  • Provide the username and password which has setup earlier as part of creating the DB server. The connection string is ready to use.
  •   Creating the Azure WebAppGoto the Azure portal homepage and select App Services from favorites
  • Click on Add

  • Select WebApp
  • Create a new WebApp
  • Provide the required details and create the WebApp
You can use the existing plan or create a new by clicking on the arrow and following the steps in next point
It’s good to have the DB and WebApp in same RG
  • Creating a new service plan- Select the App Service plan and click on create new
  • Provide the required details and click on OK to create the service plan.
Now the WebApp has been created.
  1. Add the connection string(which has been created in the 2nd Step) to the Application settings of the WebApp
  • Goto the WebApp and select Application settings from the properties
  • Add the connection string in the WebApp as given below and save it
  1. Allowing the WebApp IP in SQL firewall
  • Goto WebApp properties-> Custom Domain and copy the IP address
  • Goto the database -> Overview-> Set server firewall
  • Add a IP range which contains the WebApp IP
  • Download the publish settings-
Goto the WebApp-> overview-> Get Publish Profile
Place it in the local machine.


  • Download the script file, unblock it and extract it. Follow the steps mentioned in the below link and proceed with installation-
Sample Script-
Script execution
PS C:\WINDOWS\system32> set-executionpolicy unrestricted
Execution Policy Change
The execution policy helps protect you from scripts that you do not trust. Changing the execution policy might expose you to the security risks described in the about_Execution_Policies help topic at
https:/ Do you want to change the execution policy?
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend  [?] Help (default is "N"): A
.\Publish-Orchestrator.ps1 -action Deploy -hostAdminPassword "pwd" -isHostPassOneTime -defaultTenantAdminPassword "pwd" -isDefaultTenantPassOn
eTime -package "C:\Users\vikash.kumar\Documents\AzureInstallation\UiPathOrchestrator\" -activitiesPackagePath "C:\Users\vikash.kumar\Documents\AzureInstallation\UiPathOrchestrator\" -publishSettingsPath
"C:\Users\vikash.kumar\Documents\AzureInstallation\UiPathOrchestrator\Orch2019.PublishSettings" -nugetRepositoryType "Composite" -storageType "FileSystem" -storageLocation "RootPath=D:\home\data\NuGet "
And the installation has been completed and the services are available for now.
Visit the next page for come common issues while installing the Orchestrator in Azure. 

Issue 1: publishSettingPath is not recognized as the name of script, cmdlet…….. or if included then verify the path is correct.
This error generally comes when there will be an extra character in the installation command or the publish setting path is not correct. Verify the same and try again.

Issue 2: Database will not be created and while browsing the website it will throw an error as “Invalid object name dbo.setting”
Root Cause-
Scenario 1. This error generally comes when there has been an issue in database migration. Please verify that the firewall rules has been set correctly and try again.

Scenario 2: The web deploy has been completed successfully but there was an error while downloading the web.config file and hence the database has not been created-
Error- Exception calling ‘DownloadFile’ with 2 arguments: “The operation has timed out”
Resolution: Please Verify the FTP account mentioned in the PublishSettings file and make sure that is accessible from the system where you are running the script. Try to access the path using FileZilla or any other tool and make sure that the path is accessible.
  • If it is accessible from the FileZilla but still the error occurs, please follow the below workaround-
Remove the lines that downloading Web.Config from FTP from the installation script ( attached Screenshot) . Instead, manually download the Web.config file from FTP and drop it in the folder where scripts are placed and Re run the script.