Refresh edits

Author: ecfan

articles/connectors/built-in.md

@@ -1,12 +1,14 @@
 ---
-title: Built-in connector overview
+title: Built-In Connectors Overview
 description: Learn about connectors that run natively with the runtime in Azure Logic Apps.
 services: logic-apps
 ms.suite: integration
-ms.reviewer: estfan, azla
+ms.reviewers: estfan, azla
 ms.topic: concept-article
+ms.update-cycle: 1095-days
+ms.date: 03/09/2026
 ms.custom: engagement-fy23
-ms.date: 03/18/2025
+#Customer intent: As an integration developer who works with Azure Logic Apps, I want to learn about built-in connectors, which directly run alongside the runtime to provide better performance and throughput, compared to their counterparts that run in multitenant Azure.
 ---
 
 # Built-in connectors in Azure Logic Apps
@@ -486,10 +488,9 @@ For more information, review the following documentation:
     :::column-end:::
 :::row-end:::
 
-## Next steps
+## Related content
 
-> [!div class="nextstepaction"]
-> [Create custom APIs that you can call from Azure Logic Apps](../logic-apps/logic-apps-create-api-app.md)
+- [Create custom APIs that you can call from Azure Logic Apps](../logic-apps/logic-apps-create-api-app.md)
 
 <!-- Built-in icons -->
 [azure-ai-search-icon]: ./media/apis-list/azure-ai-search.png

articles/connectors/connectors-azure-application-insights.md

@@ -3,25 +3,22 @@ title: Connect to Azure Application Insights
 description: Connect to Application Insights from a workflow in Azure Logic Apps.
 services: logic-apps
 ms.suite: integration
-ms.reviewer: estfan, azla
+ms.reviewers: estfan, azla
 ms.topic: how-to
-ms.date: 03/21/2025
-# Customer intent: As a developer, I want to get telemetry from an Application Insights resource to use with my workflow in Azure Logic Apps.
+ms.update-cycle: 1095-days
+ms.date: 03/10/2026
+# Customer intent: As an integration developer who works with Azure Logic Apps, I want to get telemetry from an Application Insights resource to use with my workflow in Azure Logic Apps.
 ---
 
 # Connect to Azure Application Insights from workflows in Azure Logic Apps
 
 > [!NOTE]
 > 
-> The [Azure Monitor Logs connector](/connectors/azuremonitorlogs/) replaces the [Azure Log Analytics connector](/connectors/azureloganalytics/) 
-> and the [Azure Application Insights connector](/connectors/applicationinsights/). This combined connector provides the same functionality as 
-> the other connectors and is the preferred method for running a query against a Log Analytics workspace or an Application Insights resource.
+> The [Azure Monitor Logs connector](/connectors/azuremonitorlogs/) replaces both the [Azure Application Insights connector](/connectors/applicationinsights/) and the [Azure Log Analytics connector](/connectors/azureloganalytics/). This combined connector provides the same functionality as the other connectors and is the preferred way to run a query against an Application Insights resource or Log Analytics workspace.
 > 
-> For example, when you connect to your Application Insights resource, you don't have to create or provide an application ID and API key. 
-> Authentication is integrated with Microsoft Entra ID. For the how-to guide to use the Azure Monitor Logs connector, see 
-> [Connect to Log Analytics or Application Insights from workflows in Azure Logic Apps](connectors-azure-monitor-logs.md).
+> For example, when you connect to your Application Insights resource, you don't have to create or provide an application ID and API key. Authentication is integrated with Microsoft Entra ID. For the how-to guide to use the Azure Monitor Logs connector, see [Connect to Log Analytics or Application Insights from workflows in Azure Logic Apps](connectors-azure-monitor-logs.md).
 
-For more information, see the following documentation:
+For more information, see:
 
 - [Azure Monitor Logs connector](/connectors/azuremonitorlogs/)
 - [Connect to Log Analytics or Application Insights from workflows in Azure Logic Apps](connectors-azure-monitor-logs.md)

articles/connectors/connectors-create-api-cosmos-db.md

@@ -5,13 +5,15 @@ services: logic-apps
 ms.suite: integration
 author: jcocchi
 ms.author: jucocchi
-ms.reviewer: estfan, azla
+ms.reviewers: estfan, azla
 ms.topic: how-to
-ms.date: 04/15/2025
+ms.update-cycle: 365-days
+ms.date: 03/10/2026
 ms.custom: sfi-image-nochange
+# Customer intent: As an integration developer who works with Azure Logic Apps, I want to access and manage documents in Azure Cosmos DB from my workflows.
 ---
 
-# Access, create, or process documents in Azure Cosmos DB with workflows in Azure Logic Apps
+# Access, create, or process documents in Azure Cosmos DB from workflows in Azure Logic Apps
 
 [!INCLUDE [logic-apps-sku-consumption-standard](../../includes/logic-apps-sku-consumption-standard.md)]
 
@@ -27,7 +29,7 @@ You can connect to Azure Cosmos DB from both Consumption and Standard logic app
 
 ## 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/pricing/purchase-options/azure-account?cid=msft_learn).
+- An Azure account and subscription. [Get a free Azure account](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn).
 
 - An [Azure Cosmos DB account](/azure/cosmos-db/sql/create-cosmosdb-resources-portal).
 

articles/connectors/introduction.md

@@ -1,12 +1,13 @@
 ---
-title: What are connectors
+title: What are Connectors
 description: Learn how connectors in Azure Logic Apps help you access data, events, and resources in other apps, services, and systems from workflows.
 services: logic-apps
 ms.suite: integration
-ms.reviewer: estfan, azla
+ms.reviewers: estfan, azla
 ms.topic: concept-article
-ms.date: 03/27/2025
-# Customer intent: As a developer, I want to learn how connectors help me access data, events, and resources in other apps, services, systems, and platforms from my workflow in Azure Logic Apps.
+ms.update-cycle: 1095-days
+ms.date: 03/09/2026
+#Customer intent: As an integration developer who works with Azure Logic Apps, I want to learn how connectors provide access to data, events, and resources in other services, systems, apps, and ecosystems from my logic app workflows.
 ---
 
 # What are connectors in Azure Logic Apps

articles/connectors/managed.md

@@ -1,12 +1,14 @@
 ---
-title: Managed connector overview
+title: Managed Connectors Overview
 description: Learn about Microsoft-managed connectors hosted on Azure in Azure Logic Apps.
 services: logic-apps
 ms.suite: integration
-ms.reviewer: estfan, azla
+ms.reviewers: estfan, azla
 ms.topic: concept-article
+ms.update-cycle: 1095-days
+ms.date: 03/09/2026
 ms.custom: engagement-fy23
-ms.date: 06/01/2025
+#Customer intent: As an integration developer who works with Azure Logic Apps, I want to learn about shared connectors, which run in multitenant Azure, and how they differ from built-in counterparts that run alongside the runtime in Azure Logic Apps.
 ---
 
 # Managed connectors in Azure Logic Apps
@@ -15,21 +17,24 @@ Managed connectors provide ways for you to access other services and systems whe
 
 For a smaller number of services, systems and protocols, Azure Logic Apps provides a built-in version alongside the managed version. The number and range of built-in connectors vary based on whether you create a Consumption logic app workflow that runs in multitenant Azure Logic Apps or a Standard logic app workflow that runs in single-tenant Azure Logic Apps. In most cases, the built-in version provides better performance, capabilities, pricing, and so on. In a few cases, some built-in connectors are available only in one logic app workflow type, and not the other.
 
-For example, a Standard workflow can use both managed connectors and built-in connectors for Azure Blob, Azure Cosmos DB, Azure Event Hubs, Azure Service Bus, DB2, FTP, MQ, SFTP, and SQL Server, while a Consumption workflow doesn't have the built-in versions. A Consumption workflow can use built-in connectors for Azure API Management, Azure App Services, and Batch, while a Standard workflow doesn't have these built-in connectors. For more information, review [Built-in connectors in Azure Logic Apps](built-in.md) and [Single-tenant versus multitenant in Azure Logic Apps](../logic-apps/single-tenant-overview-compare.md).
+For example, a Standard workflow can use both managed connectors and built-in connectors for Azure Blob, Azure Cosmos DB, Azure Event Hubs, Azure Service Bus, DB2, FTP, MQ, SFTP, and SQL Server, while a Consumption workflow doesn't have the built-in versions. A Consumption workflow can use built-in connectors for Azure API Management, Azure App Services, and Batch, while a Standard workflow doesn't have these built-in connectors. For more information, see:
 
-This article provides a general overview about managed connectors and the way they're organized in the Consumption workflow designer versus the Standard workflow designer with examples. For technical reference information about each managed connector in Azure Logic Apps, review [Connectors reference for Azure Logic Apps](/connectors/connector-reference/connector-reference-logicapps-connectors).
+- [Built-in connectors in Azure Logic Apps](built-in.md)
+- [Single-tenant versus multitenant in Azure Logic Apps](../logic-apps/single-tenant-overview-compare.md)
 
-## Managed connector categories
+This guide provides a general overview about managed connectors and the way they're classified based on pricing and how they're billed or *metered*. For technical reference information about each managed connector in Azure Logic Apps, see [Connectors reference for Azure Logic Apps](/connectors/connector-reference/connector-reference-logicapps-connectors).
 
-For a Consumption logic app workflow, managed connectors appear in the designer under the following labels:
+## Managed connector categories
 
-* [Standard connectors](#standard-connectors) provide access to services such as Azure Blob Storage, Office 365, SharePoint, Salesforce, Power BI, OneDrive, and many more.
+For both Consumption and Standard logic app workflows, managed connectors appear in the connector gallery under the **Shared** label, which describes how these connectors are hosted and run in global, multitenant Azure. Based on the specific managed connector, pricing follows different models:
 
-* [Enterprise connectors](#enterprise-connectors) provide access to enterprise systems, such as SAP, IBM MQ, and IBM 3270 for an additional cost.
+- [Standard priced connectors](#standard-connectors) provide access to services such as Azure Blob Storage, Office 365, SharePoint, Salesforce, Power BI, OneDrive, and many more.
+- [Enterprise priced connectors](#enterprise-connectors) provide access to enterprise systems, such as SAP, IBM MQ, and IBM 3270 for an additional cost.
 
-For a Standard logic app *stateful* workflow, all managed connectors appear in the designer under the **Azure** label, which describes how these connectors are hosted on the Azure platform. A Standard *stateless* workflow can use only the built-in connectors designed to run natively in single-tenant Azure Logic Apps.
+Although managed connectors follow either Standard or Enterprise pricing in both Consumption and Standard workflows, billing or metering for managed connector usage differs based on whether your workflow is Consumption or Standard. For more information, see:
 
-Regardless whether you have a Consumption or Standard workflow, managed connector pricing follows the pricing for Enterprise connectors and Standard connectors, but metering works differently based on the workflow type. For more pricing information, review [Trigger and action operations in the Consumption model](../logic-apps/logic-apps-pricing.md#consumption-operations) and [Trigger and action operations in the Standard model](../logic-apps/logic-apps-pricing.md#standard-operations).
+- [Trigger and action operations in the Consumption model](../logic-apps/logic-apps-pricing.md#consumption-operations)
+- [Trigger and action operations in the Standard model](../logic-apps/logic-apps-pricing.md#standard-operations)
 
 Some managed connectors also fall into the following informal groups:
 
@@ -41,9 +46,7 @@ Some managed connectors also fall into the following informal groups:
 
 ## Standard connectors
 
-In the Consumption workflow designer, managed connectors that follow the Standard connector pricing model appear under the **Standard** label. This section lists *only some* of the popular managed connectors. For more pricing information, review [Trigger and action operations in the Consumption model](../logic-apps/logic-apps-pricing.md#consumption-operations).
-
-In the Standard workflow designer, *all* managed connectors appear under the **Azure** label. Managed connector pricing still follows the pricing for Enterprise connectors and Standard connectors, but metering works differently based on the workflow type. For more pricing information, review [Trigger and action operations in the Standard model](../logic-apps/logic-apps-pricing.md#standard-operations).
+This section lists only *some* of the popular managed connectors that follow the Standard pricing model:
 
 :::row:::
     :::column:::
@@ -116,9 +119,7 @@ In the Standard workflow designer, *all* managed connectors appear under the **A
 
 ## Enterprise connectors
 
-In the Consumption workflow designer, managed connectors that follow the Enterprise connector pricing model appear under the **Enterprise** label. These connectors can access enterprise systems for an additional cost. For more pricing information, review [Trigger and action operations in the Consumption model](../logic-apps/logic-apps-pricing.md#consumption-operations).
-
-In the Standard workflow designer, *all* managed connectors appear under the **Azure** label. Managed connector pricing still follows the pricing for Enterprise connectors and Standard connectors, but metering works differently based on the workflow type. For more pricing information, review [Trigger and action operations in the Standard model](../logic-apps/logic-apps-pricing.md#standard-operations).
+This section lists only *some* of the popular managed connectors that follow the Enterprise pricing model and provide access to enterprise systems for an additional cost:
 
 :::row:::
     :::column:::
@@ -143,7 +144,7 @@ In the Standard workflow designer, *all* managed connectors appear under the **A
 
 Before you can create a connection to an on-premises system, you must first [download, install, and set up an on-premises data gateway][gateway-doc]. This gateway provides a secure communication channel without having to set up the necessary network infrastructure.
 
-For a Consumption workflow, this section lists example [Standard connectors](#standard-connectors) that can access on-premises systems. For the expanded on-premises connectors list, review [Supported data sources](../logic-apps/logic-apps-gateway-connection.md#supported-connections).
+For a Consumption workflow, this section lists example [Standard connectors](#standard-connectors) that can access on-premises systems. For the expanded on-premises connectors list, see [Supported data sources](../logic-apps/logic-apps-gateway-connection.md#supported-connections).
 
 :::row:::
     :::column:::
@@ -256,11 +257,9 @@ For more information, review the following documentation:
     :::column-end:::
 :::row-end:::
 
+## Related content
 
-## Next steps
-
-> [!div class="nextstepaction"]
-> [Create custom APIs you can call from Logic Apps](../logic-apps/logic-apps-create-api-app.md)
+- [Create custom APIs you can call from Azure Logic Apps](../logic-apps/logic-apps-create-api-app.md)
 
 <!--Managed connector icons-->
 [apache-impala-icon]: ./media/apis-list/apache-impala.png

articles/logic-apps/block-connections-across-tenants.md

@@ -1,12 +1,13 @@
 ---
-title: Block access to and from other tenants
-description: Block connections between your tenant and other Microsoft Entra tenants in Azure Logic Apps.
+title: Block Shared Connection Access Across Tenants
+description: Block access through shared workflow connections between your Microsoft Entra tenant and other tenants by using Azure Logic Apps.
 services: logic-apps
 ms.suite: integration
-ms.reviewer: estfan, azla
+ms.reviewers: estfan, azla
 ms.topic: how-to
-ms.date: 03/27/2025
-# Customer intent: As a developer, I want to prevent access to and from other Microsoft Entra tenants.
+ms.update-cycle: 1095-days
+ms.date: 03/10/2026
+# Customer intent: As an integration developer who works with Azure Logic Apps, I want to prevent access through shared workflow connections between my Microsoft Entra tenant and other tenants.
 ---
 
 # Block connections to and from other tenants in Azure Logic Apps

articles/logic-apps/connect-on-premises-data-sources.md

@@ -1,13 +1,14 @@
 ---
-title: Connect to on-premises data sources
-description: Access on-premises data sources from workflows in Azure Logic Apps by creating the on-premises data gateway resource in the Azure portal.
+title: Connect to On-Premises Data Sources
+description: Access on-premises data sources from workflows in Azure Logic Apps by creating an on-premises data gateway resource in the Azure portal.
 services: logic-apps
 ms.suite: integration
-ms.reviewer: estfan, mideboer, azla
+ms.reviewers: estfan, mideboer, azla
 ms.topic: how-to
-ms.date: 04/22/2025
+ms.update-cycle: 1095-days
+ms.date: 03/10/2026
 ms.custom: sfi-image-nochange
-#Customer intent: As a logic apps developer, I want to create a data gateway resource in the Azure portal so that my logic app workflow can connect to on-premises data sources.
+#Customer intent: As an integration developer who works with Azure Logic Apps, I want my workflow to use connectors that access on-premises data sources by creating a data gateway resource in the Azure portal.
 ---
 
 # Connect to on-premises data sources from Azure Logic Apps