Merge pull request #262946 from ecfan/fresh

Azure Logic Apps: Update doc about calling from Power Apps (refresh) and Power Automate (deprecated)

Author: v-dirichards

articles/logic-apps/.openpublishing.redirection.logic-apps.json

@@ -1,5 +1,10 @@
 {
     "redirections": [
+        {
+            "source_path_from_root": "/articles/logic-apps/call-from-power-automate-power-apps.md",
+            "redirect_url": "/azure/logic-apps/call-from-power-apps",
+            "redirect_document_id": true
+        },
         {
             "source_path_from_root": "/articles/logic-apps/sap-create-example-scenario-workflows.md",
             "redirect_url": "/azure/logic-apps/connectors/sap-create-example-scenario-workflows",

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

@@ -5,7 +5,7 @@ services: logic-apps
 ms.suite: integration
 ms.reviewer: estfan, azla
 ms.topic: how-to
-ms.date: 08/01/2022
+ms.date: 01/10/2024
 # Customer intent: As a developer, I want to prevent access to and from other Microsoft Entra tenants.
 ---
 

articles/logic-apps/block-connections-connectors.md

@@ -5,7 +5,7 @@ services: logic-apps
 ms.suite: integration
 ms.reviewer: deli, estfan, azla
 ms.topic: how-to
-ms.date: 08/22/2022
+ms.date: 01/10/2024
 ---
 
 # Block connector usage in Azure Logic Apps
@@ -101,7 +101,7 @@ To block creating a connection altogether in a logic app workflow, follow these
    | **Policy enforcement** | Yes | **Enabled** | This setting specifies whether to enable or disable the policy definition when you save your work. |
    |||||
 
-1. Under **POLICY RULE**, the JSON edit box is pre-populated with a policy definition template. Replace this template with your [policy definition](../governance/policy/concepts/definition-structure.md) based on the properties described in the table below and by following this syntax:
+1. Under **POLICY RULE**, the JSON edit box is prepopulated with a policy definition template. Replace this template with your [policy definition](../governance/policy/concepts/definition-structure.md) based on the properties described in the table below and by following this syntax:
 
    ```json
    {
@@ -222,7 +222,7 @@ When you create a connection in a logic app workflow, this connection exists as
    | **Policy enforcement** | Yes | **Enabled** | This setting specifies whether to enable or disable the policy definition when you save your work. |
    |||||
 
-1. Under **POLICY RULE**, the JSON edit box is pre-populated with a policy definition template. Replace this template with your [policy definition](../governance/policy/concepts/definition-structure.md) based on the properties described in the table below and by following this syntax:
+1. Under **POLICY RULE**, the JSON edit box is prepopulated with a policy definition template. Replace this template with your [policy definition](../governance/policy/concepts/definition-structure.md) based on the properties described in the table below and by following this syntax:
 
    ```json
    {
@@ -320,7 +320,7 @@ Next, you need to assign the policy definition where you want to enforce the pol
 
 1. After the policy takes effect, you can [test your policy](#test-policy).
 
-For more information, see [Quickstart: Create a policy assignment to identify non-compliant resources](../governance/policy/assign-policy-portal.md).
+For more information, see [Quickstart: Create a policy assignment to identify noncompliant resources](../governance/policy/assign-policy-portal.md).
 
 <a name="test-policy"></a>
 

articles/logic-apps/call-from-power-apps.md

@@ -0,0 +1,97 @@
+---
+title: Call logic apps from Power Apps
+description: Call logic apps from Microsoft Power Apps by exporting logic apps as custom connectors.
+services: logic-apps
+ms.suite: integration
+ms.reviewer: estfan, azla
+ms.topic: how-to
+ms.date: 01/10/2024
+---
+
+# Call logic app workflows from Power Apps
+
+[!INCLUDE [logic-apps-sku-consumption](../../includes/logic-apps-sku-consumption.md)]
+
+To call your logic app workflow from a Power Apps flow, you can export your logic app resource and workflow as a custom connector. You can then call your workflow from a flow in a Power Apps environment.
+
+## 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/?WT.mc_id=A261C142F).
+
+* A Power Apps license.
+
+* A Consumption logic app workflow with a request trigger to export.
+
+  > [!NOTE]
+  >
+  > The Export capability is available only for Consumption logic app workflows in multitenant Azure Logic Apps.
+
+* A Power Apps flow from where to call your logic app workflow.
+
+## Export your logic app as a custom connector
+
+Before you can call your workflow from Power Apps, you must first export your logic app resource as a custom connector.
+
+1. In the [Azure portal](https://portal.azure.com) search box, enter **logic apps**. From the results, select **Logic apps**.
+
+1. Select the logic app resource that you want to export.
+
+1. On your logic app menu, select **Overview**. On the **Overview** page toolbar, select **Export** > **Export to Power Apps**.
+
+   :::image type="content" source="./media/call-from-power-apps/export-logic-app.png" alt-text="Screenshot shows Azure portal and Overview toolbar with Export button selected.":::
+
+1. On the **Export to Power Apps** pane, provide the following information:
+
+   | Property | Description |
+   |----------|-------------|
+   | **Name** | Provide a name for the custom connector to create from your logic app. 
+   | **Environment** | Select the Power Apps environment from which you want to call your logic app. 
+
+1. When you're done, select **OK**. To confirm that your logic app was successfully exported, check the notifications pane.
+
+### Export errors
+
+Here are errors that might happen when you export your logic app as a custom connector and suggested solutions:
+
+* **The current Logic App cannot be exported. To export, select a Logic App that has a request trigger.**: Check that your logic app workflow begins with a [Request trigger](../connectors/connectors-native-reqres.md).
+
+## Connect to your logic app workflow from Power Apps
+
+1. In [Power Apps](https://powerapps.microsoft.com/), on the **Power Apps** home page menu, select **Flows**.
+
+1. On the **Flows** page, select the flow from where you want to call your logic app workflow.
+
+1. On your flow page toolbar, select **Edit**.
+
+1. In the flow editor, select **+ New step**.
+
+1. In the **Choose an operation** search box, enter the name for your logic app custom connector.
+
+   Optionally, to see only custom connectors in your environment, filter the results using the **Custom** tab, for example:
+
+   :::image type="content" source="./media/call-from-power-apps/power-apps-custom-connector-action.png" alt-text="Screenshot shows Power Apps flow editor with a new operation added for custom connector and available actions.":::
+
+1. Select the custom connector operation that you want to call from your flow.
+
+1. Provide the necessary operation information to pass to the custom connector.
+
+1. On the Power Apps editor toolbar, select **Save** to save your changes. 
+
+1. In the [Azure portal](https://portal.azure.com), find and open the logic app resource that you exported.
+
+1. Confirm that your logic app workflow works as expected with your Power Apps flow.
+
+## Delete logic app custom connector from Power Apps
+
+1. In [Power Apps](https://powerapps.microsoft.com), on the **Power Apps** home page menu, select **Discover**. On the **Discover** page, find the **Data** tile, and select **Custom connectors**.
+
+1. In the list, find your custom connector, and select the ellipses (**...**) button, and then select **Delete**.
+
+   :::image type="content" source="./media/call-from-power-apps/delete-custom-connector.png" alt-text="Screenshot shows Custom connectors page with custom connector management options.":::
+
+1. To confirm deletion, select **OK**.
+
+## Next steps
+
+* [Managed connectors for Azure Logic Apps](/connectors/connector-reference/connector-reference-logicapps-connectors)
+* [Built-in connectors for Azure Logic Apps](../connectors/built-in.md)

articles/logic-apps/call-from-power-automate-power-apps.md

@@ -5,7 +5,7 @@ services: logic-apps
 ms.suite: integration
 ms.reviewer: estfan, azla
 ms.topic: how-to
-ms.date: 01/03/2023
+ms.date: 01/10/2024
 ms.custom: ignite-fall-2021, engagement-fy23, devx-track-dotnet
 # Customer intent: As a logic apps developer, I want to create a Standard logic app workflow that runs in single-tenant Azure Logic Apps using Visual Studio Code.
 ---

articles/logic-apps/create-single-tenant-workflows-visual-studio-code.md

@@ -5,17 +5,17 @@ services: logic-apps
 ms.suite: integration
 ms.reviewer: estfan, azla
 ms.topic: how-to
-ms.date: 08/20/2022
+ms.date: 01/10/2024
 ---
 
 # Estimate storage costs for Standard logic app workflows in single-tenant Azure Logic Apps
 
 [!INCLUDE [logic-apps-sku-standard](../../includes/logic-apps-sku-standard.md)]
 
-Azure Logic Apps uses [Azure Storage](../storage/index.yml) for any storage operations. In traditional *multi-tenant* Azure Logic Apps, any storage usage and costs are attached to the logic app. Now, in *single-tenant* Azure Logic Apps, you can use your own storage account. These storage costs are listed separately in your Azure billing invoice. This capability gives you more flexibility and control over your logic app data.
+Azure Logic Apps uses [Azure Storage](../storage/index.yml) for any storage operations. In traditional *multitenant* Azure Logic Apps, any storage usage and costs are attached to the logic app. Now, in *single-tenant* Azure Logic Apps, you can use your own storage account. These storage costs are listed separately in your Azure billing invoice. This capability gives you more flexibility and control over your logic app data.
 
 > [!NOTE]
-> This article applies to workflows in the single-tenant Azure Logic Apps environment. These workflows exist in the same logic app and in a single tenant that share the same storage. For more information, see [Single-tenant versus multi-tenant and integration service environment](single-tenant-overview-compare.md).
+> This article applies to workflows in the single-tenant Azure Logic Apps environment. These workflows exist in the same logic app and in a single tenant that share the same storage. For more information, see [Single-tenant versus multitenant and integration service environment](single-tenant-overview-compare.md).
 
 Storage costs change based on your workflows' content. Different triggers, actions, and payloads result in different storage operations and needs. This article describes how to estimate your storage costs when you're using your own Azure Storage account with single-tenant based logic apps. First, you can [estimate the number of storage operations you'll perform](#estimate-storage-needs) using the Logic Apps storage calculator. Then, you can [estimate your possible storage costs](#estimate-storage-costs) using these numbers in the Azure pricing calculator.
 

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

@@ -6,7 +6,7 @@ ms.suite: integration
 ms.reviewer: estfan, sneshaf, pinath, azla
 ms.topic: how-to
 ms.custom: devx-track-arm-template
-ms.date: 01/23/2023
+ms.date: 01/10/2024
 ---
 
 # Export flows from Power Automate and deploy to Azure Logic Apps