Merge pull request #253097 from alexbuckgit/alexbuckgit/docutune-autopr-20230927-234151-7914660-ignore-build

[BULK] - DocuTune - Fix code formatting issues (part 2)

Author: Jill Grant

articles/devtest-labs/devtest-lab-vm-powershell.md

@@ -186,7 +186,7 @@ You can also call the DevTest Labs REST API to get the properties of existing la
 In training, demo, and trial scenarios, you can avoid unnecessary costs by deleting VMs automatically on a certain date. You can set the VM `expirationDate` property when you create a VM. The PowerShell VM creation script earlier in this article sets an expiration date under `properties`:
 
 ```json
-          "expirationDate"          = "2022-12-01"
+  "expirationDate": "2022-12-01"
 ```
 
 You can also set expiration dates on existing VMs by using PowerShell. The following PowerShell script sets an expiration date for an existing lab VM if it doesn't already have an expiration date:

articles/devtest-labs/resource-group-control.md

@@ -71,22 +71,22 @@ Invoke the script by using the following command. ResourceGroup.ps1 is the file
 If you're using an Azure Resource Manager template to create a lab, use the **vmCreationResourceGroupId** property in the lab properties section of your template, as shown in the following example:
 
 ```json
-        {
-            "type": "microsoft.devtestlab/labs",
-            "name": "[parameters('lab_name')]",
-            "apiVersion": "2018-10-15-preview",
-            "location": "eastus",
-            "tags": {},
-            "scale": null,
-            "properties": {
-                "vmCreationResourceGroupId": "/subscriptions/<SubscriptionID>/resourcegroups/<ResourceGroupName>",
-                "labStorageType": "Premium",
-                "premiumDataDisks": "Disabled",
-                "provisioningState": "Succeeded",
-                "uniqueIdentifier": "000000000f-0000-0000-0000-00000000000000"
-            },
-            "dependsOn": []
-        },
+{
+    "type": "microsoft.devtestlab/labs",
+    "name": "[parameters('lab_name')]",
+    "apiVersion": "2018-10-15-preview",
+    "location": "eastus",
+    "tags": {},
+    "scale": null,
+    "properties": {
+        "vmCreationResourceGroupId": "/subscriptions/<SubscriptionID>/resourcegroups/<ResourceGroupName>",
+        "labStorageType": "Premium",
+        "premiumDataDisks": "Disabled",
+        "provisioningState": "Succeeded",
+        "uniqueIdentifier": "000000000f-0000-0000-0000-00000000000000"
+    },
+    "dependsOn": []
+},
 ```
 
 

articles/firewall/snat-private-range.md

@@ -201,20 +201,21 @@ You can use the following JSON to configure auto-learn. Azure Firewall must be a
 Use the following JSON to associate an Azure Route Server:
 
 ```json
-            "type": "Microsoft.Network/azureFirewalls",
-            "apiVersion": "2022-11-01",
-            "name": "[parameters('azureFirewalls_testFW_name')]",
-            "location": "eastus",
-            "properties": {
-                "sku": {
-                    "name": "AZFW_VNet",
-                    "tier": "Standard"
-                },
-                "threatIntelMode": "Alert",
-                "additionalProperties": {
-                    "Network.RouteServerInfo.RouteServerID": "[parameters'virtualHubs_TestRouteServer_externalid')]"
-                },
-        
+  "type": "Microsoft.Network/azureFirewalls",
+  "apiVersion": "2022-11-01",
+  "name": "[parameters('azureFirewalls_testFW_name')]",
+  "location": "eastus",
+  "properties": {
+    "sku": {
+      "name": "AZFW_VNet",
+      "tier": "Standard"
+    },
+    "threatIntelMode": "Alert",
+    "additionalProperties": {
+      "Network.RouteServerInfo.RouteServerID": "[parameters'virtualHubs_TestRouteServer_externalid')]"
+    },
+    ...
+  }
 ``` 
 
 ### Configure using Azure PowerShell

articles/machine-learning/how-to-create-compute-instance.md

@@ -221,7 +221,7 @@ To see the newly created network interfaces, use the [az network nic show](/cli/
 The output contains this line:
 
 ```json
-      "privateIPAllocationMethod": "Dynamic",
+  "privateIPAllocationMethod": "Dynamic",
 ```
 
 # [Azure PowerShell](#tab/azure-powershell)
@@ -311,7 +311,7 @@ To view the properties of a network interface, use the [az network nic show](/cl
 The output contains this line:
 
 ```json
-      "privateIPAllocationMethod": "Static",
+  "privateIPAllocationMethod": "Static",
 ```
 
 # [Azure PowerShell](#tab/azure-powershell)

articles/payment-hsm/create-different-vnet.md

@@ -210,7 +210,7 @@ To see the newly created network interfaces, use the [az network nic show](/cli/
 The output contains this line:
 
 ```json
-      "privateIPAllocationMethod": "Dynamic",
+  "privateIPAllocationMethod": "Dynamic",
 ```
 
 # [Azure PowerShell](#tab/azure-powershell)
@@ -300,7 +300,7 @@ To view the properties of a network interface, use the [az network nic show](/cl
 The output contains this line:
 
 ```json
-      "privateIPAllocationMethod": "Static",
+  "privateIPAllocationMethod": "Static",
 ```
 
 # [Azure PowerShell](#tab/azure-powershell)

articles/payment-hsm/create-payment-hsm.md

@@ -89,14 +89,14 @@ For the example above, the output of your skill will be written to a new node in
 
 #### document/myKeyPhrases 
 ```json
-            [
-              "world’s glaciers", 
-              "huge rivers of ice", 
-              "Canadian Rockies", 
-              "iconic landscapes",
-              "Mount Everest region",
-              "Continued warming"
-            ]
+[
+  "world’s glaciers", 
+  "huge rivers of ice", 
+  "Canadian Rockies", 
+  "iconic landscapes",
+  "Mount Everest region",
+  "Continued warming"
+]
 ```
 
 You may use "document/myKeyPhrases" as input into other skills, or as a source of an [output field mapping](cognitive-search-output-field-mapping.md).

articles/search/cognitive-search-skill-keyphrases.md

@@ -180,17 +180,16 @@ To adjust the node count for a node type using an ARM Template, adjust the `vmIn
 > The managed cluster provider will block scale adjustments and return an error if the scaling request violates required minimums.
 
 ```json
-     {
-            "apiVersion": "[variables('sfApiVersion')]",
-            "type": "Microsoft.ServiceFabric/managedclusters/nodetypes",
-            "name": "[concat(parameters('clusterName'), '/', parameters('nodeTypeName'))]",
-            "location": "[resourcegroup().location]",
-            "properties": {
-                ...
-                "vmInstanceCount": "[parameters('nodeTypeVmInstanceCount')]",
-                ...
-            }
-        }
+{
+  "apiVersion": "[variables('sfApiVersion')]",
+  "type": "Microsoft.ServiceFabric/managedclusters/nodetypes",
+  "name": "[concat(parameters('clusterName'), '/', parameters('nodeTypeName'))]",
+  "location": "[resourcegroup().location]",
+  "properties": {
+    ...
+    "vmInstanceCount": "[parameters('nodeTypeVmInstanceCount')]",
+    ...
+  }
 }
 ```
 
@@ -281,20 +280,19 @@ To modify the OS image used for a node type using an ARM Template, adjust the `v
 * The Service Fabric managed cluster resource apiVersion should be **2021-05-01** or later.
 
 ```json
-     {
-            "apiVersion": "[variables('sfApiVersion')]",
-            "type": "Microsoft.ServiceFabric/managedclusters/nodetypes",
-            "name": "[concat(parameters('clusterName'), '/', parameters('nodeTypeName'))]",
-            "location": "[resourcegroup().location]",
-            "properties": {
-                ...
-                "vmImagePublisher": "[parameters('vmImagePublisher')]",
-                "vmImageOffer": "[parameters('vmImageOffer')]",
-                "vmImageSku": "[parameters('vmImageSku')]",
-                "vmImageVersion": "[parameters('vmImageVersion')]",
-                ...
-            }
-        }
+{
+  "apiVersion": "[variables('sfApiVersion')]",
+  "type": "Microsoft.ServiceFabric/managedclusters/nodetypes",
+  "name": "[concat(parameters('clusterName'), '/', parameters('nodeTypeName'))]",
+  "location": "[resourcegroup().location]",
+  "properties": {
+    ...
+    "vmImagePublisher": "[parameters('vmImagePublisher')]",
+    "vmImageOffer": "[parameters('vmImageOffer')]",
+    "vmImageSku": "[parameters('vmImageSku')]",
+    "vmImageVersion": "[parameters('vmImageVersion')]",
+    ...
+  }
 }
 ```
 
@@ -328,18 +326,18 @@ To adjust the placement properties for a node type using an ARM Template, adjust
 * The Service Fabric managed cluster resource apiVersion should be **2021-05-01** or later.
 
 ```json
-     {
-            "apiVersion": "[variables('sfApiVersion')]",
-            "type": "Microsoft.ServiceFabric/managedclusters/nodetypes",
-            "name": "[concat(parameters('clusterName'), '/', parameters('nodeTypeName'))]",
-            "location": "[resourcegroup().location]",
-            "properties": {
-                "placementProperties": {
-                    "PremiumSSD": "true",
-                    "NodeColor": "green",
-                    "SomeProperty": "5"
-            }
-        }
+{
+  "apiVersion": "[variables('sfApiVersion')]",
+  "type": "Microsoft.ServiceFabric/managedclusters/nodetypes",
+  "name": "[concat(parameters('clusterName'), '/', parameters('nodeTypeName'))]",
+  "location": "[resourcegroup().location]",
+  "properties": {
+    "placementProperties": {
+      "PremiumSSD": "true",
+      "NodeColor": "green",
+      "SomeProperty": "5"
+    }
+  }
 }
 ```
 
@@ -359,20 +357,21 @@ Set-AzServiceFabricManagedNodeType -ResourceGroupName $rgName -ClusterName $clus
 To modify the VM SKU size used for a node type using an ARM Template, adjust the `vmSize` property with the new value and do a cluster deployment for the setting to take effect. The managed cluster provider will reimage each instance by upgrade domain.  For a list of SKU options, please refer to the [VM sizes - Azure Virtual Machines | Microsoft Learn](../virtual-machines/sizes.md).  
 
 ```json
-     {
-            "apiVersion": "[variables('sfApiVersion')]",
-            "type": "Microsoft.ServiceFabric/managedclusters/nodetypes",
-            "name": "[concat(parameters('clusterName'), '/', parameters('nodeTypeName'))]",
-            "location": "[resourcegroup().location]",
-            "properties": {
-                ...
-                "vmSize": "[parameters('vmImageVersion')]",
-                ...
-            }
-        }
+{
+  "apiVersion": "[variables('sfApiVersion')]",
+  "type": "Microsoft.ServiceFabric/managedclusters/nodetypes",
+  "name": "[concat(parameters('clusterName'), '/', parameters('nodeTypeName'))]",
+  "location": "[resourcegroup().location]",
+  "properties": {
+    ...
+    "vmSize": "[parameters('vmImageVersion')]",
+    ...
+  }
 }
 ```
+
 ## Configure multiple managed disks
+
 Service Fabric managed clusters by default configure one managed disk. By configuring the following optional property and values, you can add more managed disks to node types within a cluster. You are able to specify the drive letter, disk type, and size per disk.
 
 Configure more managed disks by declaring `additionalDataDisks` property and required parameters in your Resource Manager template as follows:
@@ -384,20 +383,20 @@ Configure more managed disks by declaring `additionalDataDisks` property and req
 * The Service Fabric managed cluster resource apiVersion should be **2022-01-01** or later.
 
 ```json
-     {
-            "apiVersion": "[variables('sfApiVersion')]",
-            "type": "Microsoft.ServiceFabric/managedclusters/nodetypes",
-            "name": "[concat(parameters('clusterName'), '/', parameters('nodeTypeName'))]",
-            "location": "[resourcegroup().location]",
-            "properties": {
-                "additionalDataDisks": {
-                    "lun": "1",
-                    "diskSizeGB": "50",
-                    "diskType": "Standard_LRS",
-                    "diskLetter": "S" 
-            }
-        }
-     }
+{
+  "apiVersion": "[variables('sfApiVersion')]",
+  "type": "Microsoft.ServiceFabric/managedclusters/nodetypes",
+  "name": "[concat(parameters('clusterName'), '/', parameters('nodeTypeName'))]",
+  "location": "[resourcegroup().location]",
+  "properties": {
+    "additionalDataDisks": {
+      "lun": "1",
+      "diskSizeGB": "50",
+      "diskType": "Standard_LRS",
+      "diskLetter": "S" 
+    }
+  }
+}
 ```
 
 See [full list of parameters available](/azure/templates/microsoft.servicefabric/2021-11-01-preview/managedclusters)
@@ -410,16 +409,17 @@ Service Fabric managed clusters by default configure a Service Fabric data disk
 * The Service Fabric managed cluster resource apiVersion should be **2022-01-01** or later.
 
 ```json
-     {
-            "apiVersion": "[variables('sfApiVersion')]",
-            "type": "Microsoft.ServiceFabric/managedclusters/nodetypes",
-            "name": "[concat(parameters('clusterName'), '/', parameters('nodeTypeName'))]",
-            "location": "[resourcegroup().location]",
-            "properties": {
-                "dataDiskLetter": "S"      
-            }
-        }
-     }
+{
+  {
+    "apiVersion": "[variables('sfApiVersion')]",
+    "type": "Microsoft.ServiceFabric/managedclusters/nodetypes",
+    "name": "[concat(parameters('clusterName'), '/', parameters('nodeTypeName'))]",
+    "location": "[resourcegroup().location]",
+    "properties": {
+      "dataDiskLetter": "S"
+    }
+  }
+}
 ```
 
 ## Next steps