added a bunch of new converted docs and updated their metadata to be still compliant with prod metadata

Author: naman-msft

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

@@ -15,18 +15,13 @@ Throughout the lifecycle of your applications, you may need to modify or update
 
 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=adcc95
-export MY_RESOURCE_GROUP_NAME="myResourceGroup$RANDOM_SUFFIX"
-export SCALE_SET_NAME="myScaleSet$RANDOM_SUFFIX"
-export NEW_INSTANCE_NAME="myNewInstance$RANDOM_SUFFIX"
-export REGION="WestUS2"
-```
-
 ## Setup Resource Group
 Before proceeding, ensure the resource group exists. This step creates the resource group if it does not already exist.
 
 ```bash
+export RANDOM_SUFFIX=$(openssl rand -hex 3)
+export MY_RESOURCE_GROUP_NAME="myResourceGroup$RANDOM_SUFFIX"
+export REGION="WestUS2"
 az group create --name $MY_RESOURCE_GROUP_NAME --location $REGION
 ```
 
@@ -49,6 +44,7 @@ az group create --name $MY_RESOURCE_GROUP_NAME --location $REGION
 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
+export SCALE_SET_NAME="myScaleSet$RANDOM_SUFFIX"
 az vmss create \
   --resource-group $MY_RESOURCE_GROUP_NAME \
   --name $SCALE_SET_NAME \
@@ -319,6 +315,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
+export NEW_INSTANCE_NAME="myNewInstance$RANDOM_SUFFIX"
 az vm create --name $NEW_INSTANCE_NAME --resource-group $MY_RESOURCE_GROUP_NAME --vmss $SCALE_SET_NAME --image RHELRaw8LVMGen2
 ```
 

scenarios/azure-management-docs/articles/azure-linux/tutorial-azure-linux-add-nodepool.md

@@ -64,8 +64,6 @@ az aks nodepool add \
 To see the status of your node pools, use the `az aks nodepool list` command and specify your resource group and cluster name. The same environment variable values declared earlier are used here.
 
 ```azurecli-interactive
-export CLUSTER_NAME="myAKSClusterabcf37"
-export RESOURCE_GROUP="myAKSResourceGroupabcf37"
 az aks nodepool list --resource-group $RESOURCE_GROUP --cluster-name $CLUSTER_NAME
 ```
 

scenarios/azure-management-docs/articles/azure-linux/tutorial-azure-linux-create-cluster.md

@@ -38,8 +38,6 @@ When creating a resource group, it is required to specify a location. This locat
 Before running the command, environment variables are declared to ensure unique resource names for each deployment.
 
 ```bash
-export RANDOM_SUFFIX=c97736
-export RESOURCE_GROUP_NAME="testAzureLinuxResourceGroup${RANDOM_SUFFIX}"
 export REGION="EastUS2"
 az group create --name $RESOURCE_GROUP_NAME --location $REGION
 ```
@@ -64,10 +62,9 @@ az group create --name $RESOURCE_GROUP_NAME --location $REGION
 
 ## Create an Azure Linux Container Host cluster
 
-Create an AKS cluster using the `az aks create` command with the `--os-sku` parameter to provision the Azure Linux Container Host with an Azure Linux image. The following example creates an Azure Linux Container Host cluster. A unique cluster name is generated using the same RANDOM_SUFFIX used when creating the resource group.
+Create an AKS cluster using the `az aks create` command with the `--os-sku` parameter to provision the Azure Linux Container Host with an Azure Linux image. The following example creates an Azure Linux Container Host cluster. 
 
 ```bash
-export CLUSTER_NAME="testAzureLinuxCluster${RANDOM_SUFFIX}"
 az aks create --name $CLUSTER_NAME --resource-group $RESOURCE_GROUP_NAME --os-sku AzureLinux
 ```
 

scenarios/azure-management-docs/articles/azure-linux/tutorial-azure-linux-telemetry-monitor.md

@@ -26,15 +26,6 @@ In the next and last tutorial, you'll learn how to upgrade your Azure Linux node
 - If you're connecting an existing AKS cluster to a Log Analytics workspace in another subscription, the Microsoft.ContainerService resource provider must be registered in the subscription with the Log Analytics workspace. For more information, see [Register resource provider](/azure/azure-resource-manager/management/resource-providers-and-types#register-resource-provider).
 - You need the latest version of Azure CLI. Run `az --version` to find the version. If you need to install or upgrade, see [Install Azure CLI](/cli/azure/install-azure-cli).
 
-## Environment Variables
-
-To ensure unique resource names for each deployment, we declare the following environment variables. These variables will be used throughout the tutorial.
-
-```bash
-export RESOURCE_GROUP="myAKSResourceGroupabcf37"
-export CLUSTER_NAME="myAKSClusterabcf37"
-```
-
 ## Enable monitoring
 
 ## Connect to your cluster