|
| 1 | +--- |
| 2 | +title: Azure Marketplace Deployment |
| 3 | +page_title: Report Server for .NET in Azure Marketplace |
| 4 | +description: "Learn how to deploy the Telerik Report Server for .NET directly from the Microsoft Azure Marketplace." |
| 5 | +slug: azure-marketplace-integration |
| 6 | +tags: report,server,dotnet,azure,marketplace |
| 7 | +published: true |
| 8 | +position: 125 |
| 9 | +--- |
| 10 | + |
| 11 | +# Using Telerik Report Server .NET from the Azure Marketplace |
| 12 | + |
| 13 | +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: |
| 14 | + |
| 15 | +* https://hub.docker.com/r/progressofficial/telerik-reportserver-app |
| 16 | +* https://hub.docker.com/r/progressofficial/telerik-reportserver-agent |
| 17 | +* https://hub.docker.com/r/progressofficial/telerik-reportserver-setup |
| 18 | + |
| 19 | +## Prerequisites |
| 20 | + |
| 21 | +* A Microsoft Azure subscription |
| 22 | +* A valid [Telerik Report Server License]({%slug license-key%}) |
| 23 | +* 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. |
| 24 | + |
| 25 | +## Configuration Steps |
| 26 | + |
| 27 | +>note Please ensure you have fulfilled all the setting fields marked with an asterisk (*) in each section below. |
| 28 | +
|
| 29 | +1. [Log in to your Azure account](https://portal.azure.com/#home) and go to the Marketplace |
| 30 | +1. Start the deployment process from your resource group: |
| 31 | + |
| 32 | +  |
| 33 | + |
| 34 | +1. Select the `Progress ReportServer .NET (preview)` product and create a new Subscription Plan for it: |
| 35 | + |
| 36 | +  |
| 37 | + |
| 38 | +1. Configure the __Basics__ by selecting the proper _Subscription_/_Resource Group_ and the preferred _Region_: |
| 39 | + |
| 40 | +  |
| 41 | + |
| 42 | +1. Configure the __Virtual Machine__ section. The screenshot below shows the recommended _Ubuntu OS Version_, _CPU Architecture_, and _VM size_: |
| 43 | + |
| 44 | +  |
| 45 | + |
| 46 | + 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. |
| 47 | + |
| 48 | + 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. |
| 49 | + |
| 50 | + >important 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. |
| 51 | + |
| 52 | +1. Add the __License__ token for your Telerik Report Server product - see how to set up the [Telerik Report Server License]({%slug license-key%}): |
| 53 | + |
| 54 | +  |
| 55 | + |
| 56 | +1. Configure the __Administrator__ settings: |
| 57 | + |
| 58 | +  |
| 59 | + |
| 60 | +1. The __Mail__ settings are optional. You may configure the SMTP in the Report Server configuration after the deployment. |
| 61 | + |
| 62 | +  |
| 63 | + |
| 64 | +1. 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. |
| 65 | + |
| 66 | +  |
| 67 | + |
| 68 | +1. In __HTTPS__, you may choose a Free Let's Encrypt HTTPS Certificate. |
| 69 | + |
| 70 | + 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. |
| 71 | + |
| 72 | +  |
| 73 | + |
| 74 | + The HTTPS Certificate is expected to be renewed automatically before expiring through a _cron job_ set up during installation. |
| 75 | + |
| 76 | +1. The last section __Review + create__ validates the above settings. |
| 77 | + |
| 78 | +  |
| 79 | + |
| 80 | + After the validation passes, you need to click on the `Create` button to start the deployment of your Report Server .NET. |
| 81 | + |
| 82 | +1. Wait for the deployment to finish. You will see a screen like below during the process that may take several minutes: |
| 83 | + |
| 84 | +  |
| 85 | + |
| 86 | + When all the items under the _Resource_ are marked with green ticks, the deployment has finished successfully, and you will see the next screen: |
| 87 | + |
| 88 | +  |
| 89 | + |
| 90 | +1. Access your Report Server on the URL specified in the _Virtual Machine_ setting: |
| 91 | + |
| 92 | +  |
| 93 | + |
| 94 | +>note The user who created the Virtual Machine is fully responsible for managing it. The user can access it through [Secure Shell Protocol (SSH Protocol)](https://en.wikipedia.org/wiki/Secure_Shell) with the credentials provided in the _Virtual Machine_ section. |
| 95 | +
|
| 96 | +## See Also |
| 97 | + |
| 98 | +* [Report Server for .NET Introduction]({%slug coming-soon%}) |
| 99 | +* [Telerik Report Server License]({%slug license-key%}) |
| 100 | +* [Telerik Report Server License Agreement](https://www.telerik.com/purchase/license-agreement/report-server) |
0 commit comments