Clean up metadata

Author: ecfan

articles/logic-apps/create-managed-service-identity.md

@@ -73,7 +73,7 @@ This article shows how to enable and set up the system-assigned identity or user
 
 ## Prerequisites
 
-* An Azure account and subscription. If you don't have a subscription, [sign up for a free Azure account](https://azure.microsoft.com/free/). Both the managed identity and the target Azure resource where you need access must use the same Azure subscription.
+* An Azure account and subscription. If you don't have a subscription, [sign up for a free Azure account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F). Both the managed identity and the target Azure resource where you need access must use the same Azure subscription.
 
 * To give a managed identity access to an Azure resource, you need to add a role to the target resource for that identity. To add roles, you need [Azure AD administrator permissions](../active-directory/roles/permissions-reference.md) that can assign roles to identities in the corresponding Azure AD tenant.
 

articles/logic-apps/create-monitoring-tracking-queries.md

@@ -1,10 +1,10 @@
 ---
 title: View and create queries for logic apps in Azure Monitor logs
-description: View and create queries in Azure Monitor logs for Azure Logic Apps
+description: View and create queries in Azure Monitor logs for Azure Logic Apps.
 services: logic-apps
 ms.suite: integration
-ms.reviewer: divswa, logicappspm
-ms.topic: article
+ms.reviewer: divswa, estfan, azla
+ms.topic: how-to
 ms.date: 01/30/2020
 ---
 
@@ -14,6 +14,8 @@ You can view the underlying queries that produce the results from [Azure Monitor
 
 ## Prerequisites
 
+* An Azure account and subscription. If you don't have a subscription, [sign up for a free Azure account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
+
 * A Log Analytics workspace. If you don't have a Log Analytics workspace, learn [how to create a Log Analytics workspace](../azure-monitor/logs/quick-create-workspace.md).
 
 * A logic app that's set up with Azure Monitor logging and sends that information to a Log Analytics workspace. Learn [how to set up Azure Monitor logs for your logic app](../logic-apps/monitor-logic-apps.md).

articles/logic-apps/custom-connector-overview.md

@@ -1,10 +1,10 @@
 ---
 title: Custom connector topic links
-description: Links to topics about how to create, use, share, and certify custom connectors
+description: Links to topics about how to create, use, share, and certify custom connectors in Azure Logic Apps.
 services: logic-apps
 ms.suite: integration
-ms.reviewer: divswa, logicappspm
-ms.topic: article
+ms.reviewer: divswa, azla
+ms.topic: conceptual
 ms.date: 1/30/2018
 ---
 

articles/logic-apps/customer-managed-keys-integration-service-environment.md

@@ -1,10 +1,10 @@
 ---
 title: Set up customer-managed keys to encrypt data at rest in ISEs
-description: Create and manage your own encryption keys to secure data at rest for integration service environments (ISEs) in Azure Logic Apps
+description: Create and manage your own encryption keys to secure data at rest for integration service environments (ISEs) in Azure Logic Apps.
 services: logic-apps
 ms.suite: integration
 ms.reviewer: mijos, rarayudu, azla
-ms.topic: conceptual
+ms.topic: how-to
 ms.date: 01/20/2021
 ---
 

articles/logic-apps/designer-overview.md

@@ -3,7 +3,7 @@ title: About single-tenant workflow designer
 description: Learn how the designer in single-tenant Azure Logic Apps helps you visually create workflows through the Azure portal. Discover the benefits and features in this latest version.
 services: logic-apps
 ms.suite: integration
-ms.reviewer: logicappspm
+ms.reviewer: estfan, azla
 ms.topic: conceptual
 ms.date: 06/30/2021
 ---

articles/logic-apps/estimate-storage-costs.md

@@ -19,7 +19,7 @@ Storage costs change based on your workflows' content. Different triggers, actio
 
 ## Prerequisites
 
-* An Azure account and subscription. If you don't have a subscription, [sign up for a free Azure account](https://azure.microsoft.com/free/).
+* An Azure account and subscription. If you don't have a subscription, [sign up for a free Azure account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
 
 * A single-tenant based logic Apps workflow. You can create a workflow [using the Azure portal](create-single-tenant-workflows-azure-portal.md) or [using Visual Studio Code](create-single-tenant-workflows-visual-studio-code.md). If you don't have a workflow yet, you can use the sample small, medium, and large workflows in the storage calculator.
 

articles/logic-apps/export-from-microsoft-flow-logic-app-template.md

@@ -1,10 +1,10 @@
 ---
 title: Export flows from Power Automate to Azure Logic Apps
-description: Migrate flows from Power Automate to Azure Logic Apps by exporting as Azure Resource Manager templates
+description: Migrate flows from Power Automate to Azure Logic Apps by exporting as Azure Resource Manager templates.
 services: logic-apps
 ms.suite: integration
-ms.reviewer: estfan, sneshaf, pinath, logicappspm
-ms.topic: conceptual
+ms.reviewer: estfan, sneshaf, pinath, azla
+ms.topic: how-to
 ms.date: 02/22/2021
 ---
 
@@ -26,7 +26,7 @@ Not all Power Automate connectors are available in Azure Logic Apps. You can mig
 
 ## Prerequisites
 
-* An Azure account and subscription. If you don't have an Azure subscription, [sign up for a free Azure account](https://azure.microsoft.com/free/).
+* An Azure account and subscription. If you don't have an Azure subscription, [sign up for a free Azure account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
 
 * The flow that you want to export from Power Automate
 

articles/logic-apps/handle-long-running-stored-procedures-sql-connector.md

@@ -1,10 +1,10 @@
 ---
 title: Handle long-running stored procedures in the SQL connector
-description: How to handle stored procedures that time out when using the SQL connector in Azure Logic Apps
+description: Handle stored procedures that time out when using the SQL connector in Azure Logic Apps.
 services: logic-apps
 ms.suite: integration
-ms.reviewer: camerost, logicappspm
-ms.topic: conceptual
+ms.reviewer: camerost, azla
+ms.topic: how-to
 ms.date: 10/27/2020
 ---
 

articles/logic-apps/handle-throttling-problems-429-errors.md

@@ -1,10 +1,10 @@
 ---
 title: Handle throttling problems, or '429 - Too many requests' errors
-description: How to work around throttling problems, or 'HTTP 429 Too many requests' errors, in Azure Logic Apps
+description: How to work around throttling problems or 'HTTP 429 Too many requests' errors in Azure Logic Apps.
 services: logic-apps
 ms.suite: integration
-ms.reviewer: deli, logicappspm
-ms.topic: conceptual
+ms.reviewer: deli, azla
+ms.topic: how-to
 ms.date: 04/13/2020
 ---
 
@@ -90,15 +90,15 @@ To handle throttling at this level, you have these options:
 
   For this option, consider whether you can distribute the workload by dividing an action's requests across multiple connections to the same destination using the same credentials.
 
-  For example, suppose that your logic app gets tables from a SQL Server database and then gets the rows from each table. Based on the number of rows that you have to process, you can use multiple connections and multiple **For each** loops to divide the total number of rows into smaller sets for processing. This scenario uses two **For each** loops to split the total number of rows in half. The first **For each** loop uses an expression that gets the first half. The other **For each** loop uses a different expression that gets the second half, for example:<p>
+  For example, suppose that your logic app gets tables from a SQL Server database and then gets the rows from each table. Based on the number of rows that you have to process, you can use multiple connections and multiple **For each** loops to divide the total number of rows into smaller sets for processing. This scenario uses two **For each** loops to split the total number of rows in half. The first **For each** loop uses an expression that gets the first half. The other **For each** loop uses a different expression that gets the second half, for example:<br><br>
 
-    * Expression 1: The `take()` function gets the front of a collection. For more information, see the [**`take()`** function](workflow-definition-language-functions-reference.md#take).
+  * Expression 1: The `take()` function gets the front of a collection. For more information, see the [**`take()`** function](workflow-definition-language-functions-reference.md#take).
 
-      `@take(collection-or-array-name, div(length(collection-or-array-name), 2))`
+    `@take(collection-or-array-name, div(length(collection-or-array-name), 2))`
 
-    * Expression 2: The `skip()` function removes the front of a collection and returns all the other items. For more information, see the [**`skip()`** function](workflow-definition-language-functions-reference.md#skip).
+  * Expression 2: The `skip()` function removes the front of a collection and returns all the other items. For more information, see the [**`skip()`** function](workflow-definition-language-functions-reference.md#skip).
 
-      `@skip(collection-or-array-name, div(length(collection-or-array-name), 2))`
+    `@skip(collection-or-array-name, div(length(collection-or-array-name), 2))`
 
     Here's a visual example that shows how you can use these expressions:
 

articles/logic-apps/healthy-unhealthy-resource.md

@@ -3,8 +3,8 @@ title: Set up logging to monitor logic apps in Azure Security Center
 description: Monitor the health of your Logic Apps resources in Azure Security Center by setting up diagnostic logging. 
 services: logic-apps
 ms.suite: integration
-ms.reviewer: estfan, logicappspm
-ms.topic: conceptual
+ms.reviewer: estfan, azla
+ms.topic: how-to
 ms.date: 12/07/2020
 ---
 
@@ -17,8 +17,10 @@ When you monitor your Logic Apps resources in [Microsoft Azure Security Center](
 
 ## Prerequisites
 
-* An Azure subscription. If you don't have a subscription, [create a free Azure account](https://azure.microsoft.com/free/) before you start.
+* An Azure subscription. If you don't have a subscription, [create a free Azure account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
+
 * Existing logic apps with [diagnostic logging enabled](#enable-diagnostic-logging).
+
 * A Log Analytics workspace, which is required to enable logging for your logic app. If you don't have a workspace, first [create your workspace](../azure-monitor/logs/quick-create-workspace.md).
 
 ## Enable diagnostic logging