Summary
Architecture selection joins workload support, connectivity, failure domains, measurable capacity, and accountable operations. Keep execution separate from management, physical cores separate from virtual allocation, and activation separate from entitlement. Approve the design only when its assumptions survive both failure analysis and support review.
You selected a deployment by capability before sizing it, traced both local and cloud dependencies, separated failover from backup and disaster recovery, and calculated usable resources in a stated failure condition. You also identified why catalog qualification, lifecycle management, licensing, and incident ownership are independent requirements.
The worked decision remains conditional: four nodes meet the example's one-unavailable-node memory envelope, but not a two-unavailable-node requirement. Neither that result nor the simplified storage calculation proves the application recovery targets. A defensible architecture preserves those limits instead of hiding them.
More info
Use these sources to validate the selected architecture and commercial conditions.
- Azure Local deployment selection and workload matrix
- Azure Local Well-Architected guidance
- Azure Local system requirements and hardware support
- Azure Local billing, deployment tiers, and payment
- Azure Hybrid Benefit eligibility for Azure Local
- Windows Server subscription and virtual-machine activation
- Extended Security Update eligibility and pricing boundaries
- Get-CimInstance reference
- Small-form-factor preview architecture
- Deployment eligibility and multi-rack preview
- Azure Local release information and servicing support
- Disaggregated architecture and scale
- Supported external storage configurations
- Azure Local VM management components
- Disconnected operations eligibility
- Storage Spaces Direct volume planning
- Azure Local host-network requirements
- Disaggregated network patterns
- Solution Builder Extension lifecycle integration