# Choose autoscale default capacity for a missing-metric condition

> The default count has a specific role when autoscale cannot read its resource metric.

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260917-117-choose-autoscale-default-capacity-for-a-missing-metric-condition/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-17T16:33:03+00:00
- Modified: 2026-09-17T16:42:35+00:00
- Last reviewed by DSE: 2026-09-17
- Resource type: Guide
- DSE priority: Information
- Topics: Cybersecurity, IT
- Reading time: 1 minutes

## What you need to know

The default count has a specific role when autoscale cannot read its resource metric.

## Potentially affected

Use this review when selecting or revising an autoscale setting's default capacity. Identify the resource metric and the workload expected during a monitoring interruption. Keep the default's missing-metric purpose distinct from the profile's minimum, maximum and ordinary rule thresholds.

## DSE recommendation

DSE recommends asking the service owner to justify the default against an agreed reduced-observability scenario.

## Article

## Source facts

Microsoft explains that when autoscale has a problem reading the resource metric, it increases capacity to the configured default if the current count is lower. If the current count already exceeds that default, this behavior does not scale it inward. The default is therefore a specific fallback count. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/azure-monitor/autoscale/autoscale-best-practices).

## Applicability

Use this review when selecting or revising an autoscale setting’s default capacity. Identify the resource metric and the workload expected during a monitoring interruption. Keep the default’s missing-metric purpose distinct from the profile’s minimum, maximum and ordinary rule thresholds.

## DSE recommendation

DSE recommends asking the service owner to justify the default against an agreed reduced-observability scenario. Record the expected behavior when current capacity is below the default and when it is above. Assess application readiness at that capacity using approved workload evidence, and document who handles the underlying telemetry failure.

## Verification

Review the deployed default and compare it with the approved scenario. In a controlled exercise where appropriate, observe the setting’s behavior when the metric is unavailable and compare lower- and higher-capacity cases. Restore normal collection and confirm fresh evaluations. Retain capacity observations separately from application-response evidence; a matching instance count alone does not prove acceptable service behavior.

## Official references

[Microsoft Learn: Best practices for autoscale](https://learn.microsoft.com/en-us/azure/azure-monitor/autoscale/autoscale-best-practices).

## Primary reference

- Name: Best practices for autoscale - Azure Monitor | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/azure-monitor/autoscale/autoscale-best-practices
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Choose autoscale default capacity for a missing-metric condition,” DSE Security, https://update.dsesecurity.com/updates/dse-20260917-117-choose-autoscale-default-capacity-for-a-missing-metric-condition/
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.