fitgap

Azure Stack HCI Solution - Multi-Tenancy with Self-Service Provisioning Experience

Features
Ease of use
Ease of management
Quality of support
Affordability
Market presence
Take the quiz to check if Azure Stack HCI Solution - Multi-Tenancy with Self-Service Provisioning Experience and its alternatives fit your requirements.
Pricing from
Pay-as-you-go
Free Trial
Free version unavailable
User corporate size
Small
Medium
Large
User industry
  1. Public sector and nonprofit organizations
  2. Education and training
  3. Construction

What is Azure Stack HCI Solution - Multi-Tenancy with Self-Service Provisioning Experience

Azure Stack HCI Solution - Multi-Tenancy with Self-Service Provisioning Experience is a reference architecture and implementation pattern for delivering a multi-tenant private cloud experience on Azure Stack HCI. It targets service providers and enterprise platform teams that need tenant isolation, delegated administration, and self-service provisioning for virtualized workloads. The solution typically combines Azure Stack HCI with Azure Arc-enabled services and Azure portal-based governance to provide centralized policy, monitoring, and lifecycle management across tenants.

pros

Azure-integrated governance controls

The solution can use Azure Arc to extend Azure policy, tagging, inventory, and monitoring constructs to on-premises Azure Stack HCI resources. This supports consistent governance and reporting across hybrid environments without building a separate control plane from scratch. It also aligns with organizations already standardizing on Azure identity and management tooling.

Multi-tenant delegation model

The design focuses on tenant isolation and delegated administration so platform teams can separate responsibilities between provider and tenant operators. It can leverage Azure RBAC and resource organization patterns to scope access and reduce cross-tenant visibility. This is useful for internal business-unit tenancy or managed service scenarios where separation of duties is required.

Self-service provisioning workflows

The approach emphasizes a self-service experience for provisioning and managing workloads, typically via Azure portal experiences and automation templates. This reduces manual ticket-based provisioning for common VM and resource requests. It also enables standardization through reusable templates and policy-driven guardrails.

cons

Not a single product

This is commonly delivered as a solution pattern that depends on multiple Microsoft components and configuration choices rather than a standalone, packaged CMP. Capabilities and user experience vary based on which Azure services, automation tooling, and portal experiences are implemented. As a result, evaluation and ongoing operations require validating the specific reference implementation, not just the platform name.

Microsoft ecosystem dependency

The solution is tightly coupled to Azure Stack HCI and Azure management services, which can limit portability to non-Microsoft hypervisor stacks or alternative on-prem cloud frameworks. Organizations with heterogeneous infrastructure may need parallel tooling or custom integration for non-HCI environments. This can increase operational complexity compared with more vendor-neutral control planes.

Complexity of tenant isolation

Achieving strong multi-tenancy typically requires careful design of identity, network segmentation, resource boundaries, and automation pipelines. Misconfiguration can lead to overly permissive access or inconsistent tenant experiences. Platform teams should expect additional engineering effort for secure defaults, chargeback/showback, and lifecycle processes across tenants.

Plan & Pricing

Pricing model: Pay-as-you-go Free tier/trial: 60-day free trial after registration (Azure Local free trial). Pricing details:

  • Host service fee (Azure Local, formerly Azure Stack HCI): Public list price not published on Microsoft pricing page; the page shows the host service fee as "$-/physical core/month" and instructs customers to request a pricing quote or contact sales. Key billing metric is per physical core (billed daily while system is registered).
  • Windows Server subscription (add-on for guest licensing): $23.3/physical core/month (pay-as-you-go); $0/physical core/month with Azure Hybrid Benefit (if you exchange qualifying core licenses).
  • Azure Kubernetes Service (AKS) enabled by Azure Arc (add-on): Included with Azure Local (2402 release and later) at no extra charge. Discounts / purchasing notes: Prices may vary by agreement, region, currency conversion; customers can exchange core licenses or use Azure Hybrid Benefit to reduce/waive fees. For disconnected (fully offline) control plane pricing or custom scenarios, Microsoft instructs contacting an account representative or requesting a pricing quote. Minimum visible published price: Microsoft does not publish a public per-core host service fee on the product pricing page (listed as "$-/physical core/month").

Source: Official Microsoft Azure Local (Azure Stack HCI) pricing page (Azure docs/pricing).

Seller details

Microsoft Corporation
Redmond, Washington, United States
1975
Public
https://www.microsoft.com/
https://x.com/Microsoft
https://www.linkedin.com/company/microsoft/

Tools by Microsoft Corporation

Clipchamp
Microsoft Stream
Azure Functions
Azure App Service
Azure Command-Line Interface (CLI)
Azure Web Apps
Azure Cloud Services
Microsoft Azure Red Hat OpenShift
Visual Studio
Azure DevTest Labs
Playwright
Azure API Management
Microsoft Graph
.NET
Azure Mobile Apps
Windows App SDK
Microsoft Build of OpenJDK
Microsoft Visual Studio App Center
Azure SDK
Microsoft Power Apps

Popular categories

All categories