Manage usage and billing for Azure Stack as a Cloud Service Provider
Applies to: Azure Stack integrated systems
This article walks you through registering Azure Stack as a Cloud Provider (CSP) and adding customers.
As a CSP you work with diverse customers using your Azure Stack. Each customer has a CSP subscription in Azure. You must direct usage from your Azure Stack to each user subscription.
The following figure shows the required steps to choose your shared services account, and register the Azure account with the Azure Stack account. Once registered, you can onboard your end customers:
Create a CSP or APSS subscription
Cloud Service Provider subscription types
Choose the type of shared services account that you use for Azure Stack. The types of subscriptions that can be used for registration of a multitenant Azure Stack are:
- Cloud Service Provider
- Partner Shared Services subscription
Azure Partner Shared Services
Azure Partner Shared Services (APSS) subscriptions are the preferred choice for registration when a direct CSP or a CSP distributor operates Azure Stack.
APSS subscriptions are associated with a shared-services tenant. When you register Azure Stack, you provide credentials for an account that is an owner of the subscription. The account you use to register Azure Stack can be different from the administrator account that you use for deployment. Furthermore, the two accounts do not need to belong to the same domain; you can deploy using the tenant that you already use. For example, you can use
ContosoCSP.onmicrosoft.com, then register using a different tenant; for example,
IURContosoCSP.onmicrosoft.com. You must remember to sign in using
ContosoCSP.onmicrosoft.com when you perform daily Azure Stack administration. You sign in to Azure using
IURContosoCSP.onmicrosoft.com when you need to do registration operations.
For a description of APSS subscriptions and how to create them, see Add Azure Partner Shared Services.
Cloud Service Provider (CSP) subscriptions are the preferred choice for registration when a CSP reseller or an end customer operates Azure Stack.
Register Azure Stack
Use the APSS subscription created using the information in the preceding section to register Azure Stack with Azure. For more information, see Register Azure Stack with your Azure Subscription.
Add end customer
To configure Azure Stack so that when a new tenant uses resources, their usage is reported to their Cloud Service Provider (CSP) subscription, see Add tenant for usage and billing to Azure Stack.
Charge the right subscriptions
Azure Stack uses a feature called registration. A registration is an object stored in Azure. The registration object documents which Azure subscription(s) to use to charge for a given Azure Stack. This section addresses the importance of registration.
Using registration Azure Stack can:
- Forward Azure Stack usage data to Azure Commerce and bill an Azure subscription.
- Report each customer'’s usage on a different subscription with a multitenant Azure Stack deployment. Multitenancy enables Azure Stack to support different organizations on the same Azure Stack instance.
For each Azure Stack, there is one default subscription and many tenant subscriptions. The default subscription is an Azure subscription that is charged if there is no tenant-specific subscription. It must be the first subscription to be registered. For multi-tenant usage reporting to work, the subscription must be a CSP or APSS subscription.
Then, the registration is updated with an Azure subscription for each tenant that uses Azure Stack. Tenant subscriptions must be of the CSP type, and must roll up to the partner who owns the default subscription. You cannot register someone else's customers.
When Azure Stack forwards usage information to global Azure, a service in Azure consults the registration and maps each tenant's usage to the appropriate tenant subscription. If a tenant has not been registered, that usage goes to the default subscription for the Azure Stack instance from which it originated.
Since tenant subscriptions are CSP subscriptions, their bill is sent to the CSP partner, and usage information is not visible to the end customer.
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.