Skip to main content

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

Use Regions to configure the platform locations CMS manages or bills, test readiness, control tenant access, review health, and run region operations.

Supported Platforms

Platform What users should expect
Azure Stack Subscriptions, usage collection, health, catalogue, quotas, and lifecycle actions.
Azure Local Azure Local VM and disk usage, image catalogue, resource groups, and billing through CMS pricing.
Public Azure Azure cost import, resource group tag mapping, fallback subscription handling, and pass-through uplift.
CloudStack CloudStack subscriptions, offers, templates, usage, billing, and quota-style limits.

User Roles

Regions 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 is enabled and ready before creating subscriptions.

Restrict Tenant 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 available platform actions such as health refresh, usage update, or region-specific maintenance. Actions appear only when the region is configured enough for the selected platform.

Configuration Notes

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, resource 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 domain/account mapping.

Known Limitations

  • Azure Local platform action buttons should be reviewed after platform setup to confirm only relevant actions are shown.
  • Public Azure unmapped billing should be reviewed by operators until Public Azure-specific alerting is available.
  • CloudStack user synchronisation is a future operational capability.

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 configuration is complete.
  4. Whether the tenant is allowed to use the region.
  5. Whether the action applies to the selected platform.
  • Subscriptions and Resource Groups
  • Catalogue, Pricing, and Calculator
  • Usage, Billing, and Invoicing
  • Quotas
Back to top