WIP 1509-2

Author: EdB-MSFT

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

@@ -15,38 +15,58 @@ ms.reviewer: akkumari
 
 # Autoscale with multiple profiles
 
+This article explains the different profiles in autoscale and how to use them.
+
 You can have one or more profiles in your autoscale setting.
-A default profile is automatically created. The default profile isn't dependent on a schedule. Add more profiles such as a recurring profile, or a profile with a fixed date and time range.
 
-Each time the autoscale service runs, the profiles are checked in the following  order:
+There are three types of profile:
+
+* Recurring profiles. A recurring profile is valid for a specific time range and repeats on the selected days of the week.
+* Fixed date and time profiles. A profile that is valid for a specific date and time range.
+* The default profile. The default profile is created automatically and isn't dependent on a schedule. The default profile can't be deleted.
+  
+Each time the autoscale service runs, the profiles are evaluated in the following order:
+
+1. Fixed date profiles
+1. Recurring profiles
+1. Default profile
+
+If a profile's date and time conditions are met, autoscale will apply that profile's limits and rules. Only the first applicable profile is used. All other profiles are ignored until the next run. If you have a rule that you want to use at all times, include the rule in all of your profiles.
+
+:::image type="content" source="./media/autoscale-multiple-profiles/autoscale-default-recurring-profiles.png" alt-text="A screenshot showing an autoscale setting with default and recurring profile or scale condition":::
+
+The example above shows an autoscale setting with a default profile and recurring profile as follows.
+
+Default profile:
+
+* Minimum instances = 2
+* Maximum instances = 10
+* Scale out when the average request count is greater than 10
+* Scale in when the average request count is less than three
 
-1. Fixed Date profile
-1. Recurring profile
-1. Default ("Always") profile
+Recurring profile:
 
-When a profile's conditions are met, autoscale will apply that profiles limits and rules. Only the first applicable profile is applied. Any other profiles are ignored until the next run. If you always want to implement a given rule, include the rule in all profiles.
+* Minimum instances = 3
+* Maximum instances = 10
+* Scale out when CPU% exceeds 50
+* Scale in when CPU% is below 20
+* Repeat this profile every Monday, between 6 AM and 6 PM Eastern Time
 
-The example below shows an autoscale setting with a default profile as follows:
+On Monday after 6 AM, the next time the autoscale service runs, the recurring profile will be used. If the instance count is two, autoscale scales to the new minimum of three. Autoscale continues to use this profile and scales based on CPU% until Monday at 6 PM.
 
-+ Minimum instances = 2
-+ Maximum instances = 10
-+ Scale out when the average request count is greater than 10
-+ Scale in when the average request count is less than three
+At all other times scaling will be done according to the default profile, based on the number of requests.
+After 6 PM on Monday, autoscale switches to the default profile. If, for example the number of instances at the time is 12, autoscale scales in to 10, which the maximum allowed for the default profile.
 
-An additional, recurring profile set for Monday has the following settings:
+## Multiple profiles using templates and CLI
 
-+ Minimum instances = 3
-+ Maximum instances = 10
-+ Scale out when CPU% exceeds 50
-+ Scale in when CPU% is below 20
-+ Repeat this profile every Monday, between 6 AM and 6 PM Eastern Time
+When creating multiple profiles using templates and the CLI, 
 
-On Monday after 6 AM, the next time the autoscale service runs, the recurring profile will be used. If the instance count is two, autoscale scales to the new minimum of three. Until Monday at 6 PM, autoscale continues to use this profile and scales based on CPU%. At all other times scaling will be based on the number of requests and the minimum number of instances is 2.
-After 6 PM on Monday, autoscale switches back to the default profile. If, for example the number of instances at the time is 12, autoscale scales in to 10, the maximum allowed for the default profile.
+#### [ARM templates](#tab/templates)
 
-:::image type="content" source="./media/autoscale-best-practices/autoscale-best-practices-multi-profile1-small.png" alt-text="A screenshot showing an autoscale settings default profile or scale condition":::
+<!--- Content here  -->
 
-[![](./media/autoscale-best-practices/autoscale-best-practices-multi-profile1-small.png)](./media/autoscale-best-practices/autoscale-best-practices-multi-profile1.png#lightbox)
-[![A screenshot showing an autoscale settings recurring profile or scale condition](./media/autoscale-best-practices/autoscale-best-practices-multi-profile2-small.png)](./media/autoscale-best-practices/autoscale-best-practices-multi-profile2.png#lightbox).
+#### [CLI](#tab/cli)
 
+<!--- Content here  -->
 
+---