Skip to content

Commit 5b5beb7

Browse files
committed
fixes
1 parent 2a4b7d3 commit 5b5beb7

File tree

1 file changed

+3
-4
lines changed

1 file changed

+3
-4
lines changed

articles/azure-monitor/autoscale/autoscale-multiprofile.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Autoscale with different profiles
3-
description: "Using different profiles in autoscale"
2+
title: Autoscale with multiple profiles
3+
description: "Using multiple and recurring profiles in autoscale"
44
author: EdB-MSFT
55
ms.author: edbaynash
66
ms.service: azure-monitor
@@ -13,7 +13,7 @@ ms.reviewer: akkumari
1313
# Customer intent: As a user or dev ops administrator, I want to understand how set up autoscale with more than one profile so I can scale my resources with more flexibility.
1414
---
1515

16-
# Autoscale with different profiles
16+
# Autoscale with multiple profiles
1717

1818
Scaling your resources for a particular day of the week, or a specific date and time can reduce your costs while still providing the capacity you need when you need it.
1919

@@ -29,7 +29,6 @@ There are three types of profile:
2929
* Recurring profiles. A recurring profile is valid for a specific time range and repeats for selected days of the week.
3030
* Fixed date and time profiles. A profile that is valid for a time range on a specific date.
3131

32-
3332
Each time the autoscale service runs, the profiles are evaluated in the following order:
3433

3534
1. Fixed date profiles

0 commit comments

Comments
 (0)