System Requirements

~~Deployment~~

System model

Requirements

The CMS is delivered as a .NET-based application backed by a MySQL database. It is packaged for deployment in containerized or virtualized environments and can be operated either alongside Azure Stack Hub infrastructure or on external platforms.

Software Requirements

~~Containerized~~ ~~using~~
Database: MySQL 8.0 or later

Application Runtime: .NET 8

Frontend: Blazor Server (runs as part of the API service or in a separate container)

Optional Components: Docker ~~and~~or ~~nginx~~Kubernetes ~~reverse~~for ~~proxy.~~container orchestration

~~Minimum~~

Hardware requirements

~~OS: Linux (recommended) or Windows with WSL2~~

~~CPU: 4 vCPU~~

~~Memory: 8 GB RAM~~

~~Disk: 50 GB (persistent volume for MySQL, logs, and assets)~~

~~Software: Docker Engine~~

~~Production considerations~~

~~Separate hosts or orchestrator for HA~~

~~External MySQL 8.0 with backups and monitoring~~

~~TLS certificates~~

~~SMTP relay for outbound email~~

~~Time sync (NTP) and stable DNS~~

~~Ports~~

Requirements

~~443/TCP~~
Production Deployment
- Minimum 4 vCPUs
- 16 GB RAM
- 100 GB storage (~~HTTPS~~expandable tobased ~~nginx)~~on retention of usage and billing data)

Development or Evaluation Deployment
- Minimum 2 vCPUs
- 8 GB RAM
- 50 GB storage

Network Requirements

Outbound HTTPS connectivity to Azure Stack Hub administrative endpoints

Inbound HTTPS (TCP 443) for API and portal access

Optional VPN or ExpressRoute for hybrid or private connectivity scenarios

Identity Requirements

Integration with Microsoft Entra ID or another supported identity provider

Federated authentication supported through token validation endpoints

Role-based access control (RBAC) enforced throughout the portal and API

High Availability and Recovery

The CMS can be deployed in a high-availability configuration using container clustering or database replication. Backup and recovery procedures should be established to protect the MySQL database and configuration state. For detailed operational guidance, see Backups & DR in the Operations chapter.