Introduction
This page presents a web-based calculator built to estimate key metrics within an Azure Local environment. It is custom-made and designed for deployment planning, CPU and storage sizing, infrastructure cost estimation and license impact assessment.
The calculator is provided as-is and without any warranties. Its results were checked against the V2 calculators, but if you notice any inconsistencies or potential issues, I would greatly appreciate your feedback 🤗 feel free to get in touch!
This tool is intended to supplement the official Microsoft Azure Local Sizer and ODIN for Azure Local. It aims to provide deeper visibility into specific resource planning areas and to bring planning, sizing and pricing together in one place.
Azure Local Calculator V3
Azure Local Calculator is a GitHub-based repository with the source code of the calculator. V3 replaces the three separate V2 calculators (CPU, Storage and Pricing) with a single one: you pick a deployment type once and the nodes, CPU, storage and cost follow from the same inputs.
The formulas, the CPU list, the catalog node types and the rates are the ones from the V2 calculators. Rules that the V2 calculators did not cover come from Microsoft Learn and carry a source number that points to the list at the end of the calculator.
Deployment Types
| Deployment type | Planning checks | CPU sizing | Storage sizing | Cost |
|---|---|---|---|---|
| Hyperconverged, 1 to 16 nodes (includes single node) | Yes | Yes | Storage Spaces Direct | L1 |
| Rack aware cluster (1+1 to 4+4) | Yes | Yes | Storage Spaces Direct with two-way or four-way mirror | L1 |
| Hyperconverged with external SAN | Yes | Yes | Storage Spaces Direct plus SAN | L2 or OEM license |
| Disaggregated, 1 to 64 nodes | Yes | Yes | SAN only | L2 or OEM license |
| Disconnected operations | Yes | Workload cluster and management cluster | Storage Spaces Direct for both | L3 with your rate |
| Multi-rack | Yes | No | No | L2 |
| Small form factor (preview) | Yes | No | No | Hardware only |
Multi-rack and small form factor are not sized. Microsoft sells multi-rack as a fixed bill of materials and small form factor runs on a short list of supported devices, so the calculator shows the planning facts and a cost estimate for them. Microsoft does not publish the L3 price, so enter your quote in the cost step.
How to Use It
- Work out: the three switches at the top (Compute, Storage and Cost) turn parts of the calculator off. With Compute off, step 2 becomes a small cluster size form, so you can run the storage or the cost part alone.
- Deployment type: sets the node limits, the storage model and the host fee, and lists the planning checks for that type.
- Compute: sizes the physical cores in two directions, from a node count to a recommended CPU or from a CPU model to the number of nodes you need. Select a node type from the Azure Local solutions catalog to only see the CPU models that system can use.
- Storage: start from your drives or from a capacity target. External SAN and the management cluster of disconnected operations have their own inputs. The Storage Spaces Direct model is based on the Express mode with full-flash drives. It is not the most efficient setup in terms of capacity, but it works well as a first approximation. For detailed Storage Spaces Direct sizing I recommend s2d-calculator.com by Armin.
- Cost: nodes and physical cores come from step 2. Rates are read in the selected currency, without exchange rate conversion.
- Solution: a 3D view of the hardware and 3D charts of the calculations. Drag to rotate a view, double-click to reset it and hover or tap a part to see its values. With the keyboard, focus a chart with Tab and read each value with the arrow keys.
Every result recalculates as you type. The notes and disclaimers of each step are collapsed under the step, and the full overview at the end lists every calculation.
Import from ODIN
The Import from ODIN button loads a configuration exported from ODIN for Azure Local. Both the Sizer “Export JSON” file and the Designer “Export Configuration” file are supported, for every cluster type ODIN offers: Single Node, Hyperconverged, Rack Aware, Disaggregated Storage and Disconnected Operations. You can also drop the file onto the calculator. The file is read locally in your browser and is never uploaded.
One import fills in the whole calculator: deployment type, workload vCPUs including future growth, vCPU to core ratio, node count, CPU, host core reservation, capacity drives, resiliency, storage target, SAN connectivity, switch count and AVD vCPUs. A summary shows what was applied and what could not be mapped.
Prices for nodes, switches and related costs are not part of ODIN exports and must be entered manually. Tiered ODIN layouts are imported as their capacity drives only. ODIN exports have no SAN vendor, so choose it after the import.
Calculator
The type sets the node limits, the storage model and the host fee.
Virtual machines in, physical cores and nodes out.
Notes and disclaimers for compute
vCPU to physical core ratio. The ratio (overcommit) sets how many virtual CPUs share one physical core. 1:1 means no overcommit and dedicated cores. Common ratios run from 2:1 to 8:1 depending on the workload. VDI workloads typically use 4:1 to 8:1, while database or latency-sensitive workloads should stay closer to 1:1 or 2:1. Higher ratios reduce hardware cost but may impact performance under load.
Management overhead. Each Azure Local node reserves CPU cores for the host OS, Azure Arc agents, Storage Spaces Direct and cluster services. The default of 4 cores is a reasonable estimate, but the real overhead varies with the enabled features, for example AKS or the Arc Resource Bridge. See the Azure Local system requirements for specifics.
High availability (N+1). With N+1 on, the calculator reserves one full node of capacity so workloads can fail over if a single node goes down. This is the standard recommendation for production clusters. With only 1 node the reservation is switched off automatically. For rack aware clusters it still reserves one node and not a full rack.
CPU recommendations. The CPU models come from publicly available specifications and are common server-grade processors. Not all CPUs are available on all OEM platforms. Server vendors (Dell, HPE, Lenovo, Supermicro and others) each qualify a subset of processors for their platforms, and availability varies by region, server model and generation. Always verify CPU availability and compatibility with your OEM or hardware vendor before purchasing. Not all CPUs listed may be validated for Azure Local.
Node types. The node type list holds the systems shown as "Current (2026 or later)" in the Azure Local solutions catalog. The catalog publishes the CPU generation and the supported cores per socket of each system, not individual CPU models, so the models offered for a system are the ones that match its generation, one of its cores-per-socket options and the selected socket count. Where a catalog entry was incomplete, the note under the node type says which value was inferred.
Newer CPU generations. Newer generations (for example Intel Xeon 6 Granite Rapids and Sierra Forest, AMD EPYC 5th Gen Turin) typically offer better IPC, higher core counts, better power efficiency and improved virtualization features. With a newer CPU you may be able to run a higher vCPU-to-core ratio at the same or better performance per VM. Validate performance expectations with your workload profile and OEM recommendations.
Cluster types. Disaggregated clusters use external SAN storage instead of Storage Spaces Direct and support up to 64 nodes. A disconnected operations management cluster is a dedicated cluster that only hosts the local control plane appliance: production needs 3 nodes with at least 24 physical cores, 128 GB (standard) or 512 GB (datacenter) of memory, 6 or 8 data drives of at least 2 TB and a 960 GB boot drive per node. The appliance size (24 vCPUs, 78 GB) and the 20% host core reservation follow the ODIN Sizer. Only catalog systems with the Disconnected operations capability are offered for it. See dedicated management cluster for disconnected operations.
No warranty. All information in the compute step is provided "as is" with no warranties, express or implied. It does not represent official Microsoft documentation. Always verify with your hardware vendor and Microsoft licensing team for accurate sizing and configuration.
Uses the node count from step 2.
Notes and disclaimers for storage
Storage Spaces Direct. The storage step estimates capacity for Storage Spaces Direct on Azure Local with full-flash NVMe configurations. The calculations follow current best practices and deployment guidelines. Real results vary with firmware, driver versions and workload patterns. See the official Microsoft documentation for the latest information.
Redundancy. With 1 or 2 nodes, Storage Spaces Direct uses two-way mirror, which stores 2 copies of the data. With 3 or more nodes, three-way mirror becomes available and stores 3 copies across different fault domains. Dual parity needs 4 or more nodes and uses erasure coding with 2 parity stripes. On a single node, a local mirror is used across the drives of that node. Rack aware clusters use two-way mirror for 1+1 and four-way mirror from 2+2.
Dual parity warning. Dual parity deviates from the standard Azure Local configuration. It is more space efficient than mirroring but has much lower write performance and longer rebuild times after a failure. It only suits specific cases such as cold or archival data, and you should only use it if you understand the implications. The standard recommendation for Azure Local production deployments is three-way mirror.
Dual parity efficiency. The efficiency depends on the number of fault domains (nodes). With N nodes it is (N-2)/N, up to 6 data columns plus 2 parity columns, which gives 75% at 8 or more nodes.
Reserved capacity. For multi-node clusters the calculator reserves the capacity of one capacity drive per node, so there is enough unallocated space for automatic repairs after a drive failure. Single-node clusters get no reserve. Real reserve behavior may differ, see the Microsoft reserve capacity documentation.
Infrastructure overhead. About 300 GB is reserved for infrastructure volumes: Infrastructure_1 (Arc Resource Bridge and AKS images, about 250 GB), ClusterPerformanceHistory (about 20 GB) and other system overhead (about 7 GB). These values are approximate and can change with the deployment.
Volume distribution. During cloud deployment the volumes in the storage pool (SU1_Pool) are assigned automatically. The usable capacity left after the infrastructure volumes is divided equally among the UserStorage volumes, one per node. These values are approximate and subject to change.
Capacity target mode. The comparison lists the minimum drives per node that meet or exceed the target for each drive size. Sizes that would need more than 24 drives per node are marked as not feasible in standard servers.
External SAN. Azure Local 2604 or later can use Fibre Channel or iSCSI block storage from supported arrays (Dell PowerStore, Everpure FlashArray, Hitachi VSP, HPE Alletra MP 10000, Lenovo ThinkSystem DS/DM/DG and NetApp ONTAP) next to Storage Spaces Direct (hyperconverged with external storage) or instead of it (disaggregated). SAN-backed CSVs must be NTFS, ReFS isn't supported for them, and each LUN backs a single CSV. The data reduction and the free space headroom are planning assumptions, so size the array with your storage vendor. The infrastructure volume sizes on the SAN follow the ODIN Sizer. See supported SAN solutions and enable external storage on Azure Local.
Disconnected operations. The management cluster is a dedicated cluster for the local control plane. Production needs 3 nodes, each with 6 (standard) or 8 (datacenter) SSD or NVMe data drives of at least 2 TB and a 960 GB boot drive. Smaller boot drives need extra data drives for the appliance. The deployment creates a thinly provisioned 2 TB infrastructure volume, which the calculator reserves in full. See dedicated management cluster for disconnected operations.
Other storage tools. For detailed Storage Spaces Direct sizing with tiered layouts, Armin Oberneder's s2d-calculator.com goes further than this step, which models full-flash storage with a single drive type.
No warranty. All information in the storage step is provided "as is" with no warranties, express or implied. It does not represent official Microsoft documentation. Always verify with your hardware vendor and the Microsoft documentation for accurate sizing and configuration.
Nodes and physical cores come from step 2. Rates are read in the selected currency, with no exchange rate conversion.
Notes and disclaimers for cost
What the estimate includes. The cost step is for information only. It covers the infrastructure price (nodes and switches, one-time), the license price (host fee and Windows Server), the SAN system for the L2 models (array price one-time, support monthly), related costs for external services such as backup or security software, and the Azure Virtual Desktop and SQL Managed Instance usage. Real costs vary with vendor quotes, hardware configurations and licensing agreements.
Deployment models. L1 applies to cloud-connected hyperconverged deployments without external storage. L2 applies to disaggregated deployments with SAN storage (up to 64 machines), to hyperconverged deployments with external storage and to multi-rack. Both L2 cases use the 20.10 per core per month host fee. An Azure Local OEM license with external storage uses the listed 10 per core per month special rate. L3 applies to disconnected operations with a locally hosted control plane. Microsoft does not publish an L3 host fee, so the calculator needs a planning rate or an account-specific quote from you. L3 is licensed per physical core on an annual capacity term, billed monthly, and includes the cores of the dedicated management cluster that runs the control plane. That is why the management cluster nodes and cores are added and no trial is applied to the L3 host fee. See the Azure Local pricing page, the disaggregated deployment overview and the disconnected operations overview.
Currency. The fixed Azure rates are treated as amounts in the selected currency. Choosing a currency does not convert anything.
Free trial. Azure Local host fees and the Windows Server subscription are free for the first 60 days after registration. The term totals subtract two months of the eligible fees when the trial option is on.
Azure Hybrid Benefit. Azure Hybrid Benefit can waive the Azure Local host fee only for L1 cloud-connected hyperconverged deployments without external storage. It does not waive the L2 host fee, including disaggregated deployments with SAN storage, or the L3 host fee, but it can still cover Windows Server VMs. Eligible customers can exchange Windows Server Datacenter core licenses with active Software Assurance through Enterprise Agreement or CSP to waive the L1 host fee and the Windows Server subscription. See the Microsoft Product Terms (EA/CSP), the Product Terms for Windows Server and Azure Hybrid Benefit for Windows Server. The Product Terms override general documentation.
Windows Server license. By default a Windows Server guest fee of 23.30 per core per month applies, unless you waive it or enter custom pricing per node. Confirm eligibility and final costs with your licensing provider.
Related costs. The related costs are split into backup, logs and monitoring, installation, external partner management and other. Each takes a one-time and a monthly amount. The values are yours to fill in and depend on vendor quotes and service agreements.
AVD and SQL Managed Instance. AVD is estimated at 0.01 per vCPU per hour. AVD isn't among the services of disconnected operations, so it is excluded for L3. SQL Managed Instance pricing depends on the tier, the licensing model and the reservation term, and the monthly rate is spread over 730 hours. See Azure Arc data services pricing and check the official pages for current prices.
No warranty. All information is provided "as is" with no warranties, express or implied. It does not represent official Microsoft documentation. Verify your agreements, product terms and quotes for accurate pricing.
The hardware and the calculations as 3D views. Drag to turn a view, double-click to reset it, hover or tap a part for its values.
Full overview with every calculation
Sources and limits of this calculator
Numbers in superscript point to this list. Microsoft Learn pages were read on 11 October 2026. The catalog systems are the ones listed as current in the Azure Local solutions catalog on .
Import from ODIN. The import reads a Sizer "Export JSON" file or a Designer "Export Configuration" file from ODIN for Azure Local. The file is read in your browser and is not uploaded. It sets the deployment type, the node count, the workload vCPUs including future growth, the vCPU ratio, the host core reservation, the ODIN CPU, the capacity drives, the resiliency, the storage target, the SAN connectivity, the switch count and the AVD vCPUs. Designer files carry hardware and workload data only when the design was started from the Sizer. Tiered ODIN layouts are imported as their capacity drives only. Prices are not part of ODIN exports.
What is and isn't calculated. CPU, Storage Spaces Direct, SAN capacity and cost follow the V2 calculators unchanged. Multi-rack and small form factor get planning facts and a cost estimate only, because Microsoft sells the first as a fixed bill of materials and the second on a short list of devices, and neither calculator in the repository sizes them. Microsoft 365 Local is a workload that a certified partner sizes on hyperconverged or disaggregated hardware, so it has no entry of its own. The storage model is all-flash with a single drive type. PDF export is not part of this version.
N+1 and rack failures. The failover option reserves one node, as in the CPU calculator. It does not reserve a full rack for rack aware clusters.
Pricing. Host fee rates (10 for L1, 20.10 for L2, 10 with an OEM license and external storage), the Windows Server subscription (23.30 per core), AVD (0.01 per vCPU per hour) and the SQL Managed Instance table are the fixed values from the Pricing calculator. They are read as amounts in the selected currency. Confirm them against the Azure Local pricing page and your agreement before quoting.
CPU models. Not every CPU is sold on every OEM platform or validated for Azure Local. The catalog publishes CPU generations and cores per socket, so the model list per system is a match on those two values. Check availability with your hardware vendor.
No warranty. This is an unofficial tool, provided as is. It isn't Microsoft documentation and doesn't replace a vendor quote, a sizing review or the product terms.
Contributors
-
Florian Hildesheim
Contributed insights and reference values for the Storage Calculator.
LinkedIn -
Karl Wester-Ebbinghaus
Provided valuable feedback and data for the Pricing Calculator and early CPU modeling discussions.
LinkedIn
The Storage Calculator is inspired by Cosmos Darwin’s work on the S2D Calculator.
LinkedIn: Cosmos Darwin
- Cristian Schmitt Nieto
Author of the calculator and blog.
LinkedIn
General Disclaimer
-
Unofficial:
This calculator is a community-built tool and does not represent official Microsoft products or documentation. -
No Endorsement:
It is provided as reference material only and does not imply endorsement of any architectural decision. -
Provided “AS IS”:
All code and tools are provided with no warranties, either express or implied. -
No Standard Support:
This tool is not covered by any Microsoft support program. -
Use at Your Own Risk:
It is your responsibility to validate and test the results for your specific environment. -
Limitation of Liability:
Neither the author(s) nor Microsoft will be liable for any damages resulting from the use of these tools, including (but not limited to) loss of business, profits or data.