Skip to main content

Subscriptions and Resource Groups

Subscriptions and Resource Groups

Overview

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

Creating Subscriptions

Administrators create subscriptions from the Subscriptions page or from relevant tenant views.

Before creating a subscription, confirm:

  1. The tenant exists.
  2. The target region is enabled and ready.
  3. The tenant is allowed to use the selected region.
  4. The user's role is allowed to create subscriptions.
  5. Required terms and conditions have been accepted when prompted.

Platform administrators can create subscriptions directly. Tenant, partner, and distributor administrators may be limited by self-provisioning settings.

Subscription Lifecycle

Depending on role, platform, and settings, subscription details can include lifecycle actions such as repair, enable, disable, delete, update usage, or platform-specific actions.

If an action is missing, check:

  • The user's role.
  • The subscription platform.
  • Whether self-provisioning is enabled for the user's role family.
  • Whether the subscription is in a state where the action is valid.

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

Subscription Grids

The Subscriptions page includes:

  • A subscriptions tab.
  • A quotas tab.
  • Region and tenant filters.
  • Scoped subscription summary rows.
  • Setup messages when no regions exist.

Users only see subscriptions in their assigned organisation scope.

Resource Groups

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

The Resource Groups tab lists Azure resource groups that are tagged for the current CMS subscription.

Default mapping tag:

CmsSubscriptionId = <CMS Subscription Id>

The platform may use a different configured tag key for the region.

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 region's Azure location and adds the CMS subscription mapping tag automatically.

Users can add extra tags, but they should not change the CMS subscription mapping tag.

Access

Resource group listing requires access to the subscription. Creating a resource group requires an administrator role in the user's permitted scope.

Tenant resource group self-service can be controlled by settings. If tenant users cannot create resource groups, ask a platform administrator to check the relevant self-service setting.

What To Check

If Azure or Azure Local usage is not appearing under the expected subscription, check that workload resource groups were created through CMS or have the correct CMS subscription mapping tag.

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