Skip to main content

Subscriptions and Resource Groups

Subscriptions and Resource Groups

Overview

Subscriptions are the tenant billing and platform resource boundary. They connect a tenant to a region and platform, and they drive usage collection, billing, invoices, quota views, resource groups, and dashboard summaries.

Subscription Creation

Administrators create subscriptions through the portal or API. Tenant, partner, and distributor administrators are subject to role-specific self-provisioning settings. Platform administrators bypass delegated self-provisioning toggles, while platform readers remain read-only.

Creation validates:

  • The signed-in user's tenant, partner, or distributor scope.
  • Region readiness.
  • Region tenant access rules.
  • New subscription terms when enabled.
  • Platform-specific subscription requirements.

Subscription Lifecycle

Lifecycle actions such as repair, enable, disable, delete, and update usage are shown only when the user role and self-provisioning settings allow them. The API enforces the same checks.

Subscription deletion preserves the original display name and appends (Deleted) once.

Public Azure subscriptions are local billing mappings. Azure Stack and CloudStack subscription lifecycle actions do not apply to Public Azure billing-only mappings.

Subscription Grids

The subscriptions page includes:

  • A subscriptions tab.
  • A quotas tab.
  • Region and tenant filters.
  • Scoped region summary loading.
  • Empty states when no regions exist.

Tenant, partner, and distributor subscription grids load only scoped region summaries and do not receive platform-wide cost, capacity, or configuration-detail values.

Resource Groups

Azure and Azure Local subscription details include a Resource Groups tab. Azure Stack and CloudStack subscriptions do not.

CMS lists Azure resource groups from the Azure subscription configured for the CMS region, filtered to resource groups whose mapping tag points to the CMS subscription being viewed.

Default mapping tag:

CmsSubscriptionId = <CMS Subscription Id>

If Region.PublicAzureTagKey is configured, CMS uses that tag key instead.

Creating Resource Groups

Creating resource groups through CMS is the preferred way to prepare Azure and Azure Local workloads for billing. CMS creates the resource group in the parent region's Azure location and automatically adds the CMS subscription mapping tag.

Users can add extra tags, but cannot override the CMS mapping tag.

Security and Scoping

Resource group listing requires access to the CMS subscription. Creation requires an administrator role in the caller's CMS scope. Read-only roles can list but cannot create.

Tenant resource group self-service can be blocked through the TenantResourceGroupSelfService subscription setting. The code still reads the legacy misspelled key for compatibility.

Operational Notes

When Azure or Azure Local usage collection cannot resolve resource-to-subscription mapping from resource or resource-group tags, the records may be unmapped or routed to fallback handling depending on platform. Operators should use the Resource Groups tab to create properly tagged workload groups before deploying resources.

  • Regions and Platforms
  • Catalogue, Pricing, and Calculator
  • Usage, Billing, and Invoicing
  • Quotas
Back to top