Provide Services on Azure Stack Hub
Core service concepts
Providing services means turning the stamp into a consumable cloud for tenants: plans, offers, subscriptions, quotas, and marketplace items. A plan is a group of service offerings (compute, storage, network, Key Vault, web apps, etc.) with quotas. An offer bundles one or more plans and controls base plans vs add-on plans and subscription visibility.
Know the tenant experience: users browse the user portal, subscribe to offers, and deploy via the marketplace or Azure Resource Manager templates. Marketplace syndication pulls items from Azure; disconnected systems need offline publishing.
Traps to watch
- Quotas are per-service and per-plan; changing a quota affects new allocations, and tenants may need a quota increase request.
- Delegated providers and managed offers allow a provider to manage tenant subscriptions; questions often conflate this with RBAC.
- Add-on plans require the base plan to be subscribed first.
- Marketplace items must be downloaded/syndicated before tenants can see them; they are not automatic on disconnected stamps.
- Confusing tenant RBAC (Owner/Contributor/Reader) with administrator roles in the admin portal.
Rule of thumb
When a tenant "cannot see a service," check the chain: offer → plan → service → quota → marketplace item. Any missing link hides the capability.
Worked example
A tenant needs VMs but sees no compute. Verify the offer's plan includes the compute service, the quota is greater than zero, and the VM image is published to the marketplace. Then confirm the tenant's subscription is active and has sufficient quota.