Merge pull request #108445 from TimShererWithAquent/us1669724q

Azure CLI syntax blocks.

Author: megvanhuygen

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

@@ -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",

articles/virtual-machines/workloads/sap/deployment-guide.md

@@ -784,9 +784,11 @@ This section has detailed steps for doing specific tasks in the configuration an
 Check frequently for updates to the PowerShell cmdlets, which usually are updated monthly. The easiest way to check for updates is to do the preceding installation steps, up to the installation page shown in step 5. The release date and release number of the cmdlets are included on the page shown in step 5. Unless stated otherwise in SAP Note [1928533] or SAP Note [2015553], we recommend that you work with the latest version of Azure PowerShell cmdlets.
 
 To check the version of the Azure PowerShell cmdlets that are installed on your computer, run this PowerShell command:
+
 ```powershell
 (Get-Module Az.Compute).Version
 ```
+
 The result looks like this:
 
 ![Result of Azure PowerShell cmdlet version check][deployment-guide-figure-600]
@@ -813,7 +815,8 @@ If the Azure cmdlet version installed on your computer is the current version, t
 Check frequently for updates to Azure CLI, which usually is updated monthly. The easiest way to check for updates is to do the preceding installation steps, up to the installation page shown in step 5.
 
 To check the version of Azure CLI that is installed on your computer, run this command:
-```
+
+```console
 azure --version
 ```
 
@@ -854,13 +857,13 @@ Use the following commands to install the VM Agent for Linux:
 
 * **SUSE Linux Enterprise Server (SLES)**
 
-  ```
+  ```console
   sudo zypper install WALinuxAgent
   ```
 
 * **Red Hat Enterprise Linux (RHEL) or Oracle Linux**
 
-  ```
+  ```console
   sudo yum install WALinuxAgent
   ```
 
@@ -890,18 +893,22 @@ Configure the correct proxy in the configuration file of the Microsoft Azure Gue
 Set the following parameters:
 
 1. **HTTP proxy host**. For example, set it to **proxy.corp.local**.
-   ```
+
+   ```console
    HttpProxy.Host=<proxy host>
 
    ```
+
 1. **HTTP proxy port**. For example, set it to **80**.
-   ```
+
+   ```console
    HttpProxy.Port=<port of the proxy host>
 
    ```
+
 1. Restart the agent.
 
-   ```
+   ```console
    sudo service waagent restart
    ```
 
@@ -970,19 +977,19 @@ To install the Azure Extension for SAP by using Azure CLI:
    1. Install Azure classic CLI, as described in [Install the Azure classic CLI][azure-cli].
    1. Sign in with your Azure account:
 
-      ```
+      ```console
       azure login
       ```
 
    1. Switch to Azure Resource Manager mode:
 
-      ```
+      ```console
       azure config mode arm
       ```
 
    1. Enable Azure Extension for SAP:
 
-      ```
+      ```console
       azure vm enable-aem <resource-group-name> <vm-name>
       ```
 
@@ -991,30 +998,31 @@ To install the Azure Extension for SAP by using Azure CLI:
    1. Install Azure CLI 2.0, as described in [Install Azure CLI 2.0][azure-cli-2].
    1. Sign in with your Azure account:
 
-      ```
+      ```azurecli
       az login
       ```
 
    1. Install Azure CLI AEM Extension
   
-      ```
+      ```azurecli
       az extension add --name aem
       ```
   
    1. Install the extension with
   
-      ```
+      ```azurecli
       az vm aem set -g <resource-group-name> -n <vm name>
       ```
 
 1. Verify that the Azure Extension for SAP is active on the Azure Linux VM. Check whether the file \\var\\lib\\AzureEnhancedMonitor\\PerfCounters exists. If it exists, at a command prompt, run this command to display information collected by the Azure Extension for SAP:
 
-   ```
+   ```console
    cat /var/lib/AzureEnhancedMonitor/PerfCounters
    ```
 
    The output looks like this:
-   ```
+
+   ```output
    ...
    2;cpu;Current Hw Frequency;;0;2194.659;MHz;60;1444036656;saplnxmon;
    2;cpu;Max Hw Frequency;;0;2194.659;MHz;0;1444036656;saplnxmon;
@@ -1133,6 +1141,7 @@ If some of the infrastructure data is not delivered correctly as indicated by th
 
 1. Make sure that you have installed the latest version of the Azure PowerShell cmdlet, as described in [Deploying Azure PowerShell cmdlets][deployment-guide-4.1].
 1. Run the following PowerShell cmdlet. For a list of available environments, run the cmdlet `Get-AzEnvironment`. To use global Azure, select the **AzureCloud** environment. For Azure in China, select **AzureChinaCloud**.
+
    ```powershell
    $env = Get-AzEnvironment -Name <name of the environment>
    Connect-AzAccount -Environment $env

articles/virtual-machines/workloads/sap/high-availability-guide-standard-load-balancer-outbound-connections.md

@@ -99,7 +99,7 @@ The configuration would look like:
    1. Select the VMs and their IP addresses and add them to the backend pool  
 3. [Create outbound rules](https://docs.microsoft.com/azure/load-balancer/configure-load-balancer-outbound-cli#create-outbound-rule). Currently it is not possible to create outbound rules from the Azure portal. You can create outbound rules with [Azure CLI](https://docs.microsoft.com/azure/cloud-shell/overview?view=azure-cli-latest).  
 
-   ```
+   ```azurecli
     az network lb outbound-rule create --address-pool MyBackendPoolOfPublicILB --frontend-ip-configs MyPublicILBFrondEndIP --idle-timeout 30 --lb-name MyPublicILB --name MyOutBoundRules  --outbound-ports 10000 --enable-tcp-reset true --protocol All --resource-group MyResourceGroup
    ```
 
@@ -186,17 +186,19 @@ You could use proxy to allow Pacemaker calls to the Azure management API public
 There are many different Proxy options available in the industry. Step-by-step instructions for the proxy deployment are outside of the scope of this document. In the example below, we assume that your proxy is responding to **MyProxyService** and listening to port **MyProxyPort**.  
 To allow pacemaker to communicate with the Azure management API, perform the following steps on all cluster nodes:  
 
-1. Edit the pacemaker configuration file /etc/sysconfig/pacemaker and add the following lines (all cluster nodes):  
-   ```
+1. Edit the pacemaker configuration file /etc/sysconfig/pacemaker and add the following lines (all cluster nodes):
+
+   ```console
    sudo vi /etc/sysconfig/pacemaker
    # Add the following lines
    http_proxy=http://MyProxyService:MyProxyPort
    https_proxy=http://MyProxyService:MyProxyPort
    ```
 
 2. Restart the pacemaker service on **all** cluster nodes.  
-  - SUSE  
-     ```
+  - SUSE
+ 
+     ```console
      # Place the cluster in maintenance mode
      sudo crm configure property maintenance-mode=true
      #Restart on all nodes
@@ -206,7 +208,8 @@ To allow pacemaker to communicate with the Azure management API, perform the fol
      ```
 
   - Red Hat  
-     ```
+
+     ```console
      # Place the cluster in maintenance mode
      sudo pcs property set maintenance-mode=true
      #Restart on all nodes