updated files and added new docs

Author: naman-msft

scenarios/azure-compute-docs/articles/virtual-machine-scale-sets/tutorial-autoscale-cli.md

@@ -37,7 +37,7 @@ export MY_RESOURCE_GROUP_NAME="myResourceGroup$RANDOM_SUFFIX"
 az group create --name $MY_RESOURCE_GROUP_NAME --location $REGION
 ```
 
-Now create a Virtual Machine Scale Set with [az vmss create](/cli/azure/vmss). The following example creates a scale set with an instance count of 2, generates SSH keys if they don't exist, and uses a valid image "Ubuntu2204".
+Now create a Virtual Machine Scale Set with [az vmss create](/cli/azure/vmss). The following example creates a scale set with an instance count of 2, generates SSH keys if they don't exist, and uses a valid image *Ubuntu2204*.
 
 ```azurecli-interactive
 export MY_SCALE_SET_NAME="myScaleSet$RANDOM_SUFFIX"
@@ -92,7 +92,7 @@ az monitor autoscale rule create \
 ```
 
 ## Simulate CPU load on scale set
-To test the autoscale rules, you need to simulate sustained CPU load on the VM instances in the scale set. In this minimalist approach, we avoid installing additional packages by using the built-in "yes" command to generate CPU load. The following command starts 3 background processes that continuously output data to /dev/null for 60 seconds and then terminates them.
+To test the autoscale rules, you need to simulate sustained CPU load on the VM instances in the scale set. In this minimalist approach, we avoid installing additional packages by using the built-in `yes` command to generate CPU load. The following command starts 3 background processes that continuously output data to `/dev/null` for 60 seconds and then terminates them.
 
 ```bash
 for i in {1..3}; do
@@ -105,7 +105,7 @@ pkill yes
 This command simulates CPU load without introducing package installation errors.
 
 ## Monitor the active autoscale rules
-To monitor the number of VM instances in your scale set, use the watch command. It may take up to 5 minutes for the autoscale rules to begin the scale-out process in response to the CPU load. However, once it happens, you can exit watch with Ctrl-c. 
+To monitor the number of VM instances in your scale set, use the `watch` command. It may take up to 5 minutes for the autoscale rules to begin the scale-out process in response to the CPU load. However, once it happens, you can exit watch with *CTRL + C* keys. 
 
 By then, the scale set will automatically increase the number of VM instances to meet the demand. The following command shows the list of VM instances in the scale set:
 

scenarios/azure-compute-docs/articles/virtual-machine-scale-sets/tutorial-modify-scale-sets-cli.md

@@ -13,10 +13,10 @@ ms.custom: mimckitt, devx-track-azurecli, linux-related-content, innovation-engi
 # Tutorial: Modify a Virtual Machine Scale Set using Azure CLI
 Throughout the lifecycle of your applications, you may need to modify or update your Virtual Machine Scale Set. These updates may include how to update the configuration of the scale set, or change the application configuration. This article describes how to modify an existing scale set using the Azure CLI.
 
-Below, we declare environment variables that will be used throughout this document. A random suffix is appended to resource names that need to be unique for each deployment. The REGION is set to WestUS2.
+Below, we declare environment variables that will be used throughout this document. A random suffix is appended to resource names that need to be unique for each deployment. The `REGION` is set to *WestUS2*.
 
 ```bash
-export RANDOM_SUFFIX=$(openssl rand -hex 3)
+export RANDOM_SUFFIX=adcc95
 export MY_RESOURCE_GROUP_NAME="myResourceGroup$RANDOM_SUFFIX"
 export SCALE_SET_NAME="myScaleSet$RANDOM_SUFFIX"
 export NEW_INSTANCE_NAME="myNewInstance$RANDOM_SUFFIX"
@@ -46,7 +46,7 @@ az group create --name $MY_RESOURCE_GROUP_NAME --location $REGION
 ```
 
 ## Create the Virtual Machine Scale Set
-To ensure that subsequent update and query commands have a valid resource to work on, create a Virtual Machine Scale Set. In this step, we deploy a basic scale set using a valid image ("Ubuntu2204") and set the instance count to 5 so that instance-specific updates can target an existing instance ID.
+To ensure that subsequent update and query commands have a valid resource to work on, create a Virtual Machine Scale Set. In this step, we deploy a basic scale set using a valid image (*Ubuntu2204*) and set the instance count to 5 so that instance-specific updates can target an existing instance ID.
 
 ```azurecli-interactive
 az vmss create \
@@ -164,7 +164,7 @@ The exact presentation of the output depends on the options you provide to the c
 }
 ```
 
-You can use [az vmss update](/cli/azure/vmss#az-vmss-update) to update various properties of your scale set. For example, updating your license type or a VM's instance protection policy. Note that the allowed license type value is "RHEL_BYOS" rather than "Windows_Server."
+You can use [az vmss update](/cli/azure/vmss#az-vmss-update) to update various properties of your scale set. For example, updating your license type or a VM's instance protection policy. Note that the allowed license type value is *RHEL_BYOS* rather than *Windows_Server*.
 
 ```azurecli-interactive
 az vmss update --name $SCALE_SET_NAME --resource-group $MY_RESOURCE_GROUP_NAME --license-type RHEL_BYOS
@@ -185,7 +185,7 @@ az vmss update \
   --protect-from-scale-in
 ```
 
-Additionally, if you previously deployed the scale set with the az vmss create command, you can run the az vmss create command again to update the scale set. Make sure that all properties in the az vmss create command are the same as before, except for the properties that you wish to modify. For example, below we're increasing the instance count to five.
+Additionally, if you previously deployed the scale set with the `az vmss create` command, you can run the `az vmss create` command again to update the scale set. Make sure that all properties in the `az vmss create` command are the same as before, except for the properties that you wish to modify. For example, below we're increasing the instance count to five.
 
 > [!IMPORTANT]
 >Starting November 2023, VM scale sets created using PowerShell and Azure CLI will default to Flexible Orchestration Mode if no orchestration mode is specified. For more information about this change and what actions you should take, go to [Breaking Change for VMSS PowerShell/CLI Customers - Microsoft Community Hub](https://techcommunity.microsoft.com/t5/azure-compute-blog/breaking-change-for-vmss-powershell-cli-customers/ba-p/3818295)
@@ -199,8 +199,7 @@ az vmss create \
   --admin-username azureuser \
   --generate-ssh-keys \
   --instance-count 5 \
-  --os-disk-size-gb 64 \
-  --admin-username azureuser
+  --os-disk-size-gb 64
 ```
 
 ## Updating individual VM instances in a scale set
@@ -288,8 +287,7 @@ These properties describe the configuration of a VM instance within a scale set,
 You can perform updates to individual VM instances in a scale set just like you would a standalone VM. For example, attaching a new data disk to instance 1:
 
 ```azurecli-interactive
-export DISK_NAME="disk_name$RANDOM_SUFFIX"
-az vm disk attach --resource-group $MY_RESOURCE_GROUP_NAME --vm-name $INSTANCE_NAME --name $DISK_NAME --new
+az vm disk attach --resource-group $MY_RESOURCE_GROUP_NAME --vm-name $INSTANCE_NAME --name disk_name1 --new
 ```
 
 Running [az vm show](/cli/azure/vm#az-vm-show) again, we now will see that the VM instance has the new disk attached.
@@ -305,11 +303,11 @@ Running [az vm show](/cli/azure/vm#az-vm-show) again, we now will see that the V
         "diskSizeGb": 1023,
         "lun": 0,
         "managedDisk": {
-          "id": "/subscriptions/xxxxx/resourceGroups/myResourceGroupxxx/providers/Microsoft.Compute/disks/disk_namexxxx",
+          "id": "/subscriptions/xxxxx/resourceGroups/myResourceGroupxxx/providers/Microsoft.Compute/disks/disk_name1",
           "resourceGroup": "myResourceGroupxxx",
           "storageAccountType": "Premium_LRS"
         },
-        "name": "disk_namexxxx",
+        "name": "disk_name1",
         "toBeDetached": false
       }
     ]
@@ -321,7 +319,7 @@ Running [az vm show](/cli/azure/vm#az-vm-show) again, we now will see that the V
 There are times where you might want to add a new VM to your scale set but want different configuration options than those listed in the scale set model. VMs can be added to a scale set during creation by using the [az vm create](/cli/azure/vmss#az-vmss-create) command and specifying the scale set name you want the instance added to.
 
 ```azurecli-interactive
-az vm create --name $NEW_INSTANCE_NAME --resource-group $MY_RESOURCE_GROUP_NAME --vmss $SCALE_SET_NAME --image RHELRaw8LVMGen2 --admin-username azureuser
+az vm create --name $NEW_INSTANCE_NAME --resource-group $MY_RESOURCE_GROUP_NAME --vmss $SCALE_SET_NAME --image RHELRaw8LVMGen2
 ```
 
 ```output

scenarios/azure-compute-docs/articles/virtual-machines/disks-enable-performance.md

@@ -6,7 +6,7 @@ ms.service: azure-disk-storage
 ms.topic: how-to
 ms.date: 12/09/2024
 ms.author: rogarana
-ms.custom: devx-track-azurepowershell, innovation-engine
+ms.custom: devx-track-azurepowershell
 ---
 
 # Preview - Increase IOPS and throughput limits for Azure Premium SSDs and Standard SSD/HDDs
@@ -29,7 +29,7 @@ Either use the Azure Cloud Shell to run your commands or install a version of th
 
 ## Enable performance plus
 
-You need to create a new disk to use performance plus. The following scripts show how to create a disk with performance plus enabled and, if desired, attach it to a VM. The commands have been organized into self-contained steps for reliability.
+You need to create a new disk to use performance plus. The following script creates a disk that has performance plus enabled and attach it to a VM:
 
 # [Azure CLI](#tab/azure-cli)
 
@@ -190,142 +190,52 @@ Results:
 
 # [Azure PowerShell](#tab/azure-powershell)
 
-### Create a resource group
-
-This step creates a resource group with a unique name.
+You need to create a new disk to use performance plus. The following script creates a disk that has performance plus enabled and attach it to a VM:
 
 ```azurepowershell
-$RANDOM_SUFFIX = (New-Guid).Guid.Substring(0,6)
-$myRG = "PerfPlusRG$RANDOM_SUFFIX"
-$region = "WestUS2"
-New-AzResourceGroup -Name $myRG -Location $region
-```
-
-Results:
-
-<!-- expected_similarity=0.3 -->
-```JSON
-{
-  "ResourceGroupName": "PerfPlusRGxxx",
-  "Location": "WestUS2",
-  "ProvisioningState": "Succeeded"
-}
-```
-
-### Create a new disk with performance plus enabled
+$myRG=yourResourceGroupName
+$myDisk=yourDiskName
+$myVM=yourVMName
+$region=desiredRegion
+# Valid values are Premium_LRS, Premium_ZRS, StandardSSD_LRS, StandardSSD_ZRS, or Standard_LRS
+$sku=desiredSKU
+#Size must be 513 or larger
+$size=513
+$lun=desiredLun
+
+Set-AzContext -SubscriptionName <yourSubscriptionName> 
 
-This step creates a new disk with performance plus enabled using a valid SKU value.
-
-```azurepowershell
-$myDisk = "PerfPlusDisk$RANDOM_SUFFIX"
-$sku = "Premium_LRS"
-$size = 513
 $diskConfig = New-AzDiskConfig -Location $region -CreateOption Empty -DiskSizeGB $size -SkuName $sku -PerformancePlus $true 
-$dataDisk = New-AzDisk -ResourceGroupName $myRG -DiskName $myDisk -Disk $diskConfig
-```
 
-Results:
-
-<!-- expected_similarity=0.3 -->
-```JSON
-{
-  "ResourceGroup": "PerfPlusRGxxx",
-  "Name": "PerfPlusDiskxxx",
-  "Location": "WestUS2",
-  "Sku": "Premium_LRS",
-  "DiskSizeGB": 513,
-  "PerformancePlus": true,
-  "ProvisioningState": "Succeeded"
-}
-```
-
-### Attempt to attach the disk to a VM
-
-This optional step checks whether the specified VM exists before attempting the disk attachment.
-
-```azurepowershell
-$myVM = "NonExistentVM"
-if (Get-AzVM -ResourceGroupName $myRG -Name $myVM -ErrorAction SilentlyContinue) {
-    Add-AzVMDataDisk -VMName $myVM -ResourceGroupName $myRG -DiskName $myDisk -Lun 0 -CreateOption Empty -ManagedDiskId $dataDisk.Id
-} else {
-    Write-Output "VM $myVM not found. Skipping disk attachment."
-}
-```
-
-Results:
+$dataDisk = New-AzDisk -ResourceGroupName $myRG -DiskName $myDisk -Disk $diskConfig
 
-<!-- expected_similarity=0.3 -->
-```text
-VM NonExistentVM not found. Skipping disk attachment.
+Add-AzVMDataDisk -VMName $myVM -ResourceGroupName $myRG -DiskName $myDisk -Lun $lun -CreateOption Empty -ManagedDiskId $dataDisk.Id
 ```
 
-### Create a new disk from an existing disk or snapshot with performance plus enabled
-
-This series of steps creates a separate resource group and then creates a new disk from an existing disk or snapshot. Replace the $sourceURI with a valid source blob URI that belongs to the same region (WestUS2) as the disk.
-
-#### Create a resource group for migration
+To migrate data from an existing disk or snapshot to a new disk with performance plus enabled, use the following script:
 
 ```azurepowershell
-$RANDOM_SUFFIX = (New-Guid).Guid.Substring(0,6)
-$myMigrRG = "PerfPlusMigrRG$RANDOM_SUFFIX"
-$region = "WestUS2"
-New-AzResourceGroup -Name $myMigrRG -Location $region
-```
-
-Results:
+$myDisk=yourDiskOrSnapshotName
+$myVM=yourVMName
+$region=desiredRegion
+# Valid values are Premium_LRS, Premium_ZRS, StandardSSD_LRS, StandardSSD_ZRS, or Standard_LRS
+$sku=desiredSKU
+#Size must be 513 or larger
+$size=513
+$sourceURI=diskOrSnapshotURI
+$lun=desiredLun
+
+Set-AzContext -SubscriptionName <<yourSubscriptionName>> 
 
-<!-- expected_similarity=0.3 -->
-```JSON
-{
-  "ResourceGroupName": "PerfPlusMigrRGxxx",
-  "Location": "WestUS2",
-  "ProvisioningState": "Succeeded"
-}
-```
-
-#### Create the disk from an existing snapshot or disk
-
-```azurepowershell
-$myDisk = "PerfPlusMigrDisk$RANDOM_SUFFIX"
-$sku = "Premium_LRS"
-$size = 513
-$sourceURI = "https://examplestorageaccount.blob.core.windows.net/snapshots/sample-westus2.vhd"  # Replace with a valid source blob URI in WestUS2
 $diskConfig = New-AzDiskConfig -Location $region -CreateOption Copy -DiskSizeGB $size -SkuName $sku -PerformancePlus $true -SourceResourceID $sourceURI
-$dataDisk = New-AzDisk -ResourceGroupName $myMigrRG -DiskName $myDisk -Disk $diskConfig
-```
-
-Results:
-
-<!-- expected_similarity=0.3 -->
-```JSON
-{
-  "ResourceGroup": "PerfPlusMigrRGxxx",
-  "Name": "PerfPlusMigrDiskxxx",
-  "Location": "WestUS2",
-  "Sku": "Premium_LRS",
-  "DiskSizeGB": 513,
-  "PerformancePlus": true,
-  "SourceResourceID": "https://examplestorageaccount.blob.core.windows.net/snapshots/sample-westus2.vhd",
-  "ProvisioningState": "Succeeded"
-}
-```
 
-#### Attempt to attach the migrated disk to a VM
-
-This optional step verifies the existence of the specified VM before attempting disk attachment.
-
-```azurepowershell
-$myVM = "NonExistentVM"
-if (Get-AzVM -ResourceGroupName $myMigrRG -Name $myVM -ErrorAction SilentlyContinue) {
-    Add-AzVMDataDisk -VMName $myVM -ResourceGroupName $myMigrRG -DiskName $myDisk -Lun 0 -CreateOption Empty -ManagedDiskId $dataDisk.Id
-} else {
-    Write-Output "VM $myVM not found. Skipping disk attachment."
-}
+$dataDisk = New-AzDisk -ResourceGroupName $myRG  -DiskName $myDisk -Disk $diskconfig
+Add-AzVMDataDisk -VMName $myVM -ResourceGroupName $myRG -DiskName $myDisk -Lun $lun -CreateOption Empty -ManagedDiskId $dataDisk.Id
 ```
+---
 
-Results:
+## Next steps
 
-<!-- expected_similarity=0.3 -->
-```text
-VM NonExistentVM not found. Skipping disk attachment.
-```
+- [Create an incremental snapshot for managed disks](disks-incremental-snapshots.md)
+- [Expand virtual hard disks on a Linux VM](linux/expand-disks.md)
+- [How to expand virtual hard disks attached to a Windows virtual machine](windows/expand-os-disk.md)

scenarios/azure-compute-docs/articles/virtual-machines/linux/tutorial-manage-vm.md

@@ -90,11 +90,13 @@ It may take a few minutes to create the VM. Once the VM has been created, the Az
 
 ## Connect to VM
 
-The original tutorial includes commands to connect to the VM via SSH. For non-interactive automated execution, the SSH command is not executed. Instead, use the provided public IP address output from VM creation to manually connect if needed. 
+You can now connect to the VM with SSH in the Azure Cloud Shell or from your local computer. Replace the example IP address with the `publicIpAddress` noted in the previous step.
 
-To connect to the VM, first retrieve the public IP address using the Azure CLI. Execute the following command to store the IP address in a variable: ```export IP_ADDRESS=$(az vm show --show-details --resource-group $MY_RESOURCE_GROUP_NAME --name $MY_VM_NAME --query publicIps --output tsv)```
+To connect to the VM, first retrieve the public IP address using the Azure CLI. Execute the following command to store the IP address in a variable: 
+```export IP_ADDRESS=$(az vm show --show-details --resource-group $MY_RESOURCE_GROUP_NAME --name $MY_VM_NAME --query publicIps --output tsv)```
 
-Once you have the IP address, use SSH to connect to the VM. The following command connects to the VM using the `azureuser` account and the retrieved IP address: ```ssh -o StrictHostKeyChecking=no azureuser@$IP_ADDRESS```
+Once you have the IP address, use SSH to connect to the VM. The following command connects to the VM using the `azureuser` account and the retrieved IP address: 
+```ssh -o StrictHostKeyChecking=no azureuser@$IP_ADDRESS```
 
 ## Understand VM images
 

tools/alert-bad-process.yaml

@@ -0,0 +1,13 @@
+apiVersion: 1
+kind: instance-spec
+image: trace_exec:v0.38.0
+name: alert-bad-process
+paramValues:
+  # monitor all namespaces
+  operator.KubeManager.all-namespaces: true
+  # monitor shell executions (only bash on this example)
+  operator.filter.filter: proc.comm==bash
+  # name of the metric to export
+  operator.otel-metrics.otel-metrics-name: 'exec:shell_executions'
+  # annotate gadget to enable metrics collection
+  operator.oci.annotate: exec:metrics.collect=true,exec:metrics.implicit-counter.name=shell_executions,exec.k8s.namespace:metrics.type=key,exec.k8s.podname:metrics.type=key,exec.k8s.containername:metrics.type=key