bold-reports/bold-reports-azure

Purpose and Scope

This is a versioned Azure Resource Manager (ARM) template repository for deploying Bold Reports On-Premise Edition to Azure App Service. It contains deployment artifacts, not application source code. Each release directory preserves templates aligned to a Bold Reports package version.

Deployment Entry Points

Consumers select a release-specific ARM JSON template and deploy it through Azure’s ARM deployment workflow. Current templates are under armtemplates/latest/, while pinned historical releases are under paths such as armtemplates/v10.1.11/ and armtemplates/v1.1.14/.

App Service Deployment Stack

The primary deployment path provisions/configures a Bold Reports Azure Web App:

• armtemplates/latest/BoldReportsAppServiceTemplate.json

• armtemplates/v10.1.11/BoldReportsAppServiceTemplate.json

• legacy armtemplates/v1.2.7/RS-UMS-AppServiceTemplate.json

These templates are the infrastructure boundary between the deployer’s Azure subscription/resource group and the Bold Reports runtime hosted by Azure App Service.

Storage Topologies

Two persistence choices are represented:

• Azure Blob Storage, using templates such as armtemplates/latest/AzureBlobStorage-BoldReports.json and armtemplates/v10.1.11/AzureBlobStorage-BoldReports.json.

• File storage, available in older Report Server releases, e.g. armtemplates/v1.2.7/FileStorage-ReportServer.json.

The selected template determines where deployed Bold Reports/Report Server state and report-related assets are persisted.

Versioned Product Evolution

Template naming reflects product evolution from Report Server/UMS to Bold Reports. Early releases provide AzureBlobStorage-ReportServer.json and RS-UMS-AppServiceTemplate.json; later versions standardize on AzureBlobStorage-BoldReports.json and BoldReportsAppServiceTemplate.json. Release-specific directories, including patch variants such as armtemplates/v6.1.45_E13672/, are compatibility contracts and should not be treated as interchangeable.

Primary Control Flow

1. Operator chooses latest or a pinned version directory.

2. Operator chooses an App Service-only or Blob Storage-backed template.

3. ARM submits the selected JSON definition to Azure.

4. Azure provisions/configures App Service and, when selected, Azure Blob Storage.

5. The resulting App Service hosts the Bold Reports On-Premise runtime, which provides report design, management, deployment, and sharing.

Runtime and External Boundaries

The material runtime is Bold Reports On-Premise Edition hosted in Azure App Service. Azure ARM is the provisioning control plane; Azure App Service is the application host; Azure Blob Storage is an optional durable storage service. Although the product supports Windows, Linux, Docker, and Kubernetes generally, this repository specifically packages the Azure App Service ARM deployment route.