# Prevent unintended default-profile gaps between autoscale schedules

> How should adjacent autoscale profiles transition without a brief return to default capacity limits?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260909-312-prevent-unintended-default-profile-gaps-between-autoscale-schedules/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-10T00:26:44+00:00
- Modified: 2026-09-10T01:40:02+00:00
- Last reviewed by DSE: 2026-09-09
- Resource type: Guide
- DSE priority: Information
- Topics: Business Continuity, Networks & Infrastructure
- Reading time: 2 minutes

## What you need to know

How should adjacent autoscale profiles transition without a brief return to default capacity limits?

## Potentially affected

Azure autoscale settings with multiple scheduled profiles.

## DSE recommendation

Review the active profile at every schedule boundary, including the default profile and the chosen deployment tool's end-time behavior.

## Article

## Source facts

Autoscale checks fixed-date profiles before recurring profiles, then the default; only the first applicable profile supplies rules and capacity limits. In the portal, explicitly adjoining end and start times can introduce a one-minute default-profile interval. Microsoft advises leaving the end time blank for contiguous profiles. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/azure-monitor/autoscale/autoscale-multiprofile).

A recurring profile without an end time is supported through the portal and ARM templates. Omitting the CLI end time instead defaults it to 23:59. PowerShell requires a separately scheduled copy of the default profile to end a recurrence. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/azure-monitor/autoscale/autoscale-multiprofile).

## Applicability

Use this review for Azure autoscale settings with multiple scheduled profiles. Distinguish a deliberately scheduled return to default from an intended direct transition between recurring profiles. Keep the authoring tool in scope because the documented behaviors differ.

## DSE recommendation

DSE recommends a boundary table listing the intended active profile immediately before and after each transition. Include its capacity limits and any fixed-date override. Review the deployed profile definitions, not only the schedule as described in a change ticket. Ask the workload owner to approve any interval governed by the default profile, even if brief.

## Verification

Rehearse an accelerated schedule on a disposable target. Observe each transition and compare it with the boundary table, especially the minute between adjacent profiles. Inspect the exported settings for unexpected default copies or end times. Retain the observed active profile and instance count without treating one rehearsal as proof of future capacity sufficiency.

## Official references

[Microsoft Learn: Autoscale with multiple profiles](https://learn.microsoft.com/en-us/azure/azure-monitor/autoscale/autoscale-multiprofile).

## Primary reference

- Name: Autoscale with multiple profiles - Azure Monitor | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/azure-monitor/autoscale/autoscale-multiprofile
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Prevent unintended default-profile gaps between autoscale schedules,” DSE Security, https://update.dsesecurity.com/updates/dse-20260909-312-prevent-unintended-default-profile-gaps-between-autoscale-schedules/
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.