Merge pull request #246712 from alexbuckgit/alexbuckgit/docutune-autopr-20230729-210510-4334702-ignore-build

[BULK] DocuTune - Fix formatting issues (part 7)

Author: ttorble

articles/dms/howto-sql-server-to-azure-sql-managed-instance-powershell-offline.md

@@ -86,7 +86,7 @@ $vSubNet = Get-AzVirtualNetworkSubnetConfig -VirtualNetwork $vNet -Name MySubnet
 $service = New-AzDms -ResourceGroupName myResourceGroup `
   -ServiceName MyDMS `
   -Location EastUS `
-  -Sku Basic_2vCores `  
+  -Sku Basic_2vCores `
   -VirtualSubnetId $vSubNet.Id`
 ```
 
@@ -200,7 +200,7 @@ foreach($DataBase in $Databases.Database_Name)
     {
       $SourceDB=$DataBase
       $TargetDB=$DataBase
-      
+
 $selectedDbs += New-AzureRmDmsSelectedDB -MigrateSqlServerSqlDbMi `
                                               -Name $SourceDB `
                                               -TargetDatabaseName $TargetDB `
@@ -252,11 +252,11 @@ Use the `New-AzDataMigrationTask` cmdlet to create and start a migration task.
 
 The `New-AzDataMigrationTask` cmdlet expects the following parameters:
 
-* *TaskType*. Type of migration task to create for SQL Server to Azure SQL Managed Instance migration type *MigrateSqlServerSqlDbMi* is expected. 
+* *TaskType*. Type of migration task to create for SQL Server to Azure SQL Managed Instance migration type *MigrateSqlServerSqlDbMi* is expected.
 * *Resource Group Name*. Name of Azure resource group in which to create the task.
 * *ServiceName*. Azure Database Migration Service instance in which to create the task.
-* *ProjectName*. Name of Azure Database Migration Service project in which to create the task. 
-* *TaskName*. Name of task to be created. 
+* *ProjectName*. Name of Azure Database Migration Service project in which to create the task.
+* *TaskName*. Name of task to be created.
 * *SourceConnection*. AzDmsConnInfo object representing source SQL Server connection.
 * *TargetConnection*. AzDmsConnInfo object representing target Azure SQL Managed Instance connection.
 * *SourceCred*. [PSCredential](/dotnet/api/system.management.automation.pscredential) object for connecting to source server.
@@ -302,12 +302,12 @@ To monitor the migration, perform the following tasks.
     To combine migration details such as properties, state, and database information associated with the migration, use the following code snippet:
 
     ```powershell
-    $CheckTask= Get-AzDataMigrationTask 	-ResourceGroupName myResourceGroup `
-                                        	-ServiceName $service.Name `
-                                       	-ProjectName $project.Name `
-                                        	-Name myDMSTask `
-                                        	-ResultType DatabaseLevelOutput `
-    					-Expand 
+    $CheckTask = Get-AzDataMigrationTask -ResourceGroupName myResourceGroup `
+                                         -ServiceName $service.Name `
+                                         -ProjectName $project.Name `
+                                         -Name myDMSTask `
+                                         -ResultType DatabaseLevelOutput `
+                                         -Expand
     Write-Host ‘$CheckTask.ProjectTask.Properties.Output’
     ```
 
@@ -321,11 +321,11 @@ To monitor the migration, perform the following tasks.
       Write-Host "migration task running"
     }
     else if($CheckTask.ProjectTask.Properties.State -eq "Succeeded")
-    { 
+    {
       Write-Host "Migration task is completed Successfully"
     }
     else if($CheckTask.ProjectTask.Properties.State -eq "Failed" -or $CheckTask.ProjectTask.Properties.State -eq "FailedInputValidation" -or $CheckTask.ProjectTask.Properties.State -eq "Faulted")
-    { 
+    {
       Write-Host "Migration Task Failed"
     }
     ```

articles/dns/dns-operations-recordsets.md

@@ -206,21 +206,21 @@ To add a record to an existing record set, follow the following three steps:
 
 1. Get the existing record set
 
-	```azurepowershell-interactive
-	$rs = Get-AzDnsRecordSet -Name www –ZoneName "contoso.com" -ResourceGroupName "MyResourceGroup" -RecordType A
-	```
+    ```azurepowershell-interactive
+    $rs = Get-AzDnsRecordSet -Name www –ZoneName "contoso.com" -ResourceGroupName "MyResourceGroup" -RecordType A
+    ```
 
 1. Add the new record to the local record set.
 
-	```azurepowershell-interactive
-	Add-AzDnsRecordConfig -RecordSet $rs -Ipv4Address "5.6.7.8"
-	```
+    ```azurepowershell-interactive
+    Add-AzDnsRecordConfig -RecordSet $rs -Ipv4Address "5.6.7.8"
+    ```
 
 3. Update the changes so it reflects to the Azure DNS service. 
 
-	```azurepowershell-interactive
-	Set-AzDnsRecordSet -RecordSet $rs
-	```
+    ```azurepowershell-interactive
+    Set-AzDnsRecordSet -RecordSet $rs
+    ```
 
 Using `Set-AzDnsRecordSet` *replaces* the existing record set in Azure DNS (and all records it contains) with the record set specified. [Etag checks](dns-zones-records.md#etags) are used to ensure concurrent changes aren't overwritten. You can use the optional `-Overwrite` switch to suppress these checks.
 
@@ -240,21 +240,21 @@ The process to remove a record from a record set is similar to the process to ad
 
 1. Get the existing record set
 
-	```azurepowershell-interactive
-	$rs = Get-AzDnsRecordSet -Name www –ZoneName "contoso.com" -ResourceGroupName "MyResourceGroup" -RecordType A
-	```
+    ```azurepowershell-interactive
+    $rs = Get-AzDnsRecordSet -Name www –ZoneName "contoso.com" -ResourceGroupName "MyResourceGroup" -RecordType A
+    ```
 
 2. Remove the record from the local record set object. The record that's being removed must be an exact match with an existing record across all parameters.
 
-	```azurepowershell-interactive
-	Remove-AzDnsRecordConfig -RecordSet $rs -Ipv4Address "5.6.7.8"
-	```
+    ```azurepowershell-interactive
+    Remove-AzDnsRecordConfig -RecordSet $rs -Ipv4Address "5.6.7.8"
+    ```
 
 3. Commit the change back to the Azure DNS service. Use the optional `-Overwrite` switch to suppress [Etag checks](dns-zones-records.md#etags) for concurrent changes.
 
-	```azurepowershell-interactive
-	Set-AzDnsRecordSet -RecordSet $Rs
-	```
+    ```azurepowershell-interactive
+    Set-AzDnsRecordSet -RecordSet $Rs
+    ```
 
 Using the above sequence to remove the last record from a record set doesn't delete the record set, rather it leaves an empty record set. To remove a record set entirely, see [Delete a record set](#delete-a-record-set).
 

articles/event-grid/auth0-log-stream-blob-storage.md

@@ -6,7 +6,7 @@ ms.date: 10/12/2022
 ---
 
 # Send Auth0 events to Azure Blob Storage
-This article shows you how to send Auth0 events to Azure Blob Storage via Azure Event Grid by using Azure Functions. 
+This article shows you how to send Auth0 events to Azure Blob Storage via Azure Event Grid by using Azure Functions.
 
 ## Prerequisites
 - [Create an Azure Event Grid stream on Auth0](https://marketplace.auth0.com/integrations/azure-log-streaming).
@@ -15,57 +15,57 @@ This article shows you how to send Auth0 events to Azure Blob Storage via Azure
 
 ## Create an Azure function
 1. Create an Azure function by following instructions from the **Create a local project** section of [Quickstart: Create a JavaScript function in Azure using Visual Studio Code](../azure-functions/create-first-function-vs-code-node.md?pivots=nodejs-model-v3).
-    1. Select **Azure Event Grid trigger** for the function template instead of **HTTP trigger** as mentioned in the quickstart. 
-    1. Continue to follow the steps, but use the following **index.js** and **function.json** files. 
-
-        > [!IMPORTANT]
-        > Update the **package.json** to include `@azure/storage-blob` as a dependency.
-    
-        **function.json**
-        ```json
-        {
-        	"bindings": [{
-        			"type": "eventGridTrigger",
-        			"name": "eventGridEvent",
-        			"direction": "in"
-        
-        		},
-        		{
-        			"type": "blob",
-        			"name": "outputBlob",
-        			"path": "events/{rand-guid}.json",
-        			"connection": "OUTPUT_STORAGE_ACCOUNT",
-        			"direction": "out"
-        
-        		}
-        	]
-        }
-        ```
-    
-        **index.js**
-    
-        ```javascript
-        // Event Grid always sends an array of data and may send more
-        // than one event in the array. The runtime invokes this function
-        // once for each array element, so we are always dealing with one.
-        // See: https://docs.microsoft.com/en-us/azure/azure-functions/functions-bindings-event-grid-trigger?tabs=
-        module.exports = async function (context, eventGridEvent) {
-            context.log(JSON.stringify(context.bindings));
-            context.log(JSON.stringify(context.bindingData));
-        
-            context.bindings.outputBlob = JSON.stringify(eventGridEvent);
-        };
-        ```    
+   1. Select **Azure Event Grid trigger** for the function template instead of **HTTP trigger** as mentioned in the quickstart.
+   1. Continue to follow the steps, but use the following **index.js** and **function.json** files.
+
+      > [!IMPORTANT]
+      > Update the **package.json** to include `@azure/storage-blob` as a dependency.
+
+      **function.json**
+
+      ```json
+      {
+        "bindings": [
+          {
+            "type": "eventGridTrigger",
+            "name": "eventGridEvent",
+            "direction": "in"
+          },
+          {
+            "type": "blob",
+            "name": "outputBlob",
+            "path": "events/{rand-guid}.json",
+            "connection": "OUTPUT_STORAGE_ACCOUNT",
+            "direction": "out"
+          }
+        ]
+      }
+      ```
+
+      **index.js**
+
+      ```javascript
+      // Event Grid always sends an array of data and may send more
+      // than one event in the array. The runtime invokes this function
+      // once for each array element, so we are always dealing with one.
+      // See: https://docs.microsoft.com/en-us/azure/azure-functions/functions-bindings-event-grid-trigger?tabs=
+      module.exports = async function (context, eventGridEvent) {
+          context.log(JSON.stringify(context.bindings));
+          context.log(JSON.stringify(context.bindingData));
+
+          context.bindings.outputBlob = JSON.stringify(eventGridEvent);
+      };
+      ```
+
 1. Create an Azure function app using instructions from [Quick function app create](../azure-functions/functions-develop-vs-code.md?tabs=csharp#quick-function-app-create).
 1. Deploy your function to the function app on Azure using instructions from [Deploy project files](../azure-functions/functions-develop-vs-code.md?tabs=csharp#republish-project-files).
 
-     
 ## Configure Azure function to use your blob storage
 1. Configure your Azure function to use your storage account.
     1. Select **Configuration** under **Settings** on the left menu.
-    1. On the **Application settings** page, select **+ New connection string** on the command bar. 
+    1. On the **Application settings** page, select **+ New connection string** on the command bar.
     1. Set **Name** to **AzureWebJobsOUTPUT_STORAGE_ACCOUNT**.
-    1. Set **Value** to the connection string to the storage account that you copied to the clipboard in the previous step. 
+    1. Set **Value** to the connection string to the storage account that you copied to the clipboard in the previous step.
     1. Select **OK**.
 
 ## Create event subscription for partner topic using function
@@ -76,26 +76,26 @@ This article shows you how to send Auth0 events to Azure Blob Storage via Azure
 1. On the **Create Event Subscription** page, follow these steps:
     1. Enter a **name** for the event subscription.
     1. For **Endpoint type**, select **Azure Function**.
-    
+
         :::image type="content" source="./media/auth0-log-stream-blob-storage/select-endpoint-type.png" alt-text="Screenshot showing the Create Event Subscription page with Azure Functions selected as the endpoint type.":::
-    1. Click **Select an endpoint** to specify details about the function. 
+    1. Click **Select an endpoint** to specify details about the function.
 1. On the **Select Azure Function** page, follow these steps.
     1. Select the **Azure subscription** that contains the function.
     1. Select the **resource group** that contains the function.
     1. Select your **function app**.
     1. Select your **Azure function**.
-    1. Then, select **Confirm Selection**. 
-1. Now, back on the **Create Event Subscription** page, select **Create** to create the event subscription. 
+    1. Then, select **Confirm Selection**.
+1. Now, back on the **Create Event Subscription** page, select **Create** to create the event subscription.
 1. After the event subscription is created successfully, you see the event subscription in the bottom pane of the **Event Grid Partner Topic - Overview** page.
-1. Select the link to your Azure function at the bottom of the page. 
+1. Select the link to your Azure function at the bottom of the page.
 1. On the **Azure Function** page, select **Monitor** and confirm data is successfully being sent. You may need to trigger logs from Auth0.
 
 ## Verify that logs are stored in the storage account
 
 1. Locate your storage account in the Azure portal.
 1. Select **Containers** under **Data Storage** on the left menu.
-1. Confirm that you see a container named **events**. 
-1. Select the container and verify that your Auth0 logs are being stored. 
+1. Confirm that you see a container named **events**.
+1. Select the container and verify that your Auth0 logs are being stored.
 
     > [!NOTE]
     > You can use steps in the article to handle events from other event sources too. For a generic example of sending Event Grid events to Azure Blob Storage or Azure Monitor Application Insights, see [this example on GitHub](https://github.com/awkwardindustries/azure-monitor-handler).