Course contentsShow
← Cloud and Infrastructure
Lesson 322 of 2,9896. Auto ScalingFree lesson

VMSS Scaling Policies and Rules

Configuring metric-based and schedule-based autoscale rules in Azure Monitor.

VMSS Scaling Policies and Rules

What you'll learn: How to configure automatic scaling rules for Azure Virtual Machine Scale Sets using performance metrics and time schedules.

The Core Idea

Now that you understand VMSS fundamentals, you need a way to tell Azure when and how to scale your instances up or down. Azure Monitor provides two primary approaches:

Metric-based scaling adjusts capacity based on real-time performance data (like CPU usage, memory, or network traffic). When your CPU exceeds 75% for 5 minutes, add 2 instances. When it drops below 25%, remove 1 instance.

Schedule-based scaling adjusts capacity at predetermined times. If you know traffic spikes every weekday at 9 AM, you can proactively scale from 2 to 10 instances at 8:55 AM, then back down at 6 PM.

How It Works

Think of metric-based rules like a thermostat: "If temperature (CPU) > 75°F, turn on AC (add instances)." Schedule-based rules are like a programmable timer: "Every Monday at 8 AM, set temperature to 68°F (scale to 10 instances)."

You configure these in Azure Monitor Autoscale, specifying:

  • Condition: Which metric to watch (CPU percentage, HTTP queue length, custom metrics)
  • Threshold: The trigger value (> 70%)
  • Duration: How long the condition must persist (5 minutes)
  • Action: How many instances to add/remove (scale out by 2, scale in by 1)
  • Cooldown: Wait time between scaling actions to prevent flapping

You can combine both types: use schedules for predictable patterns and metrics for unexpected load spikes.

Key Takeaway: VMSS scaling policies let you automate capacity changes using metric-based rules (reactive to current load) and schedule-based rules (proactive for known patterns), ensuring your application scales efficiently through Azure Monitor.