Subscriptions and Resource Groups

Subscriptions and Resource Groups

Overview

Subscriptions connect tenants to platform regions. They are the main boundary for usage, billing, invoices, quotas, resource groups, and dashboard summaries.

Purpose

Use Subscriptions to create cloud subscription records, review lifecycle state, run available platform actions, manage quotas, and prepare Azure or Azure Local resource groups for billing.

User Roles

Role family Typical subscription access
Platform administrator Create and manage subscriptions across the platform.
Platform reader View subscription information.
Distributor administrator Manage subscriptions inside distributor scope where enabled.
Partner administrator Manage subscriptions inside partner scope where enabled.
Tenant administrator Manage tenant subscriptions where enabled.
Read-only users View scoped subscription data.

Key Workflows

Create a Subscription

  1. Open Subscriptions.
  2. Choose New Subscription.
  3. Select the tenant.
  4. Select the platform and region.
  5. Complete any platform-specific fields.
  6. Accept required terms when prompted.
  7. Review and create the subscription.

Before creating a subscription, confirm the tenant exists, the region is enabled and ready, and the tenant is allowed to use the region.

Manage Subscription Lifecycle

Open a subscription details page to use available actions such as repair, enable, disable, delete, update usage, or platform-specific operations. The available actions depend on role, platform, subscription state, and self-provisioning settings.

Use Resource Groups

Azure and Azure Local subscriptions include a Resource Groups tab. Use it to create resource groups that are automatically tagged to the CMS subscription.

Default mapping tag:

CmsSubscriptionId = <CMS Subscription Id>

The region may use a different configured tag key.

Configuration

Self-provisioning settings can restrict delegated subscription creation and lifecycle actions. Public Azure subscriptions are billing mappings, so Azure Stack and CloudStack lifecycle actions do not apply to them.

What To Check

If an action or record is missing, check:

  1. The user's role and organisation scope.
  2. Whether subscription self-provisioning is enabled for the user's role family.
  3. Whether the region is enabled and ready.
  4. Whether the tenant is allowed to use the region.
  5. Whether the action applies to the subscription platform and state.
  6. Whether resource groups carry the correct CMS subscription tag.
Revision #3
Created 21 June 2026 12:17:26 by Documentation Agent
Updated 21 June 2026 12:36:22 by Documentation Agent