Merge pull request #268156 from alexbuckgit/alexbuckgit/docutune-autopr-20240305-201911-3642454-ignore-build

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

Author: prmerger-automator[bot]

articles/azure-resource-manager/templates/quickstart-create-template-specs.md

@@ -443,11 +443,11 @@ Rather than creating a new template spec for the revised template, add a new ver
 1. Deploy that version. Provide a prefix for the storage account name.
 
    ```azurecli
-    az deployment group create \
+   az deployment group create \
       --resource-group storageRG \
       --template-spec $id \
       --parameters namePrefix='demoaccount'
-    ```
+   ```
 
 # [Portal](#tab/azure-portal)
 
@@ -478,7 +478,7 @@ Rather than creating a new template spec for the revised template, add a new ver
 
 1. Again, you must make some changes to your local template to make it work with template specs. Copy the following template and save it locally as azuredeploy.json.
 
-   ```json
+    ```json
     {
       "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
       "contentVersion": "1.0.0.0",

articles/backup/azure-kubernetes-service-cluster-backup-using-cli.md

@@ -197,15 +197,13 @@ Once the vault and policy creation are complete, you need to perform the followi
 
    ```azurecli
    az k8s-extension create --name azure-aks-backup --extension-type microsoft.dataprotection.kubernetes --scope cluster --cluster-type managedClusters --cluster-name $akscluster --resource-group $aksclusterresourcegroup --release-train stable --configuration-settings blobContainer=$blobcontainer storageAccount=$storageaccount storageAccountResourceGroup=$storageaccountresourcegroup storageAccountSubscriptionId=$subscriptionId
-	
    ```
 
    As part of extension installation, a user identity is created in the AKS cluster's Node Pool Resource Group. For the extension to access the storage account, you need to provide this identity the **Storage Blob Data Contributor** role. To assign the required role, run the following command:
 
    ```azurecli
    az role assignment create --assignee-object-id $(az k8s-extension show --name azure-aks-backup --cluster-name $akscluster --resource-group $aksclusterresourcegroup --cluster-type managedClusters --query aksAssignedIdentity.principalId --output tsv) --role 'Storage Blob Data Contributor' --scope /subscriptions/$subscriptionId/resourceGroups/$storageaccountresourcegroup/providers/Microsoft.Storage/storageAccounts/$storageaccount
    ```
- 
 
 3. **Enable Trusted Access**
 

articles/backup/backup-azure-arm-restore-vms.md

@@ -320,22 +320,23 @@ If you choose to select system-assigned or user-assigned managed identities, che
 
 ```json
 "permissions": [
-            {
-                "actions": [
-                    "Microsoft.Authorization/*/read",
-                    "Microsoft.Storage/storageAccounts/blobServices/containers/delete",
-                    "Microsoft.Storage/storageAccounts/blobServices/containers/read",
-                    "Microsoft.Storage/storageAccounts/blobServices/containers/write"
-                ],
-                "notActions": [],
-                "dataActions": [
-                    "Microsoft.Storage/storageAccounts/blobServices/containers/blobs/delete",
-                    "Microsoft.Storage/storageAccounts/blobServices/containers/blobs/read",
-                    "Microsoft.Storage/storageAccounts/blobServices/containers/blobs/write",
-                    "Microsoft.Storage/storageAccounts/blobServices/containers/blobs/add/action"
-                ],
-                "notDataActions": []
-            }
+  {
+    "actions": [
+        "Microsoft.Authorization/*/read",
+        "Microsoft.Storage/storageAccounts/blobServices/containers/delete",
+        "Microsoft.Storage/storageAccounts/blobServices/containers/read",
+        "Microsoft.Storage/storageAccounts/blobServices/containers/write"
+    ],
+    "notActions": [],
+    "dataActions": [
+      "Microsoft.Storage/storageAccounts/blobServices/containers/blobs/delete",
+      "Microsoft.Storage/storageAccounts/blobServices/containers/blobs/read",
+      "Microsoft.Storage/storageAccounts/blobServices/containers/blobs/write",
+      "Microsoft.Storage/storageAccounts/blobServices/containers/blobs/add/action"
+    ],
+    "notDataActions": []
+  }
+]
 ```
 
 Or, add the role assignment on the staging location (Storage Account) to have [Storage account Backup Contributor](./blob-backup-configure-manage.md#grant-permissions-to-the-backup-vault-on-storage-accounts) and [Storage Blob data Contributor](../role-based-access-control/built-in-roles.md#storage-blob-data-contributor) for the successful restore operation.
@@ -384,7 +385,7 @@ There are a few things to note after restoring a VM:
   - Manually install VM agent if Azure Agent is found to be unresponsive by following this [link](/troubleshoot/azure/virtual-machines/install-vm-agent-offline).
   - Enable Serial Console access on VM to allow command-line access to VM
 
-  ```cmd
+    ```cmd
     bcdedit /store <drive letter>:\boot\bcd /enum
     bcdedit /store <VOLUME LETTER WHERE THE BCD FOLDER IS>:\boot\bcd /set {bootmgr} displaybootmenu yes
     bcdedit /store <VOLUME LETTER WHERE THE BCD FOLDER IS>:\boot\bcd /set {bootmgr} timeout 5

articles/backup/backup-azure-sql-database.md

@@ -166,14 +166,13 @@ To configure simultaneous backups, follow these steps:
 
      The final JSON should appear as:
 
-     ```JSON
+     ```json
      {
-             "EnableLocalDiskBackupForBackupTypes": ["Log"],
-             "LocalDiskBackupFolderPath": "E:\\LocalBackup",
+        "EnableLocalDiskBackupForBackupTypes": ["Log"],
+        "LocalDiskBackupFolderPath": "E:\\LocalBackup",
      }
-	 
-     ```	 
- 
+     ```
+
      If there are other pre-populated entries in the JSON file, add the above two entries at the bottom of the JSON file *just before the closing curly bracket*.
 
 3. For the changes to take effect immediately instead of regular one hour, go to **TaskManager** > **Services**, right-click **AzureWLbackupPluginSvc** and select **Stop**.
@@ -197,15 +196,14 @@ To configure simultaneous backups, follow these steps:
    ```azurepowershell
    $cred = Get-Credential
    New-SmbGlobalMapping -RemotePath <FileSharePath> -Credential $cred -LocalPath <LocalDrive>:  -FullAccess @("<Comma Separated list of accounts>") -Persistent $true
-   
    ```
 
    **Example**:
 
    ```azurepowershell
    $cred = Get-Credential
    New-SmbGlobalMapping -RemotePath \\i00601p1imsa01.file.core.windows.net\rsvshare -Credential $cred -LocalPath Y:  -FullAccess @("NT AUTHORITY\SYSTEM","NT Service\AzureWLBackupPluginSvc") -Persistent $true
-    ```
+   ```
 
 ## Next steps
 

articles/batch/account-move.md

@@ -57,16 +57,16 @@ Load and modify the template so you can create a new Batch account in the target
 
 1. In the uploaded **template.json** file, name the target Batch account by entering a new **defaultValue** for the Batch account name. This example sets the **defaultValue** of the Batch account name to `mytargetaccount` and replaces the string in **defaultValue** with the resource ID for `mytargetstorageaccount`.
 
-    ```json
-    {
-        "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
-        "contentVersion": "1.0.0.0",
-        "parameters": {
-            "batchAccounts_mysourceaccount_name": {
-                "defaultValue": "mytargetaccount",
-                "type": "String"
-            }
-        },
+   ```json
+   {
+       "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
+       "contentVersion": "1.0.0.0",
+       "parameters": {
+           "batchAccounts_mysourceaccount_name": {
+               "defaultValue": "mytargetaccount",
+               "type": "String"
+           }
+       },
    ```
 
 1. Next, update the **defaultValue** of the storage account with your migrated storage account's resource ID. To get this value, navigate to the storage account in the Azure portal, select **JSON View** near the top fo the screen, and then copy the value shown under **Resource ID**. This example uses the resource ID for a storage account named `mytargetstorageaccount` in the resource group `mytargetresourcegroup`.

articles/batch/batch-js-get-started.md

@@ -262,8 +262,8 @@ var jobPrepTaskConfig = {id:"installprereq",commandLine:"sudo sh startup_prereq.
 
 If there are no prerequisites to be installed for your tasks to run, you can skip the preparation tasks. Following code creates a job with display name "process csv files."
 
- ```javascript
- // Setting Batch Pool ID
+```javascript
+// Setting Batch Pool ID
 const poolInfo = { poolId: poolId };
 // Batch job configuration object
 const jobId = "processcsvjob";
@@ -273,13 +273,14 @@ const jobConfig = {
     jobPreparationTask: jobPrepTaskConfig,
     poolInfo: poolInfo
 };
- // Adding Azure batch job to the pool
- const job = batchClient.job.add(jobConfig, function (error, result) {
+// Adding Azure batch job to the pool
+const job = batchClient.job.add(jobConfig, function (error, result) {
         if (error !== null) {
             console.log("An error occurred while creating the job...");
             console.log(error.response);
         }
-    });
+    }
+);
 ```
 
 ### Step 5: Submit Azure Batch tasks for a job