Using Telerik Report Server .NET from the Azure Marketplace
You may deploy Telerik Report Server .NET directly from the Microsoft Azure Marketplace. It installs the public Report Server .NET Docker images with the specified settings on a new Azure Virtual Machine. Here are links to the necessary Docker images we provide publicly:
- https://hub.docker.com/r/progressofficial/telerik-reportserver-app
- https://hub.docker.com/r/progressofficial/telerik-reportserver-agent
- https://hub.docker.com/r/progressofficial/telerik-reportserver-setup
Prerequisites
- A Microsoft Azure subscription
- A valid Telerik Report Server License
- If you would like to use a Free Let's Encrypt HTTPS Certificate, before starting to deploy the Report Server in Azure, you have to buy a domain name, create a DNS Zone, and a Public IP address. Make the A record of the DNS zone to have the value of your public IP address. The DNS Zone and the Public IP address must be in a separate Resource group, because deploying the Report Server needs to happen in an empty resource group.
Configuration Steps
Please ensure you have fulfilled all the setting fields marked with an asterisk (*) in each section below.
-
Access the Progress Telerik Report Server on the Azure Marketplace through the __Get It Now_ button. You may need to log in to your Azure account.
-
Start the deployment process from your resource group:
-
Select the
Progress ReportServer .NET (preview)
product and create a new Subscription Plan for it: -
Configure the Basics by selecting the proper Subscription/Resource Group and the preferred Region:
-
Configure the Virtual Machine section. The screenshot below shows the recommended Ubuntu OS Version, CPU Architecture, and VM size:
You may use an existing IP Address, or create a new one with the button at the bottom of the Public IP Address for the VM setting.
If you would like to use a Free Let's Encrypt HTTPS Certificate later in the HTTPS section, you can pick the Public IP address to which you have connected your Domain name as a Prerequisite.
The DNS Prefix for the public IP Address will be concatenated with the string below it to form the Report Server URL, where you will be able to access the Report Server Manager.
-
Add the License token for your Telerik Report Server product - see how to set up the Telerik Report Server License:
-
Configure the Administrator settings:
-
The Mail settings are optional. You may configure the SMTP in the Report Server configuration after the deployment.
-
The Storage section lets you provide a connection string to an external MSSQL Database. Otherwise, the default storage will be an MSSQL Express database deployed in a Docker container in the VM.
-
In HTTPS, you may choose a Free Let's Encrypt HTTPS Certificate.
If you want to use the Free Let's Encrypt HTTPS Certificate, before starting to deploy the Report Server in Azure, you have to buy a domain name, create a DNS Zone, and a Public IP address as explained in the Virtual Machine section. Enter here your domain name created in the Virtual Machine section. It will be the domain name you bought.
The Free Let's Encrypt HTTPS Certificate is expected to be renewed automatically before expiring through a cron job set up during installation.
-
The last section Review + create validates the above settings.
After the validation passes, you need to click on the
Create
button to start the deployment of your Report Server .NET. -
Wait for the deployment to finish. You will see a screen like below during the process that may take several minutes:
When all the items under the Resource are marked with green ticks, the deployment has finished successfully, and you will see the next screen:
-
Access your Report Server on the URL specified in the Virtual Machine setting:
The user who created the Virtual Machine is fully responsible for managing it.
The user can access the Virtual Machine through Secure Shell Protocol (SSH Protocol) with the credentials provided in the Virtual Machine section. In this scenario, port 22 should be opened explicitly:
-
Select the Network Settings to open the configuration page of the Virtual Machine:
-
Add the row that opens port 22 of the Virtual Machine: