Formatting edits and add include file

Author: ecfan

articles/logic-apps/includes/visual-studio-extension-deprecation.md

@@ -0,0 +1,16 @@
+---
+ms.service: azure-logic-apps
+ms.author: estfan
+author: ecfan
+ms.date: 12/09/2024
+ms.topic: include
+---
+
+> [!IMPORTANT]
+>
+> The **Azure Logic Apps Tools for Visual Studio** extension is deprecated and no longer receives updates.
+> To create and manage logic app workflows using a local development environment, see the following documentation:
+>
+> - [Quickstart: Create and manage Consumption logic app workflows in multitenant Azure Logic Apps with Visual Studio Code](/azure/logic-apps/quickstart-create-logic-apps-visual-studio-code)
+>
+> - [Create a Standard logic app workflow in single-tenant Azure Logic Apps with Visual Studio Code](/azure/logic-apps/create-single-tenant-workflows-visual-studio-code)

articles/logic-apps/logic-apps-author-definitions.md

@@ -5,70 +5,66 @@ services: logic-apps
 ms.suite: integration
 ms.reviewer: estfan, azla
 ms.topic: how-to
-ms.date: 01/04/2024
+ms.date: 12/09/2024
 ---
 
 # Create, edit, or extend JSON for logic app workflow definitions in Azure Logic Apps
 
 [!INCLUDE [logic-apps-sku-consumption](~/reusable-content/ce-skilling/azure/includes/logic-apps-sku-consumption.md)]
 
-When you create enterprise integration solutions with automated workflows in
-[Azure Logic Apps](../logic-apps/logic-apps-overview.md), the underlying workflow definitions use simple and declarative JavaScript Object Notation (JSON) along with the [Workflow Definition Language (WDL) schema](../logic-apps/logic-apps-workflow-definition-language.md) for their description and validation. These formats make workflow definitions easier to read and understand without knowing much about code.
-When you want to automate creating and deploying logic app resources, you can include workflow definitions as
-[Azure resources](../azure-resource-manager/management/overview.md) inside [Azure Resource Manager templates](../azure-resource-manager/templates/overview.md).
-To create, manage, and deploy logic apps, you can then use [Azure PowerShell](/powershell/module/az.logicapp), [Azure CLI](../azure-resource-manager/templates/deploy-cli.md), or the [Azure Logic Apps REST APIs](/rest/api/logic/).
+When you create enterprise integration solutions with automated workflows in [Azure Logic Apps](/azure/logic-apps/logic-apps-overview), the underlying workflow definitions use simple and declarative JavaScript Object Notation (JSON) along with the [Workflow Definition Language (WDL) schema](/azure/logic-apps/logic-apps-workflow-definition-language) for their description and validation. These formats make workflow definitions easier to read and understand without knowing much about code. When you want to automate creating and deploying logic app resources, you can include workflow definitions as [Azure resources](/azure/azure-resource-manager/management/overview) inside [Azure Resource Manager templates](/azure/azure-resource-manager/templates/overview). To create, manage, and deploy logic apps, you can then use [Azure PowerShell](/powershell/module/az.logicapp), [Azure CLI](/azure/azure-resource-manager/templates/deploy-cli), or the [Azure Logic Apps REST APIs](/rest/api/logic/).
 
-To work with workflow definitions in JSON, open the Code View editor when working in the Azure portal or Visual Studio Code, or copy the definition into any editor that you want.
+To work with workflow definitions in JSON, open the code view editor when you work in the Azure portal, Visual Studio Code, or Visual Studio, or copy the definition into any editor that you want.
 
 > [!NOTE]
-> Some Azure Logic Apps capabilities, such as defining
-> parameters and multiple triggers in workflow definitions,
-> are available only in JSON, not the workflow designer.
-> So for these tasks, you must work in Code View or another editor.
+>
+> Some Azure Logic Apps capabilities, such as defining parameters and multiple triggers 
+> in workflow definitions, are available only in JSON, not the workflow designer. So, 
+> for these tasks, you must work in code view or another editor.
 
 ## Edit JSON - Azure portal
 
-1. Sign in to the
-<a href="https://portal.azure.com" target="_blank">Azure portal</a>.
+1. In the <a href="https://portal.azure.com" target="_blank">Azure portal</a> search box, enter and select **logic apps**. From the **Logic apps** page, select the Consumption logic app resource that you want.
 
-2. From the left menu, choose **All services**.
-In the search box, find "logic apps", and then from the results, select your logic app.
+1. On the logic app menu, under **Development Tools**, select **Logic app code view**.
 
-3. On your logic app's menu, under **Development Tools**, select **Logic App Code View**.
+   The code view editor opens and shows your logic app's workflow definition in JSON format.
 
-   The Code View editor opens and shows your workflow definition in JSON format.
+## Edit JSON - Visual Studio Code
+
+See [Edit deployed logic app in Visual Studio Code](/azure/logic-apps/quickstart-create-logic-apps-visual-studio-code#edit-logic-app)
 
 ## Edit JSON - Visual Studio
 
-Before you can work on your workflow definition in Visual Studio, make sure that you've [installed the required tools](../logic-apps/quickstart-create-logic-apps-with-visual-studio.md#prerequisites).
-To create a logic app with Visual Studio, review [Quickstart: Automate tasks and processes with Azure Logic Apps - Visual Studio](../logic-apps/quickstart-create-logic-apps-with-visual-studio.md).
+[!INCLUDE [visual-studio-extension-deprecation](includes/visual-studio-extension-deprecation.md)]
+
+Before you can work on a Consumption workflow definition in Visual Studio, make sure that you've [installed the required tools](/azure/logic-apps/quickstart-create-logic-apps-with-visual-studio#prerequisites). In Visual Studio, you can open logic apps that were created and deployed either directly from the Azure portal or as Azure Resource Manager projects from Visual Studio.
 
-In Visual Studio, you can open logic apps that were created and deployed either directly from the Azure portal or as Azure Resource Manager projects from Visual Studio.
+1. Open the Visual Studio solution, or [Azure Resource Group](/azure/azure-resource-manager/management/overview) project, that contains your logic app.
 
-1. Open the Visual Studio solution, or [Azure Resource Group](../azure-resource-manager/management/overview.md) project, that contains your logic app.
+1. Find and open your workflow definition, which by default, appears in an [Resource Manager template](/azure/azure-resource-manager/templates/overview), named **LogicApp.json**.
 
-2. Find and open your workflow definition, which by default, appears in an [Resource Manager template](../azure-resource-manager/templates/overview.md), named **LogicApp.json**.
-You can use and customize this template for deployment to different environments.
+   You can use and customize this template for deployment to different environments.
 
-3. Open the shortcut menu for your workflow definition and template.
-Select **Open With Logic App Designer**.
+1. Open the shortcut menu for your workflow definition and template. Select **Open With Logic App Designer**.
 
-   ![Open logic app in a Visual Studio solution](./media/logic-apps-author-definitions/open-logic-app-designer.png)
+   ![Open logic app in a Visual Studio solution.](./media/logic-apps-author-definitions/open-logic-app-designer.png)
 
    > [!TIP]
-   > If you don't have this command in Visual Studio 2019, check that you have the latest updates for Visual Studio.
+   >
+   > If you don't have this command in Visual Studio 2019, make sure that you have the latest updates for Visual Studio.
 
-4. At the bottom of the workflow designer, choose **Code View**.
+1. At the bottom of the workflow designer, choose **Code View**.
 
-   The Code View editor opens and shows your workflow definition in JSON format.
+   The code view editor opens and shows your workflow definition in JSON format.
 
-5. To return to designer view, at the bottom of the Code View editor, choose **Design**.
+1. To return to designer view, at the bottom of the code view editor, choose **Design**.
 
 ## Parameters
 
-The deployment lifecycle usually has different environments for development, test, staging, and production. When you have values that you want to reuse throughout your logic app without hardcoding or that vary based on your deployment needs, you can create an [Azure Resource Manager template](../azure-resource-manager/management/overview.md) for your workflow definition so that you can also automate logic app deployment.
+The deployment lifecycle usually has different environments for development, test, staging, and production. When you have values that you want to reuse throughout your logic app without hardcoding or that vary based on your deployment needs, you can create an [Azure Resource Manager template](/azure/azure-resource-manager/management/overview) for your workflow definition so that you can also automate logic app deployment.
 
-Follow these general steps to *parameterize*, or define and use parameters for, those values instead. You can then provide the values in a separate parameter file that passes those values to your template. That way, you can change those values more easily without having to update and redeploy your logic app. For full details, see [Overview: Automate deployment for logic apps with Azure Resource Manager templates](../logic-apps/logic-apps-azure-resource-manager-templates-overview.md).
+Follow these general steps to *parameterize*, or define and use parameters for, those values instead. You can then provide the values in a separate parameter file that passes those values to your template. That way, you can change those values more easily without having to update and redeploy your logic app. For full details, see [Overview: Automate deployment for logic apps with Azure Resource Manager templates](/azure/logic-apps/logic-apps-azure-resource-manager-templates-overview).
 
 1. In your template, define template parameters and workflow definition parameters for accepting the values to use at deployment and runtime, respectively.
 
@@ -80,7 +76,7 @@ Follow these general steps to *parameterize*, or define and use parameters for,
 
    When you specify the values for your workflow definition parameters, you can reference template parameters by using the parameters section that's outside your workflow definition but still inside the resource definition for your logic app. That way, you can pass template parameter values into your workflow definition parameters.
 
-1. Store the values for your parameters in a separate [parameter file](../azure-resource-manager/templates/parameter-files.md) and include that file with your deployment.
+1. Store the values for your parameters in a separate [parameter file](/azure/azure-resource-manager/templates/parameter-files) and include that file with your deployment.
 
 ## Process strings with functions
 
@@ -121,33 +117,29 @@ Azure Logic Apps has various functions for working with strings. For example, su
 
 These steps describe how this example processes this string, working from the inside to the outside:
 
-```
-"uri": "https://www.example.com/?id=@{replace(replace(base64(substring(parameters('order').companyName,5,sub(length(parameters('order').companyName), 5) )),'+','-') ,'/' ,'_' )}"
-```
+**`"uri": "https://www.example.com/?id=@{replace(replace(base64(substring(parameters('order').companyName,5,sub(length(parameters('order').companyName), 5) )),'+','-') ,'/' ,'_' )}"`**
 
-1. Get the [`length()`](../logic-apps/logic-apps-workflow-definition-language.md) for the company name, so you get the total number of characters.
+1. Get the [**`length()`**](/azure/logic-apps/logic-apps-workflow-definition-language) for the company name, so that you get the total number of characters.
 
-2. To get a shorter string, subtract `5`.
+1. To get a shorter string, subtract **5**.
 
-3. Now get a [`substring()`](../logic-apps/logic-apps-workflow-definition-language.md).
-Start at index `5`, and go to the remainder of the string.
+1. Now get a [**`substring()`**](/azure/logic-apps/logic-apps-workflow-definition-language). Start at index **`5`**, and go to the remainder of the string.
 
-4. Convert this substring to a [`base64()`](../logic-apps/logic-apps-workflow-definition-language.md) string.
+1. Convert this substring to a [**`base64()`**](/azure/logic-apps/logic-apps-workflow-definition-language) string.
 
-5. Now [`replace()`](../logic-apps/logic-apps-workflow-definition-language.md) all the `+` characters with `-` characters.
+1. Now [**`replace()`**](/azure/logic-apps/logic-apps-workflow-definition-language) all the **`+`** characters with **`-`** characters.
 
-6. Finally, [`replace()`](../logic-apps/logic-apps-workflow-definition-language.md) all the `/` characters with `_` characters.
+1. Finally, [**`replace()`**](/azure/logic-apps/logic-apps-workflow-definition-language) all the **`/`** characters with **`_`** characters.
 
 ## Map list items to property values, then use maps as parameters
 
 To get different results based a property's value, you can create a map that matches each property value to a result, then use that map as a parameter.
 
-For example, this workflow defines some categories as parameters and a map that matches those categories with a specific URL.
-First, the workflow gets a list of articles. Then, the workflow uses the map to find the URL matching the category for each article.
+For example, this workflow defines some categories as parameters and a map that matches those categories with a specific URL. First, the workflow gets a list of articles. Then, the workflow uses the map to find the URL matching the category for each article.
 
-*	The [`intersection()`](../logic-apps/logic-apps-workflow-definition-language.md) function checks whether the category matches a known defined category.
+*	The [**`intersection()`** function](/azure/logic-apps/logic-apps-workflow-definition-language) checks whether the category matches a known defined category.
 
-*	After getting a matching category, the example pulls the item from the map using square brackets: `parameters[...]`
+*	After the example gets a matching category, the example pulls the item from the map using square brackets: **`parameters[...]`**
 
 ``` json
 {
@@ -225,20 +217,19 @@ To get data from a data source that doesn't natively support *triggers*, you can
 "expression": "@less(actions('order').startTime,addseconds(utcNow(),-1))",
 ```
 
-1. From the `order` action, extract the `startTime`.
-2. Get the current time with `utcNow()`.
-3. Subtract one second:
+1. From the **`order`** action, extract the **`startTime`**.
+
+1. Get the current time with the **`utcNow()`** function.
 
-   [`addseconds(..., -1)`](../logic-apps/logic-apps-workflow-definition-language.md)
+1. Subtract one second: [**`addSeconds(..., -1)`**](/azure/logic-apps/logic-apps-workflow-definition-language)
 
-   You can use other units of time, like `minutes` or `hours`.
+   You can use other units of time such as **`minutes`** or **`hours`**.
 
-3. Now, you can compare these two values.
+1. Now, you can compare these two values.
 
    If the first value is less than the second value, then more than one second has passed since the order was first placed.
 
-To format dates, you can use string formatters. For example, to get the RFC1123, use [`utcnow('r')`](../logic-apps/logic-apps-workflow-definition-language.md).
-Learn more about [date formatting](../logic-apps/logic-apps-workflow-definition-language.md).
+To format dates, you can use string formatters. For example, to get the RFC1123, use [**`utcnow('r')`**](/azure/logic-apps/logic-apps-workflow-definition-language). Learn more about [date formatting](/azure/logic-apps/logic-apps-workflow-definition-language).
 
 ``` json
 {
@@ -290,12 +281,12 @@ Learn more about [date formatting](../logic-apps/logic-apps-workflow-definition-
 }
 ```
 
-## Next steps
+## Related content
 
-* [Run steps based on a condition (conditional statements)](../logic-apps/logic-apps-control-flow-conditional-statement.md)
-* [Run steps based on different values (switch statements)](../logic-apps/logic-apps-control-flow-switch-statement.md)
-* [Run and repeat steps (loops)](../logic-apps/logic-apps-control-flow-loops.md)
-* [Run or merge parallel steps (branches)](../logic-apps/logic-apps-control-flow-branches.md)
-* [Run steps based on grouped action status (scopes)](../logic-apps/logic-apps-control-flow-run-steps-group-scopes.md)
-* Learn more about the [Workflow Definition Language schema for Azure Logic Apps](../logic-apps/logic-apps-workflow-definition-language.md)
-* Learn more about [workflow actions and triggers for Azure Logic Apps](../logic-apps/logic-apps-workflow-actions-triggers.md)
+* [Run steps based on a condition (conditional statements)](/azure/logic-apps/logic-apps-control-flow-conditional-statement)
+* [Run steps based on different values (switch statements)](/azure/logic-apps/logic-apps-control-flow-switch-statement)
+* [Run and repeat steps (loops)](/azure/logic-apps/logic-apps-control-flow-loops)
+* [Run or merge parallel steps (branches)](/azure/logic-apps/logic-apps-control-flow-branches)
+* [Run steps based on grouped action status (scopes)](/azure/logic-apps/logic-apps-control-flow-run-steps-group-scopes)
+* [Workflow Definition Language schema for Azure Logic Apps](/azure/logic-apps/logic-apps-workflow-definition-language)
+* [Workflow actions and triggers for Azure Logic Apps](/azure/logic-apps/logic-apps-workflow-actions-triggers)

articles/logic-apps/manage-logic-apps-with-visual-studio.md

@@ -14,14 +14,7 @@ ms.date: 12/10/2024
 
 [!INCLUDE [logic-apps-sku-consumption](~/reusable-content/ce-skilling/azure/includes/logic-apps-sku-consumption.md)]
 
-> [!IMPORTANT]
->
-> The **Azure Logic Apps Tools for Visual Studio** extension is deprecated and no longer receives updates.
-> To create and manage logic app workflows using a local development environment, see the following documentation:
->
-> - [Quickstart: Create and manage Consumption logic app workflows in multitenant Azure Logic Apps with Visual Studio Code](/azure/logic-apps/quickstart-create-logic-apps-visual-studio-code)
->
-> - [Create a Standard logic app workflow in single-tenant Azure Logic Apps with Visual Studio Code](/azure/logic-apps/create-single-tenant-workflows-visual-studio-code)
+[!INCLUDE [visual-studio-extension-deprecation](includes/visual-studio-extension-deprecation.md)]
 
 You can create, edit, manage, and deploy automated workflows that integrate services, systems, apps, and data across enterprises and organizations by using [Azure Logic Apps](logic-apps-overview.md). Although you can perform these tasks in the Azure portal, you can also use a local development environment to create logic app projects that you can add to source control, publish different versions, and create Azure Resource Manager templates for different deployment environments.
 

articles/logic-apps/quickstart-create-logic-apps-visual-studio-code.md

@@ -233,10 +233,10 @@ To review your logic app in Azure portal, follow these steps:
 
 In Visual Studio Code, you can open and edit the workflow definition for an already deployed logic app in Azure.
 
-> [!IMPORTANT] 
-> Before you edit an actively running logic app in production, 
-> avoid the risk in breaking that logic app and minimize disruption by 
-> [disabling your logic app first](#disable-enable-logic-apps).
+> [!IMPORTANT]
+>
+> Before you edit an actively running logic app in production, avoid the risk in breaking that logic 
+> app and minimize disruption by [disabling your logic app first](#disable-enable-logic-apps).
 
 1. If you haven't signed in to your Azure account and subscription yet from inside Visual Studio Code, follow the [previous steps to sign in now](#access-azure).