# Explain an autoscale scale-in decision from all active rules

> Why can one satisfied scale-in threshold produce no reduction, or fewer removed instances than expected?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260909-119-explain-an-autoscale-scale-in-decision-from-all-active-rules/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-10T00:29:57+00:00
- Modified: 2026-09-10T00:52:38+00:00
- Last reviewed by DSE: 2026-09-09
- Resource type: Explainer
- DSE priority: Information
- Topics: Business Continuity, IT
- Reading time: 2 minutes

## What you need to know

Why can one satisfied scale-in threshold produce no reduction, or fewer removed instances than expected?

## Potentially affected

Azure Monitor autoscale profiles containing multiple metric-based scale-in rules.

## DSE recommendation

Reconstruct the complete rule decision before changing a threshold that appears not to work.

## Article

## Source facts

Azure Monitor autoscale evaluates scale-in only when no scale-out rule triggers. Every scale-in rule must then trigger, and the engine chooses the result that removes the fewest instances. It also checks whether the proposed reduction would immediately trigger scale-out; this anti-flapping check can defer the reduction or reduce its size. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/azure-monitor/autoscale/autoscale-understanding-settings).

Cooldown is evaluated separately for each candidate rule, measured from the latest scale action. It is not one global waiting period copied from the rule that last acted. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/azure-monitor/autoscale/autoscale-understanding-settings).

## Applicability

Review Azure Monitor autoscale profiles containing multiple metric-based scale-in rules. Establish the active profile first, but keep profile scheduling separate from this analysis of the rules inside it.

## DSE recommendation

DSE recommends writing down each rule’s observed condition, proposed resulting capacity and cooldown eligibility for the same evaluation interval. Include any scale-out condition before attributing a missed reduction to the scale-in rule alone. Compare the most conservative permitted result with the operator’s expectation. Do not lower thresholds or delete a protective rule simply because one chart appeared to justify removing instances.

## Verification

In an approved test, exercise a case where only one reduction rule is satisfied, followed by a case where all are satisfied. Compare the resulting capacity with each rule’s proposal and check whether a reversal would follow. Preserve the rule configuration, recent scale-action time and observed outcome so the decision can be reconstructed without relying on a single metric screenshot.

## Official references

[Microsoft Learn: Understand autoscale settings](https://learn.microsoft.com/en-us/azure/azure-monitor/autoscale/autoscale-understanding-settings).

## Primary reference

- Name: Understand autoscale settings in Azure Monitor - Azure Monitor | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/azure-monitor/autoscale/autoscale-understanding-settings
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Explain an autoscale scale-in decision from all active rules,” DSE Security, https://update.dsesecurity.com/updates/dse-20260909-119-explain-an-autoscale-scale-in-decision-from-all-active-rules/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.