Update links to renamed quickstart and fix terminology for Azure Logic Apps

ecfan · ecfan · commit 5ea5a24f5313 · 2023-03-15T13:08:44.000-07:00
diff --git a/articles/connectors/connectors-create-api-office365-outlook.md b/articles/connectors/connectors-create-api-office365-outlook.md
@@ -34,7 +34,7 @@ You can use any trigger to start your workflow, for example, when a new email ar
 
 * 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 logic app where you want to access your Outlook account. To start your workflow with an Office 365 Outlook trigger, you need to have a [blank logic app](../logic-apps/quickstart-create-first-logic-app-workflow.md). To add an Office 365 Outlook action to your workflow, your logic app workflow needs to already have a trigger.
+* The logic app where you want to access your Outlook account. To start your workflow with an Office 365 Outlook trigger, you need to have a blank logic app workflow. To add an Office 365 Outlook action to your workflow, your logic app workflow needs to already have a trigger.
 
 ## Connector reference
 
diff --git a/articles/connectors/connectors-create-api-smtp.md b/articles/connectors/connectors-create-api-smtp.md
@@ -27,8 +27,7 @@ If you're new to logic apps, review [What is Azure Logic Apps?](../logic-apps/lo
   Your credentials authorize your logic app to create 
   a connection and access your SMTP account.
 
-* Basic knowledge about 
-[how to create logic apps](../logic-apps/quickstart-create-first-logic-app-workflow.md)
+* Basic knowledge about how to create logic apps
 
 * The logic app where you want to access your SMTP account. 
 To use an SMTP action, start your logic app with a trigger, 
diff --git a/articles/connectors/connectors-integrate-security-operations-create-api-microsoft-graph-security.md b/articles/connectors/connectors-integrate-security-operations-create-api-microsoft-graph-security.md
@@ -45,7 +45,7 @@ To learn more about Microsoft Graph Security, see the [Microsoft Graph Security
 
   * During your logic app's first run, your app can request consent from your Azure AD tenant administrator through the [application consent experience](../active-directory/develop/application-consent-experience.md).
    
-* Basic knowledge about [how to create logic apps](../logic-apps/quickstart-create-first-logic-app-workflow.md)
+* Basic knowledge about how to create logic apps
 
 * The logic app where you want to access your Microsoft Graph Security entities, such as alerts. To use a Microsoft Graph Security trigger, you need a blank logic app. To use a Microsoft Graph Security action, you need a logic app that starts with the appropriate trigger for your scenario.
 
diff --git a/articles/connectors/connectors-native-delay.md b/articles/connectors/connectors-native-delay.md
@@ -29,7 +29,7 @@ Here are some example ways to use these actions:
 
 * An Azure account and subscription. If you don't have a subscription, you can [sign up for a free Azure account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
 
-* Basic knowledge about [logic apps](../logic-apps/logic-apps-overview.md). Before you can use an action, your logic app must first start with a trigger. You can use any trigger you want and add other actions before you add a delay action. This topic uses an Office 365 Outlook trigger. If you're new to logic apps, learn [how to create your first logic app](../logic-apps/quickstart-create-first-logic-app-workflow.md).
+* Basic knowledge about [logic apps](../logic-apps/logic-apps-overview.md). Before you can use an action, your logic app must first start with a trigger. You can use any trigger you want and add other actions before you add a delay action. This topic uses an Office 365 Outlook trigger.
 
 <a name="add-delay"></a>
 
diff --git a/articles/connectors/connectors-native-http-swagger.md b/articles/connectors/connectors-native-http-swagger.md
@@ -36,8 +36,6 @@ With the built-in **HTTP + Swagger** operation and [Azure Logic Apps](../logic-a
 
 * The logic app workflow from where you want to call the target endpoint. To start with the **HTTP + Swagger** trigger, create a blank logic app workflow. To use the **HTTP + Swagger** action, start your workflow with any trigger that you want. This example uses the **HTTP + Swagger** trigger as the first step. 
 
-  If you're new to logic app workflows, review [What is Azure Logic Apps?](../logic-apps/logic-apps-overview.md) and [how to create your first logic app workflow](../logic-apps/quickstart-create-first-logic-app-workflow.md).
-
 ## Add an HTTP + Swagger trigger
 
 This built-in trigger sends an HTTP request to a URL for a Swagger file that describes a REST API. The trigger then returns a response that contains that file's content.
diff --git a/articles/connectors/connectors-native-http.md b/articles/connectors/connectors-native-http.md
@@ -29,9 +29,9 @@ For information about encryption, security, and authorization for outbound calls
 
 * The URL for the target endpoint that you want to call
 
-* Basic knowledge about [how to create logic apps](../logic-apps/quickstart-create-first-logic-app-workflow.md). If you're new to logic apps, review [What is Azure Logic Apps](../logic-apps/logic-apps-overview.md)?
+* Basic knowledge about how to create logic app workflows. If you're new to logic apps, see [What is Azure Logic Apps](../logic-apps/logic-apps-overview.md)?
 
-* The logic app from where you want to call the target endpoint. To start with the HTTP trigger, [create a blank logic app](../logic-apps/quickstart-create-first-logic-app-workflow.md). To use the HTTP action, start your logic app with any trigger that you want. This example uses the HTTP trigger as the first step.
+* The logic app from where you want to call the target endpoint. To start with the HTTP trigger, you'll need a blank logic app workflow. To use the HTTP action, start your logic app with any trigger that you want. This example uses the HTTP trigger as the first step.
 
 <a name="http-trigger"></a>
 
diff --git a/articles/connectors/connectors-native-recurrence.md b/articles/connectors/connectors-native-recurrence.md
@@ -40,7 +40,7 @@ The Recurrence trigger is part of the built-in Schedule connector and runs nativ
 
 * 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).
 
-* Basic knowledge about [logic app workflows](../logic-apps/logic-apps-overview.md). If you're new to logic apps, learn [how to create your first logic app workflow](../logic-apps/quickstart-create-first-logic-app-workflow.md).
+* Basic knowledge about [logic app workflows](../logic-apps/logic-apps-overview.md).
 
 <a name="add-recurrence-trigger"></a>
 
diff --git a/articles/connectors/connectors-native-reqres.md b/articles/connectors/connectors-native-reqres.md
@@ -31,11 +31,11 @@ To run your workflow by sending an outgoing or outbound request instead, use the
 
 * The logic app workflow where you want to receive the inbound HTTPS request. To start your workflow with a Request trigger, you have to start with a blank workflow. To use the Response action, your workflow must start with the Request trigger.
 
-If you're new to Azure Logic Apps, review the following get started documentation:
+If you're new to Azure Logic Apps, see the following documentation:
 
 * [What is Azure Logic Apps](../logic-apps/logic-apps-overview.md)
 
-* [Quickstart: Create a Consumption logic app workflow in multi-tenant Azure Logic Apps](../logic-apps/quickstart-create-first-logic-app-workflow.md)
+* [Quickstart: Create a Consumption logic app workflow in multi-tenant Azure Logic Apps](../logic-apps/quickstart-create-example-consumption-workflow.md)
 
 * [Create a Standard logic app workflow in single-tenant Azure Logic Apps](../logic-apps/create-single-tenant-workflows-azure-portal.md)
 
diff --git a/articles/connectors/connectors-native-sliding-window.md b/articles/connectors/connectors-native-sliding-window.md
@@ -32,7 +32,7 @@ For differences between this trigger and the Recurrence trigger or for more info
 
 * An Azure account and subscription. If you don't have a subscription, you can [sign up for a free Azure account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
 
-* Basic knowledge about [logic apps](../logic-apps/logic-apps-overview.md). If you're new to logic apps, learn [how to create your first logic app](../logic-apps/quickstart-create-first-logic-app-workflow.md).
+* Basic knowledge about [logic apps](../logic-apps/logic-apps-overview.md).
 
 ## Add Sliding Window trigger
 
diff --git a/articles/connectors/connectors-native-webhook.md b/articles/connectors/connectors-native-webhook.md
@@ -45,9 +45,7 @@ For information about encryption, security, and authorization for inbound calls
 
 * The URL for an already deployed endpoint or API that supports the webhook subscribe and unsubscribe pattern for [webhook triggers in logic apps](../logic-apps/logic-apps-create-api-app.md#webhook-triggers) or [webhook actions in logic apps](../logic-apps/logic-apps-create-api-app.md#webhook-actions) as appropriate
 
-* Basic knowledge about [how to create logic apps](../logic-apps/quickstart-create-first-logic-app-workflow.md). If you're new to logic apps, review [What is Azure Logic Apps?](../logic-apps/logic-apps-overview.md)
-
-* The logic app where you want to wait for specific events at the target endpoint. To start with the HTTP Webhook trigger, [create a blank logic app](../logic-apps/quickstart-create-first-logic-app-workflow.md). To use the HTTP Webhook action, start your logic app with any trigger that you want. This example uses the HTTP trigger as the first step.
+* The logic app where you want to wait for specific events at the target endpoint. To start with the HTTP Webhook trigger, create a blank logic app workflow. To use the HTTP Webhook action, start your logic app with any trigger that you want. This example uses the HTTP trigger as the first step.
 
 ## Add an HTTP Webhook trigger
 
diff --git a/articles/connectors/connectors-run-3270-apps-ibm-mainframe-create-api-3270.md b/articles/connectors/connectors-run-3270-apps-ibm-mainframe-create-api-3270.md
@@ -62,8 +62,7 @@ that Azure Logic Apps supports.
 * 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).
 
-* Basic knowledge about 
-[how to create logic apps](../logic-apps/quickstart-create-first-logic-app-workflow.md)
+* Basic knowledge about [logic app workflows](../logic-apps/logic-apps-overview.md)
 
 * Recommended: An [integration service environment (ISE)](../logic-apps/connect-virtual-network-vnet-isolated-environment.md) 
 
@@ -73,12 +72,7 @@ that Azure Logic Apps supports.
 
 * The logic app to use for automating and running your 3270 screen-driven app
 
-  The IBM 3270 connector doesn't have triggers, 
-  so use another trigger to start your logic app, 
-  such as the **Recurrence** trigger. You can 
-  then add 3270 connector actions. To get started, 
-  [create a blank logic app](../logic-apps/quickstart-create-first-logic-app-workflow.md). 
-  If you use an ISE, select that ISE as your logic app's location.
+  The IBM 3270 connector doesn't have triggers, so use another trigger to start your logic app, such as the **Recurrence** trigger. You can then add 3270 connector actions. To get started, create a blank logic app workflow. If you use an ISE, select that ISE as your logic app's location.
 
 * [Download and install the 3270 Design Tool](https://aka.ms/3270-design-tool-download).
 The only prerequisite is [Microsoft .NET Framework 4.8](https://aka.ms/net-framework-download).
diff --git a/articles/connectors/introduction.md b/articles/connectors/introduction.md
@@ -186,6 +186,6 @@ The following table includes known issues for connectors in Azure Logic Apps:
 
 > [!div class="nextstepaction"]
 >
-> [Create a Consumption logic app workflow - Azure portal](../logic-apps/quickstart-create-first-logic-app-workflow.md)
+> [Create a Consumption logic app workflow - Azure portal](../logic-apps/quickstart-create-example-consumption-workflow.md)
 >
 > [Create a Standard logic app workflow - Azure portal](../logic-apps/create-single-tenant-workflows-azure-portal.md)
diff --git a/articles/data-factory/how-to-send-email.md b/articles/data-factory/how-to-send-email.md
@@ -13,22 +13,22 @@ ms.date: 08/10/2022
 
 # Send an email with an Azure Data Factory or Azure Synapse pipeline
 
-[!INCLUDE[appliesto-adf-asa-md](includes/appliesto-adf-asa-md.md)]
+[!INCLUDE [appliesto-adf-asa-md](includes/appliesto-adf-asa-md.md)]
 
 It's often necessary to send notifications during or after execution of a pipeline. Notification provides proactive alerting and reduces the need for reactive monitoring to discover issues.  This article shows how to configure email notifications from an Azure Data Factory or Azure Synapse pipeline. 
 
 ## Prerequisites
 
 - **Azure subscription**. If you don't have an Azure subscription, create a [free](https://azure.microsoft.com/free/) account before you begin.
-- **Logic App**. To trigger sending an email from the pipeline, you use [Logic Apps](../logic-apps/logic-apps-overview.md) to define the workflow. For details on creating a Logic App workflow, see [How to create a logic app](../logic-apps/quickstart-create-first-logic-app-workflow.md).
+- **Standard logic app workflow**. To trigger sending an email from the pipeline, you use [Azure Logic Apps](../logic-apps/logic-apps-overview.md) to define the workflow. For details on creating a Standard logic app workflow, see [Create an example Standard logic app workflow](../logic-apps/create-single-tenant-workflows-azure-portal.md).
 
-## Create the email workflow in your Logic App
+## Create the email workflow in your logic app
 
-Create a Logic App workflow named `SendEmailFromPipeline`. Define the workflow trigger as `When an HTTP request is received`, and add an action of `Office 365 Outlook – Send an email (V2)`.
+Create a Standard logic app workflow named `SendEmailFromPipeline`. Add the Request trigger named `When an HTTP request is received`, and add the Office 365 Outlook action named `Send an email (V2)`.
 
-:::image type="content" source="media/how-to-send-email/logic-app-workflow-designer.png" alt-text="Shows the Logic App workflow designer with a Send Email (V2); action from an HTTP request trigger.":::
+:::image type="content" source="media/how-to-send-email/logic-app-workflow-designer.png" alt-text="Shows the logic app workflow designer with the Request trigger and Send an email (V2) action.":::
 
-For the HTTP request trigger, provide this JSON for the `Request Body JSON Schema`:
+In Request trigger, provide this JSON for the `Request Body JSON Schema` property:
 
 ```json
 {
@@ -50,30 +50,30 @@ For the HTTP request trigger, provide this JSON for the `Request Body JSON Schem
 }
 ```
 
-The HTTP Request in the Logic App Designer should look like this:
+The Request trigger in the workflow designer should look like this:
 
-:::image type="content" source="media/how-to-send-email/logic-app-http-request-trigger.png" alt-text="Shows the Logic App workflow designer for the HTTP Request trigger with the Request Body JSON Schema field populated.":::
+:::image type="content" source="media/how-to-send-email/logic-app-http-request-trigger.png" alt-text="Shows the workflow designer for the Request trigger with the Request Body JSON Schema field populated.":::
 
-For the **Send Email (V2)** action, customize how you wish to format the email, using the properties from the request Body JSON schema:
+For the **Send an email (V2)** action, customize how you wish to format the email, using the properties from the request Body JSON schema:
 
-:::image type="content" source="media/how-to-send-email/logic-app-email-action.png" alt-text="Shows the Logic App workflow designer for the Send Email (V2) action.":::
+:::image type="content" source="media/how-to-send-email/logic-app-email-action.png" alt-text="Shows the workflow designer for the Send an email (V2) action.":::
 
-Save the workflow. Browse to the Overview page for the workflow.  Make a note of the Workflow URL for your new workflow then, highlighted in the image below:
+Save the workflow. Browse to the Overview page for the workflow. Make a note of the workflow URL, highlighted in the image below:
 
-:::image type="content" source="media/how-to-send-email/logic-app-workflow-url.png" alt-text="Shows the Logic App workflow Overview tab with the Workflow URL highlighted.":::
+:::image type="content" source="media/how-to-send-email/logic-app-workflow-url.png" alt-text="Shows the workflow Overview page with the Workflow URL highlighted.":::
 
 > [!NOTE]
-> To find the Workflow URL you must browse to the workflow itself, not just the logic app that contains it.  From the Workflows page of your logic app instance, choose the workflow and then navigate to its Overview page. 
+> To find the workflow URL, you must browse to the workflow itself, not just the logic app that contains it. From the Workflows page of your logic app instance, select the workflow and then navigate to its Overview page. 
 
-## Create a pipeline to trigger your Logic App email workflow
+## Create a pipeline to trigger your logic app workflow
 
-Once you create the Logic App workflow to send email, you can trigger it from a pipeline using a **Web** activity.  
+After you create the logic app workflow to send email, you can trigger it from a pipeline using a **Web** activity.  
 
 1. Create a new pipeline and find the **Web** activity under the **General** category, to drag it onto the editing canvas.
 
 1. Select the new **Web1** activity, and then select the **Settings** tab.
 
-   Provide the URL from the Logic App workflow you created previously in the **URL** field.
+   Provide the URL from the logic app workflow you created previously in the **URL** field.
 
    Provide the following JSON for the **Body**:
     ```json
@@ -85,9 +85,9 @@ Once you create the Logic App workflow to send email, you can trigger it from a
        }
     ```
     
-    Use dynamic expressions to generate useful messages for events in your pipelines.  Notice that the JSON format here matches the JSON format you defined in the Logic App, and you can also customize these as required.
+    Use dynamic expressions to generate useful messages for events in your pipelines.  Notice that the JSON format here matches the JSON format you defined in the logic app, and you can also customize these as required.
     
-    :::image type="content" source="media/how-to-send-email/pipeline-with-web-activity-calling-logic-app.png" alt-text="Shows a pipeline with a Web activity configured with the Logic App workflow URL and JSON message body.":::
+    :::image type="content" source="media/how-to-send-email/pipeline-with-web-activity-calling-logic-app.png" alt-text="Shows a pipeline with a Web activity configured with the logic app workflow URL and JSON message body.":::
 
 1. Select the background area of the pipeline designer to select the pipeline properties page and add a new parameter called receiver, providing an email address as its Default value.
    
