Regions and Platforms

Regions and Platforms

Overview

Regions aredefine thewhere subscriptions can be created, where usage can be collected, and which platform hostingintegration boundaryCMS for subscriptions, usage, health, quotas, catalogue data, and platform integrations.uses.

CMS v2 supports these platform types:

Platform	UsageUser-facing modelbehaviour
Azure Stack	CollectedUsage usageis collected and priced through CMS meterscatalogue and SKUs.pricing.
Azure Local	Generated usage from Azure Local VM and disk allocation,allocation are collected and priced through CMS.CMS catalogue and pricing.
Public Azure	Imported Azure cost recordsdata withis imported and mapped to CMS currency conversion and pass-through uplift.subscriptions.
CloudStack	Collected CloudStack usage is collected and priced through CMS offers and templates.

Region Readiness

RegionA readinessregion controlsmust whetherbe enabled and configured before users can create subscriptions or run most region operations.

When a region canis beincomplete, usedthe forportal subscription creation and operational actions. New or incomplete regions hidehides actions such as Admin Portal, Update Usage, and Refresh HealthHealth. until setup is complete or a connection test succeeds.

Delete Region remains available for incomplete regions so failedabandoned 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 visiblethe throughuser can normally access. If allowed tenants are configured, only those tenants can use the user's normal RBAC scope. If a region has one or more tenant access rows,for subscription creation and dashboardrelated health only include tenants explicitly allowed for that region after RBAC has already been applied.views.

Azure Stack

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

AzureRegion Stacksettings regionscan include:

• A Settings tab with a Use Entra Registrationregistration Services toggle.mode.
• ACertificate Secretstorage Store setting for Key Vault or encrypted database certificate storage.option.
• RegionHealth healthand handlingidentity that marks the region degraded when admin calls time out or fail to connect.checks.
• Optional region-Region-scoped usage deletion for platform administrators.cleanup.

Azure Local

Azure Local regions represent Azure Local clustersclusters. CMS can collect VM, disk, image, CPU, memory, storage, and reuseGPU-related Azureusage appfor registrationbilling.

Resource and certificateresource-group fields.

tags

connect Azure Local usageworkloads collectionback discoversto VMCMS instancessubscriptions. andCreating disksAzure Local resource groups through AzureCMS Resourcehelps Managerensure andthe Azure Arc, resolves CMScorrect subscription mapping bytag resourceis or resource group tags, and writes standard UsageData rows. Those rows then flow through pricing, billing, invoicing, and reporting.

Azure Local catalogue includes vCPU hour, memory GB hour, storage GB hour, GPU hour, and image hour meters. Image catalogue records reuse the template/pricing path so each image can be priced by image-hour.applied.

Manual Review Required: The Azure Local feature backlog says Azure Local subscription details should notbe showreviewed anto confirm platform-specific action buttons match Azure StackLocal Portal button. Confirm the current portal behaviour before publishing this as resolved.behaviour.

Public Azure

Public Azure regions collect Azure Cost Details or Consumption usage details for discovered Azure subscriptions. CMS mapsimport Azure cost rowsdata and map it to CMS subscriptions using the configured resource group tag,tags. defaulting to CmsSubscriptionId.

Unmapped or invalid Azure cost rowscosts are routed to onethe region's fallback CMS subscription perso operators can identify tagging gaps without losing billing visibility.

Public Azure region. Azure final costpricing uses CMS currency conversion first, then appliesand the configured PassThroughIncrease.

pass-through

Azure category mappings can be synced from observed billing records and applied to non-invoiced billing rows for a selected month.increase.

Implementation Gap: Public Azure-specific alert categoriesbehaviour andis close/reopenstill flowlisted as future work. Operators should review unmapped Azure billing data manually until those alerts are documented as pending. Live Cost Details compatibility against real discovered Azure subscriptions is also pending in the feature document.available.

CloudStack

CloudStack usesregions theuse CMS regiontenants, andsubscriptions, tenant model. Catalogue visibility depends on at least one CloudStack region existing. CloudStack billing and pricing use offers andoffers, templates, and subscription provisioning maps tenants to CloudStack domainsdomain/account and accounts.relationships.

Planned Behaviour: CloudStack Syncuser Accesssync is listed as afuture backlog item.work. When implemented,available, CMS usersuser access should be automaticallyreflected created underin the tenanttenant's domainCloudStack with reader or administrator access according to role.domain.

Health and Operations

Region health can be refreshed manually by platform administrators and automatically by the platform-level RegionHealththrough scheduled job.jobs. Region capacity widgets show scopedhealth and capacity and health information without exposing platform-only configuration detailsaccording to non-platformthe users.user's access.

DatabaseWhat andTo Deployment NotesCheck

TakeIf a MySQLregion backupor beforeaction applyingis region,missing, platform,check:

1. The user's role.
2. Whether the region is enabled.
3. Whether required platform settings are complete.
4. Whether the tenant access,is Azureallowed Stackto secret-store, Azure Local, Public Azure, or CloudStack scripts. The feature documents identifyuse the relevantregion.
scripts
5. Whether forthe eachaction platform.
   applies to that platform type.