Merge pull request #238858 from ecfan/designer-preview

Azure Logic Apps: Standard designer updates for GA

Author: AnnaMHuff

articles/logic-apps/create-single-tenant-workflows-azure-portal.md

@@ -1,11 +1,11 @@
 ---
-title: Create example Standard logic app workflow in the Azure portal
+title: Create example Standard logic app workflow in Azure portal
 description: Create your first example Standard logic app workflow that runs in single-tenant Azure Logic Apps using the Azure portal.
 services: logic-apps
 ms.suite: integration
 ms.reviewer: estfan, azla
 ms.topic: how-to
-ms.date: 04/04/2023
+ms.date: 05/23/2023
 ms.custom: ignite-fall-2021
 
 # Customer intent: As a developer, I want to create my first example Standard logic app workflow that runs in single-tenant Azure Logic Apps using the Azure portal.
@@ -15,7 +15,7 @@ ms.custom: ignite-fall-2021
 
 [!INCLUDE [logic-apps-sku-standard](../../includes/logic-apps-sku-standard.md)]
 
-This guide shows how to create an example automated workflow that waits for an inbound web request and then sends a message to an email account. More specifically, you'll create a [Standard logic app resource](logic-apps-overview.md#resource-environment-differences), which can include multiple [stateful and stateless workflows](single-tenant-overview-compare.md#stateful-stateless) that run in single-tenant Azure Logic Apps. 
+This how-to guide shows how to create an example automated workflow that waits for an inbound web request and then sends a message to an email account. More specifically, you'll create a [Standard logic app resource](logic-apps-overview.md#resource-environment-differences), which can include multiple [stateful and stateless workflows](single-tenant-overview-compare.md#stateful-stateless) that run in single-tenant Azure Logic Apps. 
 
 > [!NOTE]
 >
@@ -193,35 +193,13 @@ So now you'll add a trigger that starts your workflow.
 
 This example workflow starts with the [built-in Request trigger](../connectors/connectors-native-reqres.md) named **When an HTTP request is received**. This trigger creates an endpoint that other services or logic app workflows can call and waits for those inbound calls or requests to arrive. Built-in operations run natively and directly within the Azure Logic Apps runtime.
 
-### [Standard](#tab/standard)
-
-1. On the workflow designer, make sure that your blank workflow is open and that the **Choose an operation** prompt is selected on the designer surface.
-
-1. By using **request** as the search term, [follow these steps to add the built-in Request trigger named **When an HTTP request is received**](create-workflow-with-trigger-or-action.md?tabs=standard#add-trigger) to your workflow.
-
-   ![Screenshot showing pane named Add a trigger with selected trigger named When a HTTP request is received.](./media/create-single-tenant-workflows-azure-portal/find-request-trigger.png)
-
-   When the trigger appears on the designer, the trigger's information pane opens to show the trigger's properties, settings, and other actions.
-
-   ![Screenshot showing the trigger information pane.](./media/create-single-tenant-workflows-azure-portal/request-trigger-added-to-designer.png)
-
-   > [!NOTE]
-   >
-   > If the information pane doesn't appear, makes sure that the trigger is selected on the designer.
-
-1. Save your workflow. On the designer toolbar, select **Save**.
-
-### [Standard (Preview)](#tab/standard-preview)
-
 1. On the workflow designer, make sure that your blank workflow is open and that the **Add a trigger** prompt is selected on the designer surface.
 
-1. By using **request** as the search term, [follow these steps to add the built-in Request trigger named **When an HTTP request is received**](create-workflow-with-trigger-or-action.md?tabs=standard-preview#add-trigger) to your workflow.
-
-   ![Screenshot showing preview picker with selected trigger named When a HTTP request is received.](./media/create-single-tenant-workflows-azure-portal/find-request-trigger-preview.png)
+1. By using **request** as the search term, [follow these steps to add the built-in Request trigger named **When an HTTP request is received**](create-workflow-with-trigger-or-action.md?tabs=standard#add-trigger) to your workflow.
 
    When the trigger appears on the designer, the trigger's information pane opens to show the trigger's properties, settings, and other actions.
 
-   ![Screenshot showing the preview workflow designer and trigger information pane.](./media/create-single-tenant-workflows-azure-portal/request-trigger-added-to-designer-preview.png)
+   ![Screenshot showing the workflow designer and trigger information pane.](./media/create-single-tenant-workflows-azure-portal/request-trigger-added-to-designer.png)
 
 1. Save your workflow. On the designer toolbar, select **Save**.
 
@@ -233,15 +211,13 @@ When you save a workflow for the first time, and that workflow starts with a Req
 
 This example workflow continues with the [Office 365 Outlook managed connector action](../connectors/connectors-create-api-office365-outlook.md) named **Send an email**. Managed connector operations run in Azure versus natively and directly on the Azure Logic Apps runtime.
 
-### [Standard](#tab/standard)
-
 1. On the designer, under the trigger that you added, select the plus sign (**+**) > **Add an action**.
 
-   The **Choose an operation** prompt appears on the designer, and the **Add an action** pane opens so that you can select the next action.
+   The **Browse operations** pane opens so that you can select the next action.
 
-1. By using **office 365 send email** as the search term, [follow these steps to add the Office 365 Outlook action that's named **Send an email (V2)**](create-workflow-with-trigger-or-action.md?tabs=standard#add-action) to your workflow.
+1. By using **office send an email** as the search term, [follow these steps to add the Office 365 Outlook action that's named **Send an email (V2)**](create-workflow-with-trigger-or-action.md?tabs=standard#add-action) to your workflow.
 
-   ![Screenshot showing the designer, the pane named Add an action, and the selected Office 365 Outlook named Send an email.](./media/create-single-tenant-workflows-azure-portal/find-send-email-action.png)
+   ![Screenshot showing the designer, the picker pane, and the selected Office 365 Outlook named Send an email.](./media/create-single-tenant-workflows-azure-portal/find-send-email-action.png)
 
 1. In the action's information pane, on the **Create Connection** tab, select **Sign in** so that you can create a connection to your email account.
 
@@ -276,53 +252,6 @@ This example workflow continues with the [Office 365 Outlook managed connector a
 
 1. Save your work. On the designer toolbar, select **Save**.
 
-1. If your environment has strict network requirements or firewalls that limit traffic, you have to set up permissions for any trigger or action connections that exist in your workflow. To find the fully qualified domain names, review [Find domain names for firewall access](#firewall-setup).
-
-   Otherwise, to test your workflow, [manually trigger a run](#trigger-workflow).
-
-### [Standard (Preview)](#tab/standard-preview)
-
-1. On the designer, under the trigger that you added, select the plus sign (**+**) > **Add an action**.
-
-   The **Browse operations** pane opens so that you can select the next action.
-
-1. By using **office send an email** as the search term, [follow these steps to add the Office 365 Outlook action that's named **Send an email (V2)**](create-workflow-with-trigger-or-action.md?tabs=standard-preview#add-action) to your workflow.
-
-   ![Screenshot showing the preview designer, the picker pane, and the selected Office 365 Outlook named Send an email.](./media/create-single-tenant-workflows-azure-portal/find-send-email-action-preview.png)
-
-1. In the action's information pane, on the **Create Connection** tab, select **Sign in** so that you can create a connection to your email account.
-
-   ![Screenshot showing the preview designer, the pane named Send an email (V2) with Sign in button.](./media/create-single-tenant-workflows-azure-portal/send-email-action-sign-in-preview.png)
-
-1. When you're prompted for access to your email account, sign in with your account credentials.
-
-   > [!NOTE]
-   > If you get the error message, **"Failed with error: 'The browser is closed.'. Please sign in again"**, 
-   > check whether your browser blocks third-party cookies. If these cookies are blocked, 
-   > try adding **https://portal.azure.com** to the list of sites that can use cookies. 
-   > If you're using incognito mode, make sure that third-party cookies aren't blocked while working in that mode.
-   > 
-   > If necessary, reload the page, open your workflow, add the email action again, and try creating the connection.
-
-   After Azure creates the connection, the **Send an email** action appears on the designer and is selected by default. If the action isn't selected, select the action so that its information pane is also open.
-
-1. In the action information pane, on the **Parameters** tab, provide the required information for the action, for example:
-
-   ![Screenshot that shows the designer and the "Send an email" information pane with the "Parameters" tab selected.](./media/create-single-tenant-workflows-azure-portal/send-email-action-details-preview.png)
-
-   | Property | Required | Value | Description |
-   |----------|----------|-------|-------------|
-   | **To** | Yes | <*your-email-address*> | The email recipient, which can be your email address for test purposes. This example uses the fictitious email, **[email protected]**. |
-   | **Subject** | Yes | **An email from your example workflow** | The email subject |
-   | **Body** | Yes | **Hello from your example workflow!** | The email body content |
-
-   > [!NOTE]
-   > When making any changes in the information pane on the **Settings**, **Static Result**, or **Run After** tabs, 
-   > make sure that you select **Done** to commit those changes before you switch tabs or change focus to the designer. 
-   > Otherwise, the designer won't keep your changes.
-
-1. Save your work. On the designer toolbar, select **Save**.
-
 1. If your environment has strict network requirements or firewalls that limit traffic, you have to set up permissions for any trigger or action connections that exist in your workflow. To find the fully qualified domain names, review [Find domain names for firewall access](#firewall-setup).
 
    Otherwise, to test your workflow, [manually trigger a run](#trigger-workflow).