Subscriptions and Resource Groups

Subscriptions and Resource Groups

Overview

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

Creating SubscriptionsPurpose

AdministratorsUse 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

pageorfrom

Role family	Typical subscription access
Platform administrator	Create and manage subscriptions fromacross the Subscriptionsplatform.
Platform relevantreader	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 views. 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:

confirm

1. Thethe tenant exists.
exists,
2. The targetthe region is enabled and ready.
ready,
3. Theand 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.

Manage Subscription Lifecycle

DependingOpen on role, platform, and settings,a subscription details canpage includeto lifecycleuse available actions such as repair, enable, disable, delete, update usage, or platform-specific actions.

operations.

If an action is missing, check:

• The user'savailable role.
actions
• Thedepend on role, platform, subscription platform.
state,
• Whetherand 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.settings.

Subscription

Use 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 detailssubscriptions include a Resource Groups tab. AzureUse Stackit andto CloudStack subscriptions do not.

The Resource Groups tab lists Azurecreate resource groups that are automatically tagged forto the current CMS subscription.

Default mapping tag:

CmsSubscriptionId = <CMS Subscription Id>

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

Creating Resource GroupsConfiguration

CreatingSelf-provisioning resourcesettings groupscan throughrestrict CMSdelegated issubscription thecreation preferredand waylifecycle actions. Public Azure subscriptions are billing mappings, so Azure Stack and CloudStack lifecycle actions do not apply 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.them.

What To Check

If Azurean action or Azure Local usagerecord is notmissing, appearingcheck:

under

1. The user's role and organisation scope.
2. Whether subscription self-provisioning is enabled for the expecteduser's subscription,role checkfamily.
that
3. Whether workloadthe 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 were created through CMS or havecarry the correct CMS subscription mappingtag.
tag.

Related Pages

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