Syntax blocks azurecli.

Author: TimShererWithAquent

articles/virtual-machines/linux/image-builder-gallery-update-image-version.md

@@ -53,7 +53,7 @@ If you used [Create an image and distribute to a Shared Image Gallery](image-bui
 For Preview, image builder will only support creating custom images in the same Resource Group as the source managed image. Update the resource group name in this example to be the same resource group as your source managed image.
 
 
-```azurecli-interactive
+```console
 # Resource group name 
 sigResourceGroup=ibLinuxGalleryRG
 # Gallery location 
@@ -70,13 +70,13 @@ runOutputName=aibSIGLinuxUpdate
 
 Create a variable for your subscription ID. You can get this using `az account show | grep id`.
 
-```azurecli-interactive
+```console
 subscriptionID=<Subscription ID>
 ```
 
 Get the image version that you want to update.
 
-```
+```azurecli
 sigDefImgVersionId=$(az sig image-version list \
    -g $sigResourceGroup \
    --gallery-name $sigName \
@@ -102,7 +102,7 @@ You can review the example we are about to use by opening the .json file here: [
 
 Download the .json example and configure it with your variables. 
 
-```azurecli-interactive
+```console
 curl https://raw.githubusercontent.com/danielsollondon/azvmimagebuilder/master/quickquickstarts/8_Creating_a_Custom_Linux_Shared_Image_Gallery_Image_from_SIG/helloImageTemplateforSIGfromSIG.json -o helloImageTemplateforSIGfromSIG.json
 sed -i -e "s/<subscriptionID>/$subscriptionID/g" helloImageTemplateforSIGfromSIG.json
 sed -i -e "s/<rgName>/$sigResourceGroup/g" helloImageTemplateforSIGfromSIG.json
@@ -154,13 +154,13 @@ az vm create \
 
 Create an SSH connection to the VM using the public IP address of 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:            **
 **      !! AZURE VM IMAGE BUILDER Custom Image !!    **

articles/virtual-machines/windows/image-builder-gallery-update-image-version.md

@@ -55,7 +55,7 @@ If you used [Create an image and distribute to a Shared Image Gallery](image-bui
 
 For Preview, image builder will only support creating custom images in the same Resource Group as the source managed image. Update the resource group name in this example to be the same resource group as your source managed image.
 
-```azurecli-interactive
+```console
 # Resource group name - we are using ibsigRG in this example
 sigResourceGroup=myIBWinRG
 # Datacenter location - we are using West US 2 in this example
@@ -75,7 +75,7 @@ vmpassword="password for the VM"
 
 Create a variable for your subscription ID. You can get this using `az account show | grep id`.
 
-```azurecli-interactive
+```console
 subscriptionID=<Subscription ID>
 ```
 
@@ -107,7 +107,7 @@ You can review the example we are about to use by opening the .json file here: [
 
 Download the .json example and configure it with your variables. 
 
-```azurecli-interactive
+```console
 curl https://raw.githubusercontent.com/danielsollondon/azvmimagebuilder/master/quickquickstarts/8_Creating_a_Custom_Win_Shared_Image_Gallery_Image_from_SIG/helloImageTemplateforSIGfromWinSIG.json -o helloImageTemplateforSIGfromWinSIG.json
 sed -i -e "s/<subscriptionID>/$subscriptionID/g" helloImageTemplateforSIGfromWinSIG.json
 sed -i -e "s/<rgName>/$sigResourceGroup/g" helloImageTemplateforSIGfromWinSIG.json

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

@@ -62,7 +62,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=myWinImgBuilderRG
 # Region location 
@@ -77,7 +77,7 @@ imageName=aibWinImage
 
 Create a variable for your subscription ID. You can get this using `az account show | grep id`.
 
-```azurecli-interactive
+```console
 subscriptionID=<Your subscription ID>
 ```
 ## Create a resource group
@@ -106,7 +106,7 @@ az role assignment create \
 
 A parameterized image configuration template has been created for you to try. Download the example .json file and configure it with the variables you set previously.
 
-```azurecli-interactive
+```console
 curl https://raw.githubusercontent.com/danielsollondon/azvmimagebuilder/master/quickquickstarts/0_Creating_a_Custom_Windows_Managed_Image/helloImageTemplateWin.json -o helloImageTemplateWin.json
 
 sed -i -e "s/<subscriptionID>/$subscriptionID/g" helloImageTemplateWin.json
@@ -119,7 +119,7 @@ sed -i -e "s/<runOutputName>/$runOutputName/g" helloImageTemplateWin.json
 
 You can modify this example, in the terminal using a text editor like `vi`.
 
-```azurecli-interactive
+```console
 vi helloImageTemplateLinux.json
 ```
 
@@ -205,6 +205,7 @@ You should see these two directories created during image customization:
 When you are done, delete the resources.
 
 ### Delete the image builder template
+
 ```azurecli-interactive
 az resource delete \
     --resource-group $imageResourceGroup \
@@ -213,6 +214,7 @@ az resource delete \
 ```
 
 ### Delete the image resource group
+
 ```azurecli-interactive
 az group delete -n $imageResourceGroup
 ```

articles/virtual-machines/windows/quick-create-cli.md

@@ -56,7 +56,7 @@ az vm create \
 
 It takes a few minutes to create the VM and supporting resources. The following example output shows the VM create operation was successful.
 
-```azurecli-interactive
+```output
 {
   "fqdns": "",
   "id": "/subscriptions/<guid>/resourceGroups/myResourceGroup/providers/Microsoft.Compute/virtualMachines/myVM",

articles/virtual-machines/windows/template-description.md

@@ -153,7 +153,7 @@ This example shows a typical resource section of a template for creating a speci
 
 When you deploy resources using a template, you have to specify a version of the API to use. The example shows the virtual machine resource using this apiVersion element:
 
-```
+```json
 "apiVersion": "2016-04-30-preview",
 ```
 
@@ -170,7 +170,7 @@ Use these opportunities for getting the latest API versions:
 
 [Parameters](../../resource-group-authoring-templates.md) make it easy for you to specify values for the template when you run it. This parameters section is used in the example:
 
-```        
+```json
 "parameters": {
   "adminUsername": { "type": "string" },
   "adminPassword": { "type": "securestring" },
@@ -182,7 +182,7 @@ When you deploy the example template, you enter values for the name and password
 
 [Variables](../../resource-group-authoring-templates.md) make it easy for you to set up values in the template that are used repeatedly throughout it or that can change over time. This variables section is used in the example:
 
-```
+```json
 "variables": { 
   "storageName": "mystore1",
   "accountid": "[concat('/subscriptions/', subscription().subscriptionId, 
@@ -219,7 +219,7 @@ When you deploy the example template, variable values are used for the name and
 
 When you need more than one virtual machine for your application, you can use a copy element in a template. This optional element loops through creating the number of VMs that you specified as a parameter:
 
-```
+```json
 "copy": {
   "name": "virtualMachineLoop",	
   "count": "[parameters('numberOfInstances')]"
@@ -228,7 +228,7 @@ When you need more than one virtual machine for your application, you can use a
 
 Also, notice in the example that the loop index is used when specifying some of the values for the resource. For example, if you entered an instance count of three, the names of the operating system disks are myOSDisk1, myOSDisk2, and myOSDisk3:
 
-```
+```json
 "osDisk": { 
   "name": "[concat('myOSDisk', copyindex())]",
   "caching": "ReadWrite", 
@@ -243,7 +243,7 @@ Also, notice in the example that the loop index is used when specifying some of
 
 Keep in mind that creating a loop for one resource in the template may require you to use the loop when creating or accessing other resources. For example, multiple VMs can’t use the same network interface, so if your template loops through creating three VMs it must also loop through creating three network interfaces. When assigning a network interface to a VM, the loop index is used to identify it:
 
-```
+```json
 "networkInterfaces": [ { 
   "id": "[resourceId('Microsoft.Network/networkInterfaces',
     concat('myNIC', copyindex()))]" 
@@ -254,7 +254,7 @@ Keep in mind that creating a loop for one resource in the template may require y
 
 Most resources depend on other resources to work correctly. Virtual machines must be associated with a virtual network and to do that it needs a network interface. The [dependsOn](../../resource-group-define-dependencies.md) element is used to make sure that the network interface is ready to be used before the VMs are created:
 
-```
+```json
 "dependsOn": [
   "[concat('Microsoft.Network/networkInterfaces/', 'myNIC', copyindex())]" 
 ],
@@ -264,7 +264,7 @@ Resource Manager deploys in parallel any resources that aren't dependent on anot
 
 How do you know if a dependency is required? Look at the values you set in the template. If an element in the virtual machine resource definition points to another resource that is deployed in the same template, you need a dependency. For example, your example virtual machine defines a network profile:
 
-```
+```json
 "networkProfile": { 
   "networkInterfaces": [ { 
     "id": "[resourceId('Microsoft.Network/networkInterfaces',
@@ -293,7 +293,7 @@ In Azure, vhd files can represent [disks or images](managed-disks-overview.md?to
 
 When you create a VM, you must decide what operating system to use. The imageReference element is used to define the operating system of a new VM. The example shows a definition for a Windows Server operating system:
 
-```
+```json
 "imageReference": { 
   "publisher": "MicrosoftWindowsServer", 
   "offer": "WindowsServer", 
@@ -304,7 +304,7 @@ When you create a VM, you must decide what operating system to use. The imageRef
 
 If you want to create a Linux operating system, you might use this definition:
 
-```
+```json
 "imageReference": {
   "publisher": "Canonical",
   "offer": "UbuntuServer",
@@ -315,7 +315,7 @@ If you want to create a Linux operating system, you might use this definition:
 
 Configuration settings for the operating system disk are assigned with the osDisk element. The example defines a new managed disk with the caching mode set to **ReadWrite** and that the disk is being created from a [platform image](cli-ps-findimage.md):
 
-```
+```json
 "osDisk": { 
   "name": "[concat('myOSDisk', copyindex())]",
   "caching": "ReadWrite", 
@@ -327,7 +327,7 @@ Configuration settings for the operating system disk are assigned with the osDis
 
 If you want to create virtual machines from existing disks, remove the imageReference and the osProfile elements and define these disk settings:
 
-```
+```json
 "osDisk": { 
   "osType": "Windows",
   "managedDisk": { 
@@ -342,7 +342,7 @@ If you want to create virtual machines from existing disks, remove the imageRefe
 
 If you want to create a virtual machine from a managed image, change the imageReference element and define these disk settings:
 
-```
+```json
 "storageProfile": { 
   "imageReference": {
     "id": "[resourceId('Microsoft.Compute/images', 'myImage')]"
@@ -360,7 +360,7 @@ If you want to create a virtual machine from a managed image, change the imageRe
 
 You can optionally add data disks to the VMs. The [number of disks](sizes.md) depends on the size of operating system disk that you use. With the size of the VMs set to Standard_DS1_v2, the maximum number of data disks that could be added to the them is two. In the example, one managed data disk is being added to each VM:
 
-```
+```json
 "dataDisks": [
   {
     "name": "[concat('myDataDisk', copyindex())]",
@@ -376,7 +376,7 @@ You can optionally add data disks to the VMs. The [number of disks](sizes.md) de
 
 Although [extensions](extensions-features.md) are a separate resource, they're closely tied to VMs. Extensions can be added as a child resource of the VM or as a separate resource. The example shows the [Diagnostics Extension](extensions-diagnostics-template.md) being added to the VMs:
 
-```
+```json
 { 
   "name": "Microsoft.Insights.VMDiagnosticsSettings", 
   "type": "extensions", 
@@ -411,7 +411,7 @@ This extension resource uses the storageName variable and the diagnostic variabl
 
 There are many extensions that you can install on a VM, but the most useful is probably the [Custom Script Extension](extensions-customscript.md). In the example, a PowerShell script named start.ps1 runs on each VM when it first starts:
 
-```
+```json
 {
   "name": "MyCustomScriptExtension",
   "type": "extensions",