Merge pull request #285463 from EdB-MSFT/refresh-autoscale-multiple-profiles

fresheness updates

Author: prmerger-automator[bot]

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

@@ -7,7 +7,7 @@ ms.service: azure-monitor
 ms.subservice: autoscale
 ms.custom: devx-track-azurecli, devx-track-azurepowershell
 ms.topic: conceptual
-ms.date: 06/20/2023
+ms.date: 08/25/2024
 ms.reviewer: akkumari
 
 # 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.
@@ -35,18 +35,18 @@ Each time the autoscale service runs, the profiles are evaluated in the followin
 1. Recurring profiles
 1. Default profile
 
-If a profile's date and time settings match the current time, autoscale will apply that profile's rules and capacity limits. Only the first applicable profile is used.
+If a profile's date and time settings match the current time, autoscale applies that profile's rules and capacity limits. Only the first applicable profile is used.
 
-The example below shows an autoscale setting with a default profile and recurring profile.
+The following example shows an autoscale setting with a default profile and recurring profile.
 
 :::image type="content" source="./media/autoscale-multiple-profiles/autoscale-default-recurring-profiles.png" lightbox="./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.":::
 
-In the above example, on Monday after 3 AM, the recurring profile will cease to be used. If the instance count is less than 3, autoscale scales to the new minimum of three. Autoscale continues to use this profile and scales based on CPU% until Monday at 8 PM. At all other times scaling will be done according to the default profile, based on the number of requests. After 8 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.
+In the example above, on Monday after 3 AM, the recurring profile will cease to be used. If the instance count is less than 3, autoscale scales to the new minimum of three. Autoscale continues to use this profile and scales based on CPU% until Monday at 8 PM. At all other times scaling is done according to the default profile, based on the number of requests. After 8 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.
 
 ## Multiple contiguous profiles
 Autoscale transitions between profiles based on their start times. The end time for a given profile is determined by the start time of the following profile.
 
-In the portal, the end time field becomes the next start time for the default profile. You can't specify the same time for the end of one profile and the start of the next. The portal will force the end time to be one minute before the start time of the following profile. During this minute, the default profile will become active. If you don't want the default profile to become active between recurring profiles, leave the end time field empty.
+In the portal, the end time field becomes the next start time for the default profile. You can't specify the same time for the end of one profile and the start of the next. The portal forces the end time to be one minute before the start time of the following profile. During this minute, the default profile becomes active. If you don't want the default profile to become active between recurring profiles, leave the end time field empty.
 
 > [!TIP]
 > To set up multiple contiguous profiles using the portal, leave the end time empty. The current profile will stop being used when the next profile becomes active. Only specify an end time when you want to revert to the default profile. 
@@ -60,16 +60,16 @@ When creating multiple profiles using templates, the CLI, and PowerShell, follow
 
 See the autoscale section of the [ARM template resource definition](/azure/templates/microsoft.insights/autoscalesettings) for a full template reference.
 
-There is no specification in the template for end time. A profile will remain active until the next profile's start time.  
+There's no specification in the template for end time. A profile will remain active until the next profile's start time.  
 
 
 ## Add a recurring profile using ARM templates
 
-The example below shows how to create two recurring profiles. One profile for weekends from 00:01 on Saturday morning and a second Weekday profile starting on Mondays at 04:00. That means that the weekend profile will start on Saturday morning at one minute passed midnight and end on Monday morning at 04:00. The Weekday profile will start at 4am on Monday and end just after midnight on Saturday morning.
+The following example shows how to create two recurring profiles. One profile for weekends from 00:01 on Saturday morning and a second Weekday profile starting on Mondays at 04:00. That means that the weekend profile starts on Saturday morning at one minute passed midnight and end on Monday morning at 04:00. The Weekday profile will start at 4am on Monday and end just after midnight on Saturday morning.
 
 Use the following command to deploy the template:
 `az deployment group create --name VMSS1-Autoscale-607 --resource-group rg-vmss1 --template-file VMSS1-autoscale.json`
-where *VMSS1-autoscale.json* is the file containing the JSON object below.
+where *VMSS1-autoscale.json* is the file containing the following JSON object.
 
 ``` JSON
 {
@@ -85,7 +85,7 @@ where *VMSS1-autoscale.json* is the file containing the JSON object below.
 
                 "name": "VMSS1-Autoscale-607",
                 "enabled": true,
-                "targetResourceUri": "/subscriptions/abc123456-987-f6e5-d43c-9a8d8e7f6541/resourceGroups/rg-vmss1/providers/Microsoft.Compute/virtualMachineScaleSets/VMSS1",
+                "targetResourceUri": "/subscriptions/0000aaaa-11BB-cccc-dd22-eeeeee333333/resourceGroups/rg-vmss1/providers/Microsoft.Compute/virtualMachineScaleSets/VMSS1",
                 "profiles": [
                     {
                         "name": "Weekday profile",
@@ -105,7 +105,7 @@ where *VMSS1-autoscale.json* is the file containing the JSON object below.
                                 "metricTrigger": {
                                     "metricName": "Inbound Flows",
                                     "metricNamespace": "microsoft.compute/virtualmachinescalesets",
-                                    "metricResourceUri": "/subscriptions/abc123456-987-f6e5-d43c-9a8d8e7f6541/resourceGroups/rg-vmss1/providers/Microsoft.Compute/virtualMachineScaleSets/VMSS1",
+                                    "metricResourceUri": "/subscriptions/0000aaaa-11BB-cccc-dd22-eeeeee333333/resourceGroups/rg-vmss1/providers/Microsoft.Compute/virtualMachineScaleSets/VMSS1",
                                     "operator": "GreaterThan",
                                     "statistic": "Average",
                                     "threshold": 100,
@@ -126,7 +126,7 @@ where *VMSS1-autoscale.json* is the file containing the JSON object below.
                                 "metricTrigger": {
                                     "metricName": "Inbound Flows",
                                     "metricNamespace": "microsoft.compute/virtualmachinescalesets",
-                                    "metricResourceUri": "/subscriptions/abc123456-987-f6e5-d43c-9a8d8e7f6541/resourceGroups/rg-vmss1/providers/Microsoft.Compute/virtualMachineScaleSets/VMSS1",
+                                    "metricResourceUri": "/subscriptions/0000aaaa-11BB-cccc-dd22-eeeeee333333/resourceGroups/rg-vmss1/providers/Microsoft.Compute/virtualMachineScaleSets/VMSS1",
                                     "operator": "LessThan",
                                     "statistic": "Average",
                                     "threshold": 60,
@@ -202,11 +202,12 @@ The following steps show how to create a recurring autoscale profile using the C
 
 ## Add a recurring profile using CLI
 
-The example below shows how to add a recurring autoscale profile, recurring on Thursdays between 06:00 and 22:50.
+The following example shows how to add a recurring autoscale profile, recurring on Thursdays between 06:00 and 22:50.
 
 ``` azurecli
 
-export autoscaleName=vmss-autoscalesetting=002
+az account set --subscription 0000aaaa-11bb-cccc-dd22-eeeeee333333
+export autoscaleName=vmss-autoscalesetting-002
 export resourceGroupName=rg-vmss-001
 
 
@@ -267,7 +268,7 @@ az monitor autoscale rule create -g rg-vmss1--autoscale-name VMSS1-Autoscale-607
 
 PowerShell can be used to create multiple profiles in your autoscale settings.
 
-See the [PowerShell Az.Monitor Reference](/powershell/module/az.monitor/#monitor) for the full set of autoscale PowerShell commands.
+See the [PowerShell Az PowerShell module.Monitor Reference](/powershell/module/az.monitor/#monitor) for the full set of autoscale PowerShell commands.
 
 The following steps show how to create an autoscale profile using PowerShell.
 
@@ -277,13 +278,14 @@ The following steps show how to create an autoscale profile using PowerShell.
 
 ## Add a recurring profile using PowerShell
 
-The example below shows how to create default profile and a recurring autoscale profile, recurring on Wednesdays and Fridays between 09:00 and 23:00.
+The following example shows how to create default profile and a recurring autoscale profile, recurring on Wednesdays and Fridays between 09:00 and 23:00.
 The default profile uses the  `CpuIn` and `CpuOut` Rules. The recurring profile uses the `BandwidthIn` and `BandwidthOut` rules.
 
 ```azurepowershell
 
+Set-AzureSubscription -SubscriptionId "0000aaaa-11BB-cccc-dd22-eeeeee333333"
 $ResourceGroupName="rg-vmss-001"
-$TargetResourceId="/subscriptions/abc123456-987-f6e5-d43c-9a8d8e7f6541/resourceGroups/rg-vmss-001/providers/Microsoft.Compute/virtualMachineScaleSets/vmss-001"
+$TargetResourceId="/subscriptions/0000aaaa-11BB-cccc-dd22-eeeeee333333/resourceGroups/rg-vmss-001/providers/Microsoft.Compute/virtualMachineScaleSets/vmss-001"
 $ScaleSettingName="vmss-autoscalesetting=001"
 
 $CpuOut=New-AzAutoscaleScaleRuleObject `