Azure Stack Hub services, plans, offers, subscriptions overview
Microsoft Azure Stack Hub is a hybrid cloud platform that lets you deliver services from your datacenter. Services include virtual machines (VMs), SQL Server databases, SharePoint, Exchange, and even Azure Marketplace items. As a service provider, you can offer services to your tenants. Within a business or government agency, you can offer on-premises services to your employees.
As an Azure Stack Hub operator, you configure and deliver services by using offers, plans, and subscriptions. Offers contain one or more plans, and each plan includes one or more services, each configured with quotas. By creating plans and combining them into different offers, users can subscribe to your offers and deploy resources. This structure lets you manage:
- Which services and resources your users can access.
- The amount of resources that users can consume.
- Which regions have access to the resources.
To deliver a service, follow these high-level steps:
Plan your service offering, using:
- Foundational services, like compute, storage, networking, or Key Vault.
- Value-add services, like Event Hubs, App Service, SQL Server, or MySQL Server.
Create a plan that consists of one or more services. When creating a plan, select or create quotas that define the resource limits of each service in the plan.
Create an offer that has one or more plans. The offer can include base plans and optional add-on plans.
After you've created the offer, your users can subscribe to it to access the services and deploy resources. Users can subscribe to as many offers as they want. The following figure shows a simple example of a user who has subscribed to two offers. Each offer has a plan or two, and each plan gives them access to specific services.
You can offer Infrastructure as a Service (IaaS) services that enable your users to build an on-demand computing infrastructure, provisioned and managed from the Azure Stack Hub user portal.
You can also deploy Platform as a Service (PaaS) services for Azure Stack Hub from Microsoft and third-party providers. The PaaS services that you can deploy include, but aren't limited to:
You can also combine services to integrate and build complex solutions for different users.
To help manage your cloud capacity, you can use pre-configured quotas, or create a new quota for each service in a plan. Quotas define the upper resource limits that a user subscription can provision or consume. For example, a quota might allow a user to create up to five VMs.
It can take up to two hours for new quotas to be available in the user portal or before a changed quota is enforced.
You can set up quotas by region. For example, a plan that provides compute services for Region A could have a quota of two VMs.
In the Azure Stack Development Kit (ASDK), only one region (named local) is available.
Learn more about quota types in Azure Stack Hub.
Plans are groupings of one or more services. As an Azure Stack Hub operator, you create plans to offer to your users. In turn, your users subscribe to your offers to use the plans and services they include. When creating plans, make sure to set your quotas, define your base plans, and consider including optional add-on plans.
When creating an offer, the service administrator can include a base plan. These base plans are included by default when a user subscribes to that offer. When a user subscribes, they have access to all the resource providers specified in those base plans (with the corresponding quotas).
If an offer has multiple base plans, the combined storage capacity of the plans cannot exceed the storage quota.
Add-on plans are optional plans you add to an offer. Add-on plans aren't included by default in the subscription. Add-on plans are additional plans (with quotas) available in an offer that a subscriber can add to their subscriptions. For example, you can offer a base plan with limited resources for a trial, and an add-on plan with more substantial resources to customers who decide to adopt the service.
Offers are groups of one or more plans that you create so that users can subscribe to them. For example: Offer Alpha can contain Plan A, which provides a set of compute services, and Plan B, which provides a set of storage and network services.
When you create an offer, you must include at least one base plan, but you can also create add-on plans that users can add to their subscription.
When you're planning your offers, keep the following points in mind:
Trial offers: You use trial offers to attract new users, who can then upgrade to additional services. To create a trial offer, create a small base plan with an optional larger add-on plan. Alternatively, you can create a trial offer consisting of a small base plan, and a separate offer with a larger "pay as you go" plan.
Capacity planning: You might be concerned about users who grab large amounts of resources and clog the system for all users. To help performance, you can configure your plans with quotas to cap usage.
Delegated providers: You can grant others the ability to create offers in your environment. For example, if you're a service provider, you can delegate this ability to your resellers. Or, if you're an organization, you can delegate to other divisions/subsidiaries.
Subscriptions let users access your offers. If you're an Azure Stack Hub operator for a service provider, your users (tenants) buy your services by subscribing to your offers. If you're an Azure Stack Hub operator at an organization, your users (employees) can subscribe to the services you offer without paying.
Users create new subscriptions and get access to existing subscriptions by signing in to Azure Stack Hub. Each subscription represents an association with a single offer. The offer (and its plans and quotas) assigned to one subscription can't be shared with other subscriptions. Each resource that a user creates is associated with one subscription.
As an Azure Stack Hub operator, you can see information about tenant subscriptions, but you can't access the contents of those subscriptions unless you are explicitly added through RBAC by a tenant administrator of that subscription. This allows tenants to enforce separation of power and responsibilities between Azure Stack Hub operator and tenant spaces.
The exception to this case is a situation in which the subscription owner is unable to provide the operator with access to the subscription, which requires the administrator to take ownership of the subscription as discussed in Change the billing owner for an Azure Stack Hub user subscription.
If your Azure Stack Hub instance is disconnected and you have two different domains where users in domain 1 create subscriptions that users in domain 2 consume, some subscriptions may appear in the admin portal but not appear in the user portal. To fix this, have the users in domain 1 set the correct RBAC for the subscriptions in domain 2.
Default provider subscription
The default provider subscription is automatically created when you deploy the ASDK. This subscription can be used to manage Azure Stack Hub, deploy additional resource providers, and create plans and offers for users. For security and licensing reasons, it shouldn't be used to run customer workloads and apps. The quota of the default provider subscription can't be changed.
To learn more about creating plans, offers, and subscriptions, start with Create a plan.