Single Node Orchestrator Deployment In Azure For v2019.10

Single Node Orchestrator Deployment / Installation in Azure for v2019.10 .

Following steps are valid for 19.10.x Orchestrator when Identity was coupled with Orchestrator. Identity has moved out of Orchestrator from 2020.4.1 version.

Single Node Orchestrator Deployment in Azure

  1. Introduction
  2. Creating the SQL database
  3. Creating the Azure WebApp
  4. Adding the connection string to WebApp and downloading the publish settings
  5. Allowing the WebApp IP in SQL firewall
  6. Getting the authentication details
  7. Installation

  1. Introduction

UiPath Orchestrator is a web application and can be installed in the Azure WebApp. An Azure WebApp needs to be created to deploy the application in the WebApp. Read the Azure App Service Installation for the detailed prerequisites.

It requires the below components:

  • Azure WebApp with Windows server
  • SQL server instance
  1. 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 favourites (Can be also found by clicking the option Create a resource and searching for SQL)


  • Click on 'Add' to create a new database

  • Provide the details requested

  • Creating the DB server: click on the 'Create a new server' and provide the required details

  • 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.
  • Go to 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.

  1. Creating the Azure WebApp
  • Go to 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

  • 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.
  • Copy the subscription ID from the overview of the WebApp and keep it handy

  1. Add the connection string (which has been created in the 2nd Step) to the 'Application settings' of the WebApp
  • Go to 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
  • Go to 'WebApp' properties-> Custom Domain and copy the IP address

  • Go to the 'database' > 'Overview;' > Set server firewall

  • Add a IP range which contains the WebApp IP

  1. Getting the authentication details
  • Register the app in 'Azure Active Directory'
  • Go to' Azure Portal' > 'Azure Active Directory' > 'App Registration'

  • Click on New App Registration

  • Provide the required details and click on Register button at bottom

  • It will register the application and create the application ID and Tenant ID, Copy and keep it handy.

  • Create a new password for login.
  • Go to the 'certificates' and secrets option under 'Manage' > 'Create a new client secret' and copy (keep it handy, this is the Azure account password)
  • Add a role in the resource group for this Ad Application.
  • Go to 'resource group' > 'Access Control' > 'Add Role Assignment'

  • Fill the details > select the Application which have been registered previously and save.

  1. Installation

The below details should be handy from above steps:

  • Subscrption ID- from Step 3
  • Application ID- from Step 6
  • Tenant ID- from Step 6
  • Azure account password- from Step 6
  • Download the script file, unblock it and extract it. Click here to follow the steps and proceed with installation.

Sample Script

  • Script execution

PS C:\WINDOWS\system32> set-executionpolicy unrestricted

  • Execution Policy Change

The execution policy helps protect from scripts that are not trusted. Changing the execution policy might expose 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

PS C:\WINDOWS\system32> cd C:\OrchInstall\UiPathOrchestrator

PS C:\OrchInstall\up201910\UiPathOrchestrator> .\Publish-Orchestrator.ps1 -action Deploy -package "C:\OrchInstall\up201910\UiPathOrchestrator\" -stopApplicationBeforePublish -azureSubscriptionId "8e34672-hafslhg-4ba0-b40e-51bab19bf0d" -azureAccountTenantId "jksdfnb153-4d17-8827-902c1f72357" -azureAccountApplicationId "6cf681f6-f8-sjfi-a995-769d525f5" -azureAccountPassword "1kjbsR3:/khgjfhkjsd]b3kcp" -resourceGroupName "Resource-Group" -appServiceName "orvik" -hostAdminPassword "123wkjhert" -defaultTenantAdminPassword "1234,gert" -verbose