Search Results

The CMS for Azure Stack Hub is a management and billing platform for Azure Stack Hub that connects technical service delivery with commercial operations. It is designed for service providers, enterprises, and partners who need to operate Azure Stack Hub as a s...

The CMS is designed to support a wide range of operational and business models for organizations using Azure Stack Hub. It combines a multi-tier commercial hierarchy with flexible deployment patterns, ensuring that both service providers and enterprises can al...

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 Requ...

The CMS is deployed as a containerized service. Deployment involves preparing the database, configuring application settings, and validating connectivity to Azure Stack Hub. Prerequisites A Linux or Windows host with Docker or Kubernetes support Acc...

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). Accessing th...

The following walkthrough introduces the core concepts of the CMS by creating a simple tenant, publishing a plan, and generating usage data. Step 1: Add a Tenant Log in as an Administrator. Navigate to Administration → Tenants. Select Add Tenan...

Purpose Explains how authentication and authorization work across the hierarchy, and how the CMS enforces least-privilege access. Authentication Supports CMS credentials and federated sign-in (e.g., Microsoft Entra). Tokens are validated for issuer, audi...

Purpose This page explains the CMS hierarchy and how ownership, visibility, and billing flow across Distributors, Partners, Tenants, and Subscriptions. It also clarifies the role of platform administrators. Roles in the hierarchy Platform Administrators: ...

Purpose Defines how the CMS models chargeable items (SKUs), how prices are set (flat or tiered), how credits/discounts apply, and how this connects to commissions. Core concepts SKU: A metered service or unit that can be priced (for example: VM vCPU-hour,...

Purpose Explains how regions (stamps) are represented and how usage flows from collection to rating and billing, including offline scenarios. Regions (stamps) A Region represents a source of usage. Each Region has the endpoints/credentials required for u...

Provisioning in the CMS follows the hierarchy of Distributor → Partner → Tenant → Subscription. Each workflow ensures that commercial alignment and technical access are established at the same time. Adding a Distributor Action: Platform Admin creates a n...

Protecting CMS data is essential for both compliance and operational recovery. The key data asset is the MySQL database, along with configuration files and TLS certificates. Backup Strategy Database: Perform regular dumps or use replication to a secondar...

The CMS provides monitoring hooks and reporting functions to ensure service continuity and compliance with billing accuracy. Core Monitoring Areas Usage Processing: Track success/failure of usage collection jobs per region. Billing Runs: Monitor inv...

The CMS is designed to be white-label and flexible. Platform administrators can adjust branding and system settings to align with the service provider or enterprise identity. Branding Options Logos: Upload light and dark mode variants. Colors & Them...

The CMS is delivered as containerized services. Maintenance focuses on applying updates, securing the environment, and ensuring continuous availability. Upgrades Container Images: Pull updated images from the registry. Rolling Updates: Apply updates...

When issues occur, the CMS provides multiple layers of diagnostic tools. Effective troubleshooting combines log analysis, API checks, and data validation. Common Issues Login Failures: Often linked to misconfigured identity providers or expired federatio...

The CMS exposes a REST API that mirrors all major platform functions, allowing administrators, partners, and developers to automate operations. API Design Principles Standards-Based: JSON over HTTPS, aligned with REST conventions. Role-Aware: All ca...

CMS API API Reference Version: v1 Cloud Management Service Authentication All endpoints require a Bearer token in the Authorization header unless otherwise noted. Example: Authorization: Bearer <token> Alerts GET /api/v1/alerts Responses 200: OK POST /api/v1...

Introduction Relationship management is a critical part of administering the system. Add a Distributor PurposeRegister a new distributor as the top-level commercial entity under the platform. Permission LevelPlatform Administrator Steps Go to Adm...

Introduction This page covers day-to-day region administration. Add a Region PurposeRegister a new region so usage can be collected and processed. Permission LevelPlatform Administrator Steps Go to Administration → Regions. Select Create. ...