Configure Azure VMs for high availability

The platform identifies Azure Virtual Machines (VMs) that are not configured for high availability and recommends implementing availability zones, availability sets, or virtual machine scale sets. Failure to configure high availability leaves critical workloads vulnerable to downtime from hardware failures, maintenance events, or other disruptions, potentially impacting business continuity.

Recommendation Impact Across KPIs

KPIImpactCalculated?
Reliability:Reduces potential downtime through redundancy and fault tolerance✅
Security Compliance:No direct security impact❌
Economic:No direct economic impact calculated❌
User Experience:No direct user experience impact calculated❌
Environment:No direct environmental impact calculated❌

Score Calculation

1. Data Ingestion

  • VM Instance Names
  • Current Availability Configuration
  • Zone/Region Distribution
  • Scale Set Membership

2. Data Enrichment

  • Mapping to Availability Requirements
  • Suitable HA Configuration Options
  • Potential Downtime Risk Assessment

3. Health Score

  • Calculate the Reliability score based on potential downtime minutes
  • Score multiplier increases based on time since recommendation was loaded (0.01 per day)
  • Data sourced from DataTable-VM

Example Graph

Pie chart showing the distribution of VMs across different configuration options, highlighting the percentage of VMs in various availability states as tracked in DataTable-VM.

Business Opportunities

Product Sales Opportunity

As a provider this recommendation provides you an opportunity to generate revenue through system upgrade configurations. Each VM requiring high availability configuration represents a billable opportunity based on the system count.

Professional Services Opportunity

The recommendation provides opportunities for professional services to implement high availability configurations, including architectural planning, implementation, and testing. Additional revenue can be generated through Azure license sales and ongoing management tools.

Remediation Guidance

To resolve the recommendation the following steps are recommended:

  1. Develop a High Availability Plan
  2. Identify Critical VMs
  3. Assess Requirements
  4. Choose HA Strategy

Allocate Resources

Communicate with Stakeholders

  1. Notify IT Teams
  2. Clarify Impact

Schedule Implementation

Execute High Availability Configuration

  1. Configure Availability Sets
  2. Configure Availability Zones
  3. Set Up Scale Sets

Implement Load Balancing

Post-Configuration Monitoring & Optimization

  1. Verify VM Availability
  2. Monitor High Availability

Test Failover

Ongoing Maintenance

  1. Review VM Health
  2. Update HA Configuration
  3. Stay Updated with Best Practices

Supporting Information

Supported Data Sources

  • Azure Advisor
  • CoreStack

Recommendation Categorisation

  • Reconfigure
  • Infrastructure
  • High Availability

Supported Instances

  • Azure Virtual Machines
  • Server Workloads

Planned Instances

  • Status: In Development
  • Implementation Type: New Configuration
  • Asset Type: Server