Reporting Services 2019 on SQL Server

You get SQL Server 2019 Reporting Services (SSRS) with a SQL Server 2019 Enterprise database engine for its report catalog, on Windows Server 2019 Datacenter as a Generation 1 VM, configured and running at first boot. Built on 17 October 2026 from Microsoft's SQL Server 2019 Enterprise marketplace image, with Windows and SQL updates applied, Microsoft Edge current and the Windows Update and firewall services left on.

Who it's for

• Teams that publish paginated reports with SQL Server 2019 Reporting Services
• Organizations that need a dedicated report server alongside existing SQL Server 2019 databases

What's included

• SQL Server 2019 Reporting Services (15.0.1105.34), with the report server database hosted on the local SQL Server 2019 Enterprise instance (15.0.4500.2)
• Windows Server 2019 Datacenter (build 17763.9376, October 2026 update KB5126651) with Microsoft Edge 155; CVE-2013-3900 certificate-padding mitigation enabled
• Windows authentication only: the administrator account you create at deployment is a SQL Server sysadmin and an SSRS System Administrator; the sa login is disabled

After deployment

• Set the administrator user name and password at deployment and allow inbound RDP (port 3389) from your own IP address only.
• Sign in over RDP and open the Reporting Services web portal in a browser on the VM itself (its Reports virtual directory); the report server web service uses the ReportServer virtual directory.
• Before exposing the portal to other machines, bind it to HTTPS with your own certificate in Report Server Configuration Manager, then open port 443 in the Windows Firewall and the network security group (NSG, the firewall rules Azure applies to the VM).

Why this image

• A fresh build checked on a deployed test VM before publishing: report server and portal answering, Windows authentication working, no build accounts or certificates left behind, and the Azure Marketplace certification rubric passed
• Email support at support@dcassociatesgroup.com and a quick-start page at www.dcassociatesgroup.com/support/

How it runs on Azure

The VM runs in your own Azure subscription and virtual network. Billing is pay-as-you-go on your Azure invoice: an hourly software charge per vCPU, the SQL Server Enterprise and Windows Server licences, plus standard Azure compute and storage. Requirement: a VM size that supports Generation 1 images.