Originally reported by ZDNet (August 2020). This article summarizes and contextualizes that reporting for a DevOps engineering audience.
What Was Azure Stack ‘Fiji’?
According to reporting by ZDNet in August 2020, Microsoft was working on a new hybrid cloud product internally codenamed Azure Stack ‘Fiji’. The goal: give customers a rack of Microsoft-supplied servers, installed on-premises or in a colocation facility, but fully managed through the Azure public cloud — much like Amazon’s AWS Outposts model.
If accurate, Fiji would represent a significant evolution in Microsoft’s hybrid strategy, moving away from partner-delivered appliances toward Microsoft-owned and Microsoft-managed hardware infrastructure delivered directly to customers.
The Competitive Context: AWS Outposts and Google Anthos
Microsoft was actually an early mover in hybrid cloud, beginning to sell Azure Stack in July 2017. However, competitor offerings that followed raised the bar:
- AWS Outposts — Made generally available in December 2019, Outposts extends AWS infrastructure, APIs, and services directly into customer datacenters or colocation facilities. AWS positions it as a fully managed service for workloads requiring low latency, local data processing, or local data storage.
- Google Cloud Anthos — A managed application platform that runs on-premises (on Google-provided or customer hardware) and across multiple clouds, with centralized management from Google Cloud.
Azure Stack Fiji was reportedly aimed squarely at matching the AWS Outposts model: rack-scale hardware supplied by the cloud vendor, managed entirely through the provider’s public cloud fabric rather than by the customer’s own operations team.
How Fiji Would Differ from Existing Azure Stack Products
At the time of the report, Microsoft’s hybrid portfolio already included several distinct products. Understanding where Fiji would fit requires knowing the landscape:
| Product | Description |
|---|---|
| Azure Stack Hub | An “Azure-consistent private cloud” delivered as an appliance on certified hardware from Microsoft partners. Customers manage it themselves. |
| Azure Stack Edge | A cloud-managed edge appliance for local compute and AI inferencing at the edge. |
| Azure Stack HCI | A hyperconverged infrastructure solution for running virtualized workloads on validated hardware. |
| Azure Edge Zones | An ultra-low-latency extension of Azure for use cases like 5G and real-time applications. |
| Azure Stack ‘Fiji’ (rumored) | Microsoft-supplied and Microsoft-managed hardware racks installed at customer sites, managed via Azure public cloud (reportedly via Azure Arc). |
The key distinction for Fiji would be who manages the hardware. Azure Stack Hub relies on partner-certified hardware and places operational responsibility on the customer. Fiji, like AWS Outposts, would shift that management burden back to the cloud provider.
The Role of Azure Arc
The ZDNet report speculated that Fiji’s management plane would be Azure Arc, Microsoft’s control-plane service for managing resources across on-premises, multi-cloud, and edge environments from a single Azure portal. Arc already allows operators to project Kubernetes clusters, servers, and data services running outside Azure into Azure Resource Manager for unified governance, policy enforcement, and monitoring.
Using Arc as the management fabric for Fiji-class hardware would be a logical extension — giving enterprises a consistent operational experience whether their workloads run in an Azure region or in their own datacenter on Microsoft-owned infrastructure.
Engineering Challenges Microsoft Would Need to Solve
The ZDNet report noted that delivering a product like Fiji is technically non-trivial. Microsoft would need to address:
- Service architecture changes — Azure services built to run at global-region scale must be adapted to run on a much smaller hardware footprint inside a customer facility.
- Security model adjustments — Hardware sitting in a third-party datacenter requires a revised trust boundary, hardware attestation approach, and physical security model compared to hardware inside Microsoft’s own facilities.
- Hardware configuration and supply chain — Microsoft would need to manage logistics, racking, cabling, and lifecycle operations for hardware it owns but that lives on customer premises at scale.
- Connectivity requirements — Fiji instances would need reliable, low-latency connectivity back to Azure for management plane operations, similar to the connectivity requirements AWS imposes on Outposts deployments.
Microsoft’s Official Response
When ZDNet asked Microsoft for comment on the Fiji project, a spokesperson responded that “Microsoft has nothing to share.” No further public confirmation or denial was offered at the time of the original report.
Why This Matters for DevOps and Platform Engineers
For teams evaluating hybrid cloud architecture, the direction signaled by projects like Fiji has practical implications:
- Reduced operational overhead — If the cloud provider manages the hardware, your team focuses on workloads and configuration, not firmware updates, drive replacements, or capacity planning at the hardware layer.
- Consistent APIs — Running on the same hardware and software stack as the public cloud means the same SDKs, CLI tools, and IaC templates (ARM, Bicep, Terraform) apply without significant modification.
- Data residency and latency — Regulated industries or latency-sensitive applications can keep data on-premises while still consuming managed cloud services and tooling.
- Hybrid GitOps workflows — Azure Arc-managed infrastructure enables GitOps-style deployment and policy enforcement across both cloud and on-premises environments from a single control plane.
Current Status
This reporting dates from August 2020. Since then, Microsoft has continued to evolve Azure Arc and the broader Azure Stack portfolio. Whether the internal ‘Fiji’ project shipped under that name, was folded into another product, or was cancelled is not confirmed in the original source. Readers should consult current Microsoft documentation and announcements for the latest on Azure’s hybrid offerings.