Fixing disallowed html tags

Author: JasonWHowell

articles/iot-develop/tutorial-configure-tsi.md

@@ -205,11 +205,11 @@ Select the **Instances** tab. Find the instance that represents the device's wor
 
 ![Screenshot showing how to edit an instance.](./media/tutorial-configure-tsi/edit-instance.png)
 
-Open the **Type** drop-down menu and then select **Temperature Controller**. Enter *defaultComponent, <your device name>* to update the name of the instance that represents all top-level tags associated with your device.
+Open the **Type** drop-down menu and then select **Temperature Controller**. Enter *defaultComponent, \<your device name\>* to update the name of the instance that represents all top-level tags associated with your device.
 
 ![Screenshot showing how to change an instance type.](./media/tutorial-configure-tsi/change-type.png)
 
-Before you select **Save**, first select the **Instance Fields** tab, and then select **Device Fleet**. To group the telemetry together, enter *\<your device name> - Temp Controller*. Then select **Save**.
+Before you select **Save**, first select the **Instance Fields** tab, and then select **Device Fleet**. To group the telemetry together, enter *\<your device name\> - Temp Controller*. Then select **Save**.
 
 ![Screenshot showing how to assign an instance to a hierarchy](./media/tutorial-configure-tsi/assign-to-hierarchy.png)
 

articles/iot-hub-device-update/device-update-agent-provisioning.md

@@ -180,7 +180,7 @@ The Device Update agent can also be configured without the IoT Identity service
 
     1. You should see a window open with some text in it. Delete the entire string following 'connection_String=' the first-time you provision the Device Update agent on the IoT device. It is just place holder text.
 
-    1. In the terminal, replace <your-connection-string> with the connection string of the device for your instance of Device Update agent. Select Enter and then **Save.** It should look this example:
+    1. In the terminal, replace \<your-connection-string\> with the connection string of the device for your instance of Device Update agent. Select Enter and then **Save.** It should look this example:
 
         ```text
         connection_string=<ADD CONNECTION STRING HERE>

articles/logic-apps/logic-apps-batch-process-send-receive-messages.md

@@ -156,9 +156,9 @@ Now create one or more batch sender logic apps that send messages to the batch r
       > check that you previously created and deployed your batch receiver to Azure. If you haven't, learn 
       > [how to deploy your batch receiver logic app to Azure](../logic-apps/quickstart-create-logic-apps-with-visual-studio.md#deploy-logic-app-to-azure).
 
-   1. From the actions list, select this action: **Batch_messages - <*your-logic-app-name*>**
+   1. From the actions list, select this action: **Batch_messages - \<*your-logic-app-name*\>**
 
-      ![Select this action: "Batch_messages - <your-logic-app>"](./media/logic-apps-batch-process-send-receive-messages/batch-sender-select-batch.png)
+      ![Select this action: "Batch_messages - \<your-logic-app\>"](./media/logic-apps-batch-process-send-receive-messages/batch-sender-select-batch.png)
 
 1. Set the batch sender's properties:
 

articles/logic-apps/manage-logic-apps-with-visual-studio.md

@@ -124,7 +124,7 @@ To build logic apps for business-to-business (B2B) enterprise integration scenar
 
 1. In Visual Studio, open the Azure Resource Group project that contains your logic app.
 
-1. In Solution Explorer, open the **<logic-app-name>.json** file's shortcut menu, and select **Open With Logic App Designer**. (Keyboard: Ctrl + L)
+1. In Solution Explorer, open the **\<logic-app-name\>.json** file's shortcut menu, and select **Open With Logic App Designer**. (Keyboard: Ctrl + L)
 
    ![Open logic app's .json file with Logic App Designer](./media/manage-logic-apps-with-visual-studio/open-logic-app-designer.png)
 

articles/migrate/replicate-using-expressroute.md

@@ -6,7 +6,6 @@ ms.author: deseelam
 ms.manager: bsiva
 ms.topic: how-to
 ms.date: 02/22/2021
-
 ---
 
 # Replicate data over ExpressRoute with Azure Migrate: Server Migration
@@ -152,7 +151,7 @@ To validate the private link connection, perform a DNS resolution of the cache s
 
 An illustrative example for DNS resolution of the cache storage account. 
 
-- Enter nslookup _storageaccountname_.blob.core.windows.net. Replace <storage-account-name> with the name of the cache storage account created by Azure Migrate.  
+- Enter nslookup _storageaccountname_.blob.core.windows.net. Replace \<storage-account-name\> with the name of the cache storage account created by Azure Migrate.  
 
     You'll receive a message like this:  
 

articles/migrate/tutorial-migrate-aws-virtual-machines.md

@@ -136,7 +136,7 @@ The first step of migration is to set up the replication appliance. To set up th
 
 2. In **Discover machines** > **Are your machines virtualized?**, click **Not virtualized/Other**.
 3. In **Target region**, select the Azure region to which you want to migrate the machines.
-4. Select **Confirm that the target region for migration is <region-name>**.
+4. Select **Confirm that the target region for migration is \<region-name\>**.
 5. Click **Create resources**. This creates an Azure Site Recovery vault in the background.
     - If you've already set up migration with Azure Migrate Server Migration, the target option can't be configured, since resources were set up previously.
     - You can't change the target region for this project after clicking this button.

articles/network-watcher/network-watcher-nsg-flow-logging-powershell.md

@@ -2,22 +2,15 @@
 title: Manage NSG Flow logs - Azure PowerShell
 titleSuffix: Azure Network Watcher
 description: This page explains how to manage Network Security Group Flow logs in Azure Network Watcher with PowerShell
-services: network-watcher
-documentationcenter: na
 author: damendo
-
 ms.service: network-watcher
-ms.devlang: na
 ms.topic: how-to
-ms.tgt_pltfrm: na
 ms.workload:  infrastructure-services
 ms.date: 01/07/2021
 ms.author: damendo 
 ms.custom: devx-track-azurepowershell
-
 ---
 
-
 # Configuring Network Security Group Flow logs with PowerShell
 
 > [!div class="op_single_selector"]
@@ -33,7 +26,7 @@ The detailed specification of all NSG flow logs commands for various versions of
 > [!NOTE]
 > - The commands [Get-AzNetworkWatcherFlowLogStatus](/powershell/module/az.network/get-aznetworkwatcherflowlogstatus) and [Set-AzNetworkWatcherConfigFlowLog](/powershell/module/az.network/set-aznetworkwatcherconfigflowlog) used in this doc, requires an additional "reader" permission in the resource group of the network watcher. Also, these commands are old and may soon be deprecated.
 > - It is recommended to use the new [Get-AzNetworkWatcherFlowLog](/powershell/module/az.network/get-aznetworkwatcherflowlog) and [Set-AzNetworkWatcherFlowLog](/powershell/module/az.network/set-aznetworkwatcherflowlog) commands instead.
-> - The new [Get-AzNetworkWatcherFlowLog](/powershell/module/az.network/get-aznetworkwatcherflowlog) command offers four variants for flexibility. In case you are using the "Location <String>" variant of this command, an additional "reader" permission in the resource group of the network watcher would be required. For other variants, no additional permissions are required. 
+> - The new [Get-AzNetworkWatcherFlowLog](/powershell/module/az.network/get-aznetworkwatcherflowlog) command offers four variants for flexibility. In case you are using the "Location \<String\>" variant of this command, an additional "reader" permission in the resource group of the network watcher would be required. For other variants, no additional permissions are required. 
 
 ## Register Insights provider
 

articles/network-watcher/traffic-analytics-schema.md

@@ -1,16 +1,10 @@
 ---
 title: Azure traffic analytics schema | Microsoft Docs
 description: Understand schema of Traffic Analytics to analyze Azure network security group flow logs.
-services: network-watcher
-documentationcenter: na
 author: vinynigam
 manager: agummadi
-editor:
-
 ms.service: network-watcher
-ms.devlang: na
 ms.topic: article
-ms.tgt_pltfrm: na
 ms.workload:  infrastructure-services
 ms.date: 01/07/2021
 ms.author: vinigam
@@ -140,7 +134,7 @@ Listed below are the fields in the schema and what they signify
 | LocalNetworkGateway1_s | \<SubscriptionID>/\<ResourceGroupName>/\<LocalNetworkGatewayName> | Local network gateway associated with the Source IP in the flow |
 | LocalNetworkGateway2_s | \<SubscriptionID>/\<ResourceGroupName>/\<LocalNetworkGatewayName> | Local network gateway associated with the Destination IP in the flow |
 | ConnectionType_s | Possible values are VNetPeering, VpnGateway, and ExpressRoute |	Connection Type |
-| ConnectionName_s | \<SubscriptionID>/\<ResourceGroupName>/\<ConnectionName> | Connection Name. For flow type P2S, this will be formatted as <gateway name>_<VPN Client IP> |
+| ConnectionName_s | \<SubscriptionID>/\<ResourceGroupName>/\<ConnectionName> | Connection Name. For flow type P2S, this will be formatted as \<gateway name\>_\<VPN Client IP\> |
 | ConnectingVNets_s	| Space separated list of virtual network names | In case of hub and spoke topology, hub virtual networks will be populated here |
 | Country_s | Two letter country code (ISO 3166-1 alpha-2) | Populated for flow type ExternalPublic. All IP addresses in PublicIPs_s field will share the same country code |
 | AzureRegion_s | Azure region locations | Populated for flow type AzurePublic. All IP addresses in PublicIPs_s field will share the Azure region |

articles/search/search-howto-run-reset-indexers.md

@@ -2,7 +2,6 @@
 title: Run or reset indexers
 titleSuffix: Azure Cognitive Search
 description: Reset an indexer, skills, or individual documents to refresh all or part of and index or knowledge store.
-
 author: HeidiSteen
 manager: nitinme
 ms.author: heidist
@@ -41,7 +40,7 @@ Indexer execution is subject to the following limits:
 
 + Maximum number of indexer jobs is 1 per replica  No concurrent jobs.
 
-  If indexer execution is already at capacity,  you will get this notification: "Failed to run indexer '<indexer-name>', error: "Another indexer invocation is currently in progress; concurrent invocations are not allowed."
+  If indexer execution is already at capacity,  you will get this notification: "Failed to run indexer '\<indexer-name\>', error: "Another indexer invocation is currently in progress; concurrent invocations are not allowed."
 
 + Maximum running time is 2 hours if using a skillset, and 24 hours without. 
 

articles/security-center/secure-score-security-controls.md

@@ -96,23 +96,9 @@ We recommend every organization carefully review their assigned Azure Policy ini
 > For details of reviewing and editing your initiatives, see [Working with security policies](tutorial-security-policy.md). 
 
 Even though Security Center's default security initiative is based on industry best practices and standards, there are scenarios in which the built-in recommendations listed below might not completely fit your organization. Consequently, it'll sometimes be necessary to adjust the default initiative - without compromising security - to ensure it's aligned with your organization's own policies, industry standards, regulatory standards, and benchmarks you're obligated to meet.<br><br>
-<div class="foo">
-
-<style type="text/css">
-.tg  {border-collapse:collapse;border-spacing:0;}
-.tg td{border-color:black;border-style:solid;border-width:1px;font-family:Arial, sans-serif;font-size:14px;
-  overflow:hidden;padding:10px 5px;word-break:normal;}
-.tg th{border-color:black;border-style:solid;border-width:1px;font-family:Arial, sans-serif;font-size:18px;
-  font-weight:normal;overflow:hidden;padding:10px 5px;word-break:normal;}
-.tg .tg-cly1{text-align:left;vertical-align:middle}
-.tg .tg-lboi{border-color:inherit;text-align:left;vertical-align:middle}
-</style>
 
 [!INCLUDE [security-center-controls-and-recommendations](../../includes/asc/security-control-recommendations.md)]
 
-</div>
-
-
 
 
 ## FAQ - Secure score

articles/sentinel/ueba-enrichments.md

@@ -1,18 +1,10 @@
 ---
 title: Azure Sentinel UEBA enrichments reference | Microsoft Docs
 description: This article displays the entity enrichments generated by Azure Sentinel's entity behavior analytics.
-services: sentinel
-cloud: na
-documentationcenter: na
 author: yelevin
 manager: rkarlin
-
-ms.assetid:
 ms.service: azure-sentinel
 ms.subservice: azure-sentinel
-ms.workload: na
-ms.tgt_pltfrm: na
-ms.devlang: na
 ms.topic: reference
 ms.date: 05/10/2021
 ms.author: yelevin
@@ -195,7 +187,7 @@ The following tables describe the enrichments featured in the **ActivityInsights
 
 | Enrichment name | [Baseline](#baseline-explained) (days) | Description | Sample value |
 | --- | --- | --- | --- |
-| **Last time user performed action**<br>*(LastTimeUserPerformedAction)* | 180 | Last time the user performed the same action. | <Timestamp> |
+| **Last time user performed action**<br>*(LastTimeUserPerformedAction)* | 180 | Last time the user performed the same action. | \<Timestamp\> |
 | **Similar action wasn't performed in the past**<br>*(SimilarActionWasn'tPerformedInThePast)* | 30 | No action in the same resource provider was performed by the user. | True, False |
 | **Source IP location**<br>*(SourceIPLocation)* | *N/A* | The country resolved from the source IP of the action. | [Surrey, England] |
 | **Uncommon high volume of operations**<br>*(UncommonHighVolumeOfOperations)* | 7 | A user performed a burst of similar operations within the same provider | True, False |

articles/storsimple/storsimple-8000-support-options.md

@@ -107,7 +107,7 @@ StorSimple 8000 Series Storage Arrays support is provided based on how the StorS
 
 
 
-*<text> * Premium coverage is not available in all locations. Contact Microsoft at SSSupOps\@microsoft.com for geographical coverage before purchasing StorSimple Premium Support.*
+* Premium coverage is not available in all locations. Contact Microsoft at SSSupOps\@microsoft.com for geographical coverage before purchasing StorSimple Premium Support.*
 
 ***The StorSimple appliance must be deployed in a region where the customer is covered by Premier support in order to be eligible for a free upgrade to premium StorSimple support.*