Getting Started

Installation

The CMS is deployed as a containerized service. Deployment involves preparing the database, configuring application settings, and validating connectivity to Azure Stack Hub.

Prerequisites

Installation Steps

  1. Database Setup

    • Create a dedicated MySQL database (e.g., cms).

    • Apply the schema migrations provided with the installation package.

  2. Application Deployment

    • Pull the container image from the registry or build it from source.

    • Run the container with environment variables specifying database connection strings, identity provider configuration, and API settings.

    • If deploying on Kubernetes, apply the provided YAML manifests to the cluster.

  3. Initial Configuration

    • Access the CMS portal at https://<hostname>.

    • Log in with the default administrator account created during setup.

    • Update branding, system settings, and identity provider integration through the Administration menu.

  4. Connectivity Validation

    • Confirm that the CMS can reach Azure Stack Hub endpoints.

    • Test authentication through Microsoft Entra ID or the configured identity provider.

    • Verify database connectivity and confirm that initial tenants and subscriptions can be created.

Post-Installation Tasks

First Login

Once the CMS has been deployed and initial configuration is complete, administrators and users can access the portal and API. The first login process establishes identity integration and sets the foundation for role-based access control (RBAC).

image.png

Accessing the Portal

Default Roles

The CMS uses a role-based access model to control permissions. The following roles are provided by default:

First-Time Setup

On first login, the administrator should:

  1. Change the default password or confirm federated login is enforced.

  2. Configure additional administrators or delegated roles.

  3. Verify role mappings if using federated identity providers.

Quick Start Tutorial

Introduction

This page is intended to guide new operators through the steps required to onboard tenants.

Step 1: Add a Region

Note: Only Platform Administrators can onboard regions.

Step 2: Add a Distributor

Note: Only Platform Administrators can onboard distributors.

Step 3: Add a Partner

Note: Only Platform and Distributor Administrators can onboard partners.

Step 4: Add a Tenant

Note: Only Platform, Distributor and Partner Administrators can onboard tenants.

Step 5: Create a Subscription

Note: Any Administrator role can onboard a new subscription.

Step 6: Configure Users

Note: Create and scope users accordingly noting that at each level of the model (Distributors, Partners and Tenants) can manage their respective scoped users.

Step 7: Configure Pricing

Step 8: Generate Billing Records