Regions and Platforms

Overview

Regions define where subscriptions can be created, where usage can be collected, and which platform integration CMS uses.

CMS v2 supports these platform types:

Platform	User-facing behaviour
Azure Stack	Usage is collected and priced through CMS catalogue and pricing.
Azure Local	VM and disk allocation are collected and priced through CMS catalogue and pricing.
Public Azure	Azure cost data is imported and mapped to CMS subscriptions.
CloudStack	CloudStack usage is collected and priced through CMS offers and templates.

Region Readiness

A region must be enabled and configured before users can create subscriptions or run most region operations.

When a region is incomplete, the portal hides actions such as Admin Portal, Update Usage, and Refresh Health. Delete remains available so abandoned setup can be cleaned up.

Tenant Access

Platform administrators can restrict a region to an allowed tenant list from the Tenant Access tab.

If a region has no tenant access rows, it is available to all tenants the user can normally access. If allowed tenants are configured, only those tenants can use the region for subscription creation and related health views.

Azure Stack

Azure Stack regions support provider credentials, readiness checks, health refresh, usage collection, catalogue sync, quota templates, and subscription lifecycle actions.

Region settings can include:

Entra registration mode.
Certificate storage option.
Health and identity checks.
Region-scoped usage cleanup.

Azure Local

Azure Local regions represent Azure Local clusters. CMS can collect VM, disk, image, CPU, memory, storage, and GPU-related usage for billing.

Resource and resource-group tags connect Azure Local workloads back to CMS subscriptions. Creating Azure Local resource groups through CMS helps ensure the correct subscription mapping tag is applied.

Manual Review Required: Azure Local subscription details should be reviewed to confirm platform-specific action buttons match Azure Local behaviour.

Public Azure

Public Azure regions import Azure cost data and map it to CMS subscriptions using resource group tags. Unmapped or invalid costs are routed to the region's fallback subscription so operators can identify tagging gaps without losing billing visibility.

Public Azure pricing uses currency conversion and the configured pass-through increase.

Implementation Gap: Public Azure-specific alert behaviour is still listed as future work. Operators should review unmapped Azure billing data manually until those alerts are available.

CloudStack

CloudStack regions use CMS tenants, subscriptions, offers, templates, and CloudStack domain/account relationships.

Planned Behaviour: CloudStack user sync is listed as future work. When available, CMS user access should be reflected in the tenant's CloudStack domain.

Health and Operations

Region health can be refreshed manually by platform administrators and automatically through scheduled jobs. Region capacity widgets show health and capacity information according to the user's access.

What To Check

If a region or action is missing, check:

The user's role.
Whether the region is enabled.
Whether required platform settings are complete.
Whether the tenant is allowed to use the region.
Whether the action applies to that platform type.