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 regionplatform andregion. platform,They andare theythe drivemain usageboundary collection,for usage, billing, invoices, quota views, resource groups, and dashboard summaries.

SubscriptionCreating CreationSubscriptions

Administrators create subscriptions throughfrom the portalSubscriptions page or API.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 aremay subjectbe tolimited role-specificby 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

LifecycleDepending on role, platform, and settings, subscription details can include lifecycle actions such as repair, enable, disable, delete, and update usageusage, areor shownplatform-specific onlyactions.

when

If thean useraction roleis andmissing, check:

  • The user's role.
  • The subscription platform.
  • Whether self-provisioning settingsis allowenabled them. The API enforcesfor the sameuser's checks.

    role

    Subscriptionfamily.

    • deletion preserves
  • Whether the originalsubscription displayis namein anda appendsstate (Deleted)where once.

    the action is valid.

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

Subscription Grids

The subscriptionsSubscriptions page includes:

  • A subscriptions tab.
  • A quotas tab.
  • Region and tenant filters.
  • Scoped regionsubscription summary loading.rows.
  • EmptySetup statesmessages when no regions exist.

Tenant, partner, and distributor subscription grids loadUsers only scopedsee regionsubscriptions summariesin andtheir doassigned notorganisation receive platform-wide cost, capacity, or configuration-detail values.scope.

Resource Groups

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

CMSThe Resource Groups tab lists Azure resource groups fromthat theare Azure subscription configuredtagged for the CMS region, filtered to resource groups whose mapping tag points to thecurrent CMS subscription being viewed.subscription.

Default mapping tag:

CmsSubscriptionId = <CMS Subscription Id>

IfThe Region.PublicAzureTagKeyplatform ismay configured,use CMSa usesdifferent thatconfigured tag key instead.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 parent region's Azure location and automatically adds the CMS subscription mapping tag.tag automatically.

Users can add extra tags, but cannotthey overrideshould not change the CMS subscription mapping tag.

Security and ScopingAccess

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

Tenant resource group self-service can be blockedcontrolled throughby settings. If tenant users cannot create resource groups, ask a platform administrator to check the TenantResourceGroupSelfServicerelevant subscriptionself-service setting. The code still reads the legacy misspelled key for compatibility.

OperationalWhat NotesTo Check

WhenIf Azure or Azure Local usage collectionis cannotnot resolveappearing resource-to-under the expected subscription, check that workload resource groups were created through CMS or have the correct CMS 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.tag.

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