Syntax blocks azurecli.

Author: TimShererWithAquent

articles/virtual-machines/extensions/diagnostics-linux.md

@@ -56,7 +56,7 @@ The downloadable configuration is just an example; modify it to suit your own ne
 
 Fill in the correct values for the variables in the first section before running:
 
-```bash
+```azurecli
 # Set your Azure VM diagnostic variables correctly below
 my_resource_group=<your_azure_resource_group_name_containing_your_azure_linux_vm>
 my_linux_vm=<your_azure_linux_vm_name>
@@ -88,7 +88,7 @@ The URL for the sample configuration, and its contents, are subject to change. D
 
 #### PowerShell sample
 
-```Powershell
+```powershell
 $storageAccountName = "yourStorageAccountName"
 $storageAccountResourceGroup = "yourStorageAccountResourceGroupName"
 $vmName = "yourVMName"
@@ -216,7 +216,7 @@ The "sasURL" entry contains the full URL, including SAS token, for the Event Hub
 
 If you created a SAS good until midnight UTC on January 1, 2018, the sasURL value might be:
 
-```url
+```https
 https://contosohub.servicebus.windows.net/syslogmsgs?sr=contosohub.servicebus.windows.net%2fsyslogmsgs&sig=xxxxxxxxxxxxxxxxxxxxxxxxx&se=1514764800&skn=writer
 ```
 

articles/virtual-machines/linux/cloudinit-prepare-custom-image.md

@@ -24,12 +24,14 @@ sudo yum install - y cloud-init
 ```
 
 Update the `cloud_init_modules` section in `/etc/cloud/cloud.cfg` to include the following modules:
+
 ```bash
 - disk_setup
 - mounts
 ```
 
 Here is a sample of what a general-purpose `cloud_init_modules` section looks like.
+
 ```bash
 cloud_init_modules:
  - migrator
@@ -46,7 +48,9 @@ cloud_init_modules:
  - users-groups
  - ssh
 ```
-A number of tasks relating to provisioning and handling ephemeral disks need to be updated in `/etc/waagent.conf`. Run the following commands to update the appropriate settings. 
+
+A number of tasks relating to provisioning and handling ephemeral disks need to be updated in `/etc/waagent.conf`. Run the following commands to update the appropriate settings.
+
 ```bash
 sed -i 's/Provisioning.Enabled=y/Provisioning.Enabled=n/g' /etc/waagent.conf
 sed -i 's/Provisioning.UseCloudInit=n/Provisioning.UseCloudInit=y/g' /etc/waagent.conf
@@ -67,12 +71,14 @@ If your existing Azure image has a swap file configured and you want to change t
 For Red Hat based images - follow the instructions in the following Red Hat document explaining how to [remove the swap file](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/storage_administration_guide/swap-removing-file).
 
 For CentOS images with swapfile enabled, you can run the following command to turn off the swapfile:
+
 ```bash
 sudo swapoff /mnt/resource/swapfile
 ```
 
 Ensure the swapfile reference is removed from `/etc/fstab` - it should look something like the following output:
-```text
+
+```output
 # /etc/fstab
 # Accessible filesystems, by reference, are maintained under '/dev/disk'
 # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
@@ -82,9 +88,11 @@ UUID=7c473048-a4e7-4908-bad3-a9be22e9d37d /boot xfs defaults 0 0
 ```
 
 To save space and remove the swap file you can run the following command:
+
 ```bash
 rm /mnt/resource/swapfile
 ```
+
 ## Extra step for cloud-init prepared image
 > [!NOTE]
 > If your image was previously a **cloud-init** prepared and configured image, you need to do the following steps.
@@ -107,7 +115,7 @@ For more information about the Azure Linux Agent deprovision commands, see the [
 
 Exit the SSH session, then from your bash shell, run the following AzureCLI commands to deallocate, generalize and create a new Azure VM image.  Replace `myResourceGroup` and `sourceVmName` with the appropriate information reflecting your sourceVM.
 
-```bash
+```azurecli
 az vm deallocate --resource-group myResourceGroup --name sourceVmName
 az vm generalize --resource-group myResourceGroup --name sourceVmName
 az image create --resource-group myResourceGroup --name myCloudInitImage --source sourceVmName

articles/virtual-machines/linux/disks-upload-vhd-to-managed-disk-cli.md

@@ -41,7 +41,7 @@ Before you can create an empty standard HDD for uploading, you'll need to have t
 
 Create an empty standard HDD for uploading by specifying both the **-–for-upload** parameter and the **--upload-size-bytes** parameter in a [disk create](/cli/azure/disk#az-disk-create) cmdlet:
 
-```bash
+```azurecli
 az disk create -n mydiskname -g resourcegroupname -l westus2 --for-upload --upload-size-bytes 34359738880 --sku standard_lrs
 ```
 
@@ -51,13 +51,13 @@ You have now created an empty managed disk that is configured for the upload pro
 
 To generate a writable SAS of your empty managed disk, use the following command:
 
-```bash
+```azurecli
 az disk grant-access -n mydiskname -g resourcegroupname --access-level Write --duration-in-seconds 86400
 ```
 
 Sample returned value:
 
-```
+```output
 {
   "accessSas": "https://md-impexp-t0rdsfgsdfg4.blob.core.windows.net/w2c3mj0ksfgl/abcd?sv=2017-04-17&sr=b&si=600a9281-d39e-4cc3-91d2-923c4a696537&sig=xXaT6mFgf139ycT87CADyFxb%2BnPXBElYirYRlbnJZbs%3D"
 }
@@ -77,7 +77,7 @@ AzCopy.exe copy "c:\somewhere\mydisk.vhd" "sas-URI" --blob-type PageBlob
 
 After the upload is complete, and you no longer need to write any more data to the disk, revoke the SAS. Revoking the SAS will change the state of the managed disk and allow you to attach the disk to a VM.
 
-```bash
+```azurecli
 az disk revoke-access -n mydiskname -g resourcegroupname
 ```
 
@@ -92,7 +92,7 @@ The follow script will do this for you, the process is similar to the steps desc
 
 Replace the `<sourceResourceGroupHere>`, `<sourceDiskNameHere>`, `<targetDiskNameHere>`, `<targetResourceGroupHere>`, and `<yourTargetLocationHere>` (an example of a location value would be uswest2) with your values, then run the following script in order to copy a managed disk.
 
-```bash
+```azurecli
 sourceDiskName = <sourceDiskNameHere>
 sourceRG = <sourceResourceGroupHere>
 targetDiskName = <targetDiskNameHere>

articles/virtual-machines/linux/image-builder-user-assigned-identity.md

@@ -59,7 +59,7 @@ az provider register -n Microsoft.Storage
 We will be using some pieces of information repeatedly, so we will create some variables to store that information.
 
 
-```azurecli-interactive
+```console
 # Image resource group name 
 imageResourceGroup=aibmdimsi
 # storage resource group
@@ -74,7 +74,7 @@ runOutputName=u1804ManImgMsiro
 
 Create a variable for your subscription ID. You can get this using `az account show | grep id`.
 
-```azurecli-interactive
+```console
 subscriptionID=<Your subscription ID>
 ```
 
@@ -148,7 +148,7 @@ imgBuilderId=/subscriptions/$subscriptionID/resourcegroups/$imageResourceGroup/p
 
 Download the example .json file and configure it with the variables you created.
 
-```azurecli-interactive
+```console
 curl https://raw.githubusercontent.com/danielsollondon/azvmimagebuilder/master/quickquickstarts/7_Creating_Custom_Image_using_MSI_to_Access_Storage/helloImageTemplateMsi.json -o helloImageTemplateMsi.json
 sed -i -e "s/<subscriptionID>/$subscriptionID/g" helloImageTemplateMsi.json
 sed -i -e "s/<rgName>/$imageResourceGroup/g" helloImageTemplateMsi.json
@@ -188,7 +188,7 @@ Wait for the build to complete. This can take about 15 minutes.
 
 Create a VM from the image. 
 
-```bash
+```azurecli
 az vm create \
   --resource-group $imageResourceGroup \
   --name aibImgVm00 \
@@ -200,13 +200,13 @@ az vm create \
 
 After the VM has been created, start an SSH session with the VM.
 
-```azurecli-interactive
+```console
 ssh aibuser@<publicIp>
 ```
 
 You should see the image was customized with a Message of the Day as soon as your SSH connection is established!
 
-```console
+```output
 
 *******************************************************
 **            This VM was built from the:            **

articles/virtual-machines/linux/image-builder.md

@@ -60,7 +60,7 @@ az provider register -n Microsoft.Storage
 We will be using some pieces of information repeatedly, so we will create some variables to store that information.
 
 
-```azurecli-interactive
+```console
 # Resource group name - we are using myImageBuilderRG in this example
 imageResourceGroup=myImageBuilerRGLinux
 # Datacenter location - we are using West US 2 in this example
@@ -73,7 +73,7 @@ runOutputName=aibLinux
 
 Create a variable for your subscription ID. You can get this using `az account show | grep id`.
 
-```azurecli-interactive
+```console
 subscriptionID=<Your subscription ID>
 ```
 
@@ -100,7 +100,7 @@ az role assignment create \
 
 A parameterized sample image configuration template has been created for you to use. Download the sample .json file and configure it with the variables you set earlier.
 
-```azurecli-interactive
+```console
 curl https://raw.githubusercontent.com/danielsollondon/azvmimagebuilder/master/quickquickstarts/0_Creating_a_Custom_Linux_Managed_Image/helloImageTemplateLinux.json -o helloImageTemplateLinux.json
 
 sed -i -e "s/<subscriptionID>/$subscriptionID/g" helloImageTemplateLinux.json
@@ -112,7 +112,7 @@ sed -i -e "s/<runOutputName>/$runOutputName/g" helloImageTemplateLinux.json
 
 You can modify this example .json as needed. For example, you can increase the value of `buildTimeoutInMinutes` to allow for longer running builds. You can edit the file in Cloud Shell using  a text editor like `vi`.
 
-```azurecli-interactive
+```console
 vi helloImageTemplateLinux.json
 ```
 
@@ -184,13 +184,13 @@ az vm create \
 
 Get the IP address from the output of creating the VM and use it to SSH to the VM.
 
-```azurecli-interactive
+```console
 ssh azureuser@<pubIp>
 ```
 
 You should see the image was customized with a Message of the Day as soon as your SSH connection is established!
 
-```console
+```output
 
 *******************************************************
 **            This VM was built from the:            **
@@ -205,7 +205,7 @@ Type `exit` when you are done to close the SSH connection.
 
 In the Image Builder Template, in the 'Properties', you will see the source image, customization script it runs, and where it is distributed.
 
-```azurecli-interactive
+```console
 cat helloImageTemplateLinux.json
 ```
 
@@ -226,7 +226,7 @@ az resource delete \
 
 Delete the image resource group.
 
-```bash
+```azurecli
 az group delete -n $imageResourceGroup
 ```
 

articles/virtual-machines/linux/migration-classic-resource-manager-plan.md

@@ -120,19 +120,19 @@ The following were issues discovered in many of the larger migrations. This is n
 
     **Compute** *(Cores, Availability Sets)*
 
-    ```bash
+    ```azurecli
     az vm list-usage -l <azure-region> -o jsonc
     ```
 
     **Network** *(Virtual Networks, Static Public IPs, Public IPs, Network Security Groups, Network Interfaces, Load Balancers, Route Tables)*
 
-    ```bash
+    ```azurecli
     az network list-usages -l <azure-region> -o jsonc
     ```
 
     **Storage** *(Storage Account)*
 
-    ```bash
+    ```azurecli
     az storage account show-usage
     ```
 

articles/virtual-machines/linux/mount-azure-file-storage-on-linux-using-smb.md

@@ -24,15 +24,15 @@ This guide requires that you're running the Azure CLI version 2.0.4 or later. Ru
 
 Create a resource group named *myResourceGroup* in the *East US* location.
 
-```bash
+```azurecli
 az group create --name myResourceGroup --location eastus
 ```
 
 ## Create a storage account
 
 Create a new storage account, within the resource group that you created, using [az storage account create](/cli/azure/storage/account). This example creates a storage account named *mySTORAGEACCT\<random number>* and puts the name of that storage account in the variable **STORAGEACCT**. Storage account names must be unique, using `$RANDOM` appends a number to the end to make it unique.
 
-```bash
+```azurecli
 STORAGEACCT=$(az storage account create \
     --resource-group "myResourceGroup" \
     --name "mystorageacct$RANDOM" \
@@ -47,7 +47,7 @@ When you create a storage account, the account keys are created in pairs so that
 
 View the storage account keys using [az storage account keys list](/cli/azure/storage/account/keys). This example stores the value of key 1 in the **STORAGEKEY** variable.
 
-```bash
+```azurecli
 STORAGEKEY=$(az storage account keys list \
     --resource-group "myResourceGroup" \
     --account-name $STORAGEACCT \
@@ -62,7 +62,7 @@ Share names need to be all lower case letters, numbers, and single hyphens but c
 
 This example creates a share named *myshare* with a 10-GiB quota. 
 
-```bash
+```azurecli
 az storage share create --name myshare \
     --quota 10 \
     --account-name $STORAGEACCT \
@@ -98,6 +98,7 @@ When you reboot the Linux VM, the mounted SMB share is unmounted during shutdown
 ```bash
 //myaccountname.file.core.windows.net/mystorageshare /mnt/mymountpoint cifs vers=3.0,username=mystorageaccount,password=myStorageAccountKeyEndingIn==,dir_mode=0777,file_mode=0777
 ```
+
 For increased security in production environments, you should store your credentials outside of fstab.
 
 ## Next steps

articles/virtual-machines/linux/openshift-container-platform-3x-prerequisites.md

@@ -51,16 +51,17 @@ If you don't have an Azure subscription, create a [free account](https://azure.m
 ## Sign in to Azure 
 Sign in to your Azure subscription with the [az login](/cli/azure/reference-index) command and follow the on-screen directions, or click **Try it** to use Cloud Shell.
 
-```azurecli 
+```azurecli
 az login
 ```
+
 ## Create a resource group
 
 Create a resource group with the [az group create](/cli/azure/group) command. An Azure resource group is a logical container into which Azure resources are deployed and managed. You should use a dedicated resource group to host the key vault. This group is separate from the resource group into which the OpenShift cluster resources deploy.
 
 The following example creates a resource group named *keyvaultrg* in the *eastus* location:
 
-```azurecli 
+```azurecli
 az group create --name keyvaultrg --location eastus
 ```
 
@@ -78,7 +79,7 @@ az keyvault create --resource-group keyvaultrg --name keyvault \
 ## Create an SSH key 
 An SSH key is needed to secure access to the OpenShift cluster. Create an SSH key pair by using the `ssh-keygen` command (on Linux or macOS):
 
- ```bash
+```bash
 ssh-keygen -f ~/.ssh/openshift_rsa -t rsa -N ''
 ```
 
@@ -112,6 +113,7 @@ Create service principal:
 ```azurecli
 az group show --name openshiftrg --query id
 ```
+
 Save the output of the command and use in place of $scope in next command
 
 ```azurecli
@@ -120,6 +122,7 @@ az ad sp create-for-rbac --name openshiftsp \
 ```
 
 Take note of the appId property and password returned from the command:
+
 ```json
 {
   "appId": "11111111-abcd-1234-efgh-111111111111",
@@ -129,6 +132,7 @@ Take note of the appId property and password returned from the command:
   "tenant": "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"
 }
 ```
+
  > [!WARNING] 
  > Be sure to write down the secure password as it will not be possible to retrieve this password again.
 
@@ -157,7 +161,7 @@ You'll need to store these files in Key Vault secrets.  Use the same Key Vault a
 
 Create the secrets using the Azure CLI. Below is an example.
 
-```bash
+```azurecli
 az keyvault secret set --vault-name KeyVaultName -n mastercafile --file ~/certificates/masterca.pem
 ```