Regions and Platforms

Regions and Platforms

Overview

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

Purpose

CMSUse v2Regions supportsto theseconfigure the platform types:locations CMS manages or bills, test readiness, control tenant access, review health, and run region operations.

Supported Platforms

Platform	User-facingWhat behaviourusers should expect
Azure Stack	UsageSubscriptions, isusage collectedcollection, health, catalogue, quotas, and pricedlifecycle through CMS catalogue and pricing.actions.
Azure Local	Azure Local VM and disk allocationusage, areimage collectedcatalogue, resource groups, and pricedbilling through CMS catalogue and pricing.
Public Azure	Azure cost dataimport, isresource importedgroup tag mapping, fallback subscription handling, and mappedpass-through to CMS subscriptions.uplift.
CloudStack	CloudStack usagesubscriptions, isoffers, collectedtemplates, usage, billing, and pricedquota-style through CMS offers and templates.limits.

RegionUser ReadinessRoles

ARegions are primarily managed by platform administrators. Platform readers can review platform information where permitted. Non-platform users see region-related information only where it is needed for dashboards, subscriptions, calculator options, or billing visibility.

Key Workflows

Prepare a Region

1. Open Regions.
2. Create or edit a region.
3. Select the platform.
4. Enter required platform configuration.
5. Save the region.
6. Run the available connection or health checks.
7. Confirm the region must beis enabled and configuredready before userscreating cansubscriptions.
create

subscriptions

Restrict orTenant Access

1. Open the region details.
2. Select Tenant Access.
3. Add allowed tenants when the region should be restricted.
4. Leave the list empty when all role-visible tenants may use the region.

Run Region Operations

Use region details to run mostavailable region operations.

When a region is incomplete, the portal hidesplatform 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,update, catalogueor region-specific maintenance. Actions appear only when the region is configured enough for the selected platform.

Configuration Notes

actions.

Region

settings

Platform	Important configuration
Azure Stack	Provider connection, identity registration mode, certificate storage, catalogue, quotas, and health.
Azure Local	Azure connection, region location, cluster details, image sync, quotaresource group tagging, and usage collection.
Public Azure	Azure connection, resource group tag key, currency, fallback subscription, and pass-through pricing.
CloudStack	CloudStack endpoint, zone/account configuration, offers, templates, and subscriptiondomain/account lifecyclemapping.

can

Known include:

Limitations

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

Azure Local

Azure Local regionsplatform representaction 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 detailsbuttons should be reviewed after platform setup to confirm platform-specificonly actionrelevant buttonsactions matchare Azureshown. Local behaviour.

Public Azure

Public Azure regionsunmapped importbilling Azureshould costbe datareviewed and map it to CMS subscriptions using resource group tags. Unmapped or invalid costs are routed to the region's fallback subscription soby operators can identify tagging gaps without losing billing visibility.

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

Implementation Gap:until Public Azure-specific alert behaviouralerting is stillavailable.

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 syncsynchronisation is listed asa future work.operational Whencapability.

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:

1. The user's role.
2. Whether the region is enabled.
3. Whether required platform settingsconfiguration areis complete.
4. Whether the tenant is allowed to use the region.
5. Whether the action applies to thatthe platformselected type.platform.

Related Pages

• Subscriptions and Resource Groups
• Catalogue, Pricing, and Calculator
• Usage, Billing, and Invoicing
• Quotas