Wednesday, December 10, 2025

Deploying Home windows Servers in an Azure Availability Set


Deploying Home windows Servers in an Azure Availability Set

This information demonstrates deploying Home windows Server an Azure Availability Set for Home windows Server IIS workloads.

An availability set logically teams digital machines throughout fault domains and replace domains inside a single Azure knowledge middle. Fault domains present bodily {hardware} isolation (separate racks, energy, and community switches), whereas replace domains guarantee Azure staggers platform upkeep, rebooting just one area at a time with 30-minute restoration home windows. VMs should be assigned to availability units throughout creation and you can not add current VMs later.

Creating the First VM

  1. Navigate to Azure Portal > Digital Machines > Create
  2. Create a brand new useful resource group (e.g., “Zava IIS”)
  3. Identify the VM (e.g., “Zava IIS 1”) and choose area (e.g., East US 2)
  4. Beneath Availability Choices, choose “Availability set” > Create New
  5. Identify the supply set and settle for defaults (2 fault domains, 2 replace domains)
  6. Configure native admin account (keep away from utilizing “Administrator”)
  7. Choose “No inbound ports” for safety
  8. Allow Azure Hybrid Profit you probably have current Home windows Server licenses
  9. Confirm Premium SSD is chosen beneath Disks (required for 99.95% SLA)
  10. Be aware the digital community identify for subsequent VMs
  11. Beneath Administration, disable automated shutdown and hotpatch
  12. Beneath Monitoring, disable boot diagnostics
  13. Assessment and create the VMAvailability-Set-Audio-Pre-avatar.txt​

Creating the Second VM

  1. Return to Digital Machines > Create
  2. Use the identical useful resource group
  3. Identify the second VM (e.g., “Zava IIS 2”)
  4. Choose the prevailing availability set created in step 4 above
  5. Match all settings from the primary VM (admin account, no inbound ports, hybrid profit, Premium SSD)
  6. Make sure the VM connects to the identical digital community as the primary VM
  7. Disable auto shutdown, hotpatch, and boot diagnostics
  8. Assessment and create

Make sure that the VMs are configured with Premium SSD to attain the very best attainable SLA of 99.999%.

In a future submit, we’ll cowl how one can configure Azure Software Gateway to load stability visitors throughout computer systems in an availability set in addition to defending towards DDoS and OWASP high 10 assaults

 

Study extra about Azure Availability Units

Related Articles

Latest Articles