Remove Visual Studio support references

Author: ecfan

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

@@ -849,11 +849,11 @@ When you have a workflow that starts with the **Request** trigger, you can retur
 
 ## Retest your logic app
 
-After you make updates to your logic app, you can run another test by rerunning the debugger in Visual Studio and sending another request to trigger your updated logic app, similar to the steps in [Run, test, and debug locally](#run-test-debug-locally).
+After you make updates to your logic app, you can run another test by rerunning the debugger in Visual Studio Code and sending another request to trigger your updated logic app, similar to the steps in [Run, test, and debug locally](#run-test-debug-locally).
 
 1. On the Visual Studio Code Activity Bar, open the **Run** menu, and select **Start Debugging** (F5).
 
-1. In Postman or your tool for creating and sending requests, send another request to trigger your workflow.
+1. In your tool for creating and sending requests, send another request to trigger your workflow.
 
 1. If you created a stateful workflow, on the workflow's overview page, check the status for the most recent run. To view the status, inputs, and outputs for each step in that run, select the ellipses (**...**) button for that run, and select **Show run**.
 
@@ -1384,7 +1384,7 @@ To fix the outdated bundle, follow these steps to delete the outdated bundle, wh
 > the Azure Logic Apps (Standard) extension, not the logic apps that you created using the Azure portal. 
 > See [Supported triggers and actions are missing from the designer in the Azure portal](create-single-tenant-workflows-azure-portal.md#missing-triggers-actions).
 
-1. Save any work that you don't want to lose, and close Visual Studio.
+1. Save any work that you don't want to lose, and close Visual Studio Code.
 
 1. On your computer, browse to the following folder, which contains versioned folders for the existing bundle:
 

articles/logic-apps/create-workflow-with-trigger-or-action.md

@@ -26,10 +26,9 @@ This guide shows the steps for Consumption and Standard logic app workflows.
 
 - To add an action, you have to start with a logic app resource and a workflow that minimally has a trigger.
 
-The following steps use the Azure portal, but you can also use the following tools to create a logic app and workflow:
-
-  - Consumption workflows: [Visual Studio](quickstart-create-logic-apps-with-visual-studio.md) or [Visual Studio Code](quickstart-create-logic-apps-visual-studio-code.md)
+The following steps use the Azure portal, but you can also use the following tools to build a logic app workflow:
 
+  - Consumption workflows: [Visual Studio Code](quickstart-create-logic-apps-visual-studio-code.md)
   - Standard workflows: [Visual Studio Code](create-single-tenant-workflows-visual-studio-code.md)
 
 <a name="add-trigger"></a>

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

@@ -14,7 +14,7 @@ ms.date: 12/09/2024
 
 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 you work in the Azure portal, Visual Studio Code, or Visual Studio, 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 or Visual Studio Code. You can also copy and paste the definition into any editor that you want.
 
 > [!NOTE]
 >

articles/logic-apps/logic-apps-azure-resource-manager-templates-overview.md

@@ -20,9 +20,8 @@ For example, if you deploy to environments for development, test, and production
 This overview describes the attributes in a Resource Manager template that includes a logic app workflow definition. Both the template and your workflow definition use JSON syntax, but some differences exist because the workflow definition also follows the [Workflow Definition Language schema](../logic-apps/logic-apps-workflow-definition-language.md). For example, template expressions and workflow definition expressions differ in how they [reference parameters](#parameter-references) and the values that they can accept.
 
 > [!TIP]
-> For the easiest way to get a valid parameterized logic app template that's mostly ready for deployment, use Visual Studio (free Community edition or greater) and the Azure Logic Apps Tools for Visual Studio. You can then either [create your logic app in Visual Studio](../logic-apps/quickstart-create-logic-apps-with-visual-studio.md) or [find and download an existing logic app from Azure into Visual Studio](../logic-apps/manage-logic-apps-with-visual-studio.md).
 >
-> Or, you can create logic app templates by using [Azure PowerShell with the LogicAppTemplate module](../logic-apps/logic-apps-create-azure-resource-manager-templates.md#azure-powershell).
+> You can create logic app templates by using [Azure PowerShell with the LogicAppTemplate module](../logic-apps/logic-apps-create-azure-resource-manager-templates.md#azure-powershell).
 
 The example logic app in this topic uses an [Office 365 Outlook trigger](/connectors/office365/) that fires when a new email arrives and an [Azure Blob Storage action](/connectors/azureblob/) that creates a blob for the email body and uploads that blob to an Azure storage container. The examples also show how to parameterize values that vary at deployment.
 
@@ -263,18 +262,9 @@ Your template has a `resources` object, which is an array that contains definiti
 ```
 
 > [!NOTE]
-> Templates can include resource definitions for multiple logic apps, so make sure that all your logic app resources specify the same Azure resource group. When you deploy the template to an Azure resource group by using Visual Studio, you're prompted for which logic app that you want to open. Also, your Azure resource group project can contain more than one template, so make sure that you select the correct parameters file when prompted.
-
-<a name="view-resource-definitions"></a>
-
-### View resource definitions
-
-To review the resource definitions for all the resources in an Azure resource group, [download your logic app from Azure into Visual Studio](../logic-apps/manage-logic-apps-with-visual-studio.md), which is the easiest way to create a valid parameterized logic app template that's mostly ready for deployment.
-
-For general information about template resources and their attributes, see these topics:
-
-* [Resources - Resource Manager template structure and syntax](../azure-resource-manager/templates/syntax.md#resources)
-* [Best practices for template resources](../azure-resource-manager/templates/best-practices.md#resources)
+>
+> Templates can include resource definitions for multiple logic apps, so make 
+> sure that all your logic app resources specify the same Azure resource group.
 
 <a name="logic-app-resource-definition"></a>
 
@@ -330,7 +320,7 @@ Here are the attributes that are specific to your logic app resource definition:
 |-----------|----------|------|-------------|
 | `state` | Yes | String | Your logic app's state at deployment where `Enabled` means your logic app is live and `Disabled` means that your logic app is inactive. For example, if you're not ready for your logic app to go live but want to deploy a draft version, you can use the `Disabled` option. |
 | `integrationAccount` | No | Object | If your logic app uses an integration account, which stores artifacts for business-to-business (B2B) scenarios, this object includes the `id` attribute, which specifies the ID for the integration account. |
-| `definition` | Yes | Object | Your logic app's underlying workflow definition, which is the same object that appears in code view and is fully described in the [Schema reference for Workflow Definition Language](../logic-apps/logic-apps-workflow-definition-language.md) topic. In this workflow definition, the `parameters` object declares parameters for the values to use at logic app runtime. For more information, see [Workflow definition and parameters](#workflow-definition-parameters). <p><p>To view the attributes in your logic app's workflow definition, switch from "design view" to "code view" in the Azure portal or Visual Studio, or by using a tool such as [Azure Resource Explorer](https://resources.azure.com). |
+| `definition` | Yes | Object | Your logic app's underlying workflow definition, which is the same object that appears in code view and is fully described in the [Schema reference for Workflow Definition Language](../logic-apps/logic-apps-workflow-definition-language.md) topic. In this workflow definition, the `parameters` object declares parameters for the values to use at logic app runtime. For more information, see [Workflow definition and parameters](#workflow-definition-parameters). <p><p>To view the attributes in your logic app's workflow definition, switch from designer view to code view in the Azure portal, or by using a tool such as [Azure Resource Explorer](https://resources.azure.com). |
 | `parameters` | No | Object | The [workflow definition parameter values](#workflow-definition-parameters) to use at logic app runtime. The parameter definitions for these values appear inside your [workflow definition's parameters object](#workflow-definition-parameters). Also, if your logic app uses [managed connectors](../connectors/managed.md) for accessing other services and systems, this object includes a `$connections` object that sets the connection values to use at runtime. |
 | `accessControl` | No | Object | For specifying security attributes for your logic app, such as restricting IP access to request triggers or run history inputs and outputs. For more information, see [Secure access to logic apps](../logic-apps/logic-apps-securing-a-logic-app.md). |
 | `runtimeConfiguration` | No | Object | For specifying any `operationOptions` properties that control the way that your logic app behaves at run time. For example, you can run your logic app in [high throughput mode](../logic-apps/logic-apps-limits-and-config.md#run-high-throughput-mode). |
@@ -608,7 +598,7 @@ For more information about workflow definition parameters, see [Parameters - Wor
 
 When your logic app creates and uses connections to other services and system by using [managed connectors](../connectors/managed.md), your template's `resources` object contains the resource definitions for those connections. Although you create connections from within a logic app, connections are separate Azure resources with their own resource definitions. Also, if your connection uses an on-premises data gateway resource, this resource definition exists separately from the connector resource definition. For more information, see [On-premises data gateway resource definitions](#data-gateway-resource-definitions) and [Microsoft.Web connectionGateways](/azure/templates/microsoft.web/connectiongateways?pivots=deployment-language-arm-template#connectiongatewayreference-1).
 
-To review connection resource definitions, [download your logic app from Azure into Visual Studio](../logic-apps/manage-logic-apps-with-visual-studio.md), which is the easiest way to create a valid parameterized logic app template that's mostly ready for deployment.
+The following example shows where you can find connection resource definitions:
 
 ```json
 {
@@ -696,7 +686,7 @@ Your logic app's resource definition also works with connection resource definit
 
   For example, metadata can include connection strings and access tokens, which you can store in [Azure Key Vault](../azure-resource-manager/templates/key-vault-parameter.md). To pass those values to your template parameters, you reference that key vault in the [parameters file](#template-parameter-files) that's used by your template at deployment. For more information about differences in referencing parameters, see [References to parameters](#parameter-references) later in this topic.
 
-  When you open your logic app's workflow definition in code view through the Azure portal or Visual Studio, the `$connections` object appears outside your workflow definition but at the same level. This ordering in code view makes these parameters easier to reference when you manually update the workflow definition:
+  When you open your logic app's workflow definition in code view through the Azure portal, the `$connections` object appears outside your workflow definition but at the same level. This ordering in code view makes these parameters easier to reference when you manually update the workflow definition:
 
   ```json
   {

articles/logic-apps/logic-apps-create-azure-resource-manager-templates.md

@@ -26,17 +26,6 @@ For more information about Azure Resource Manager templates, see the following t
 * [Author Azure Resource Manager templates](../azure-resource-manager/templates/syntax.md)
 * [Develop Azure Resource Manager templates for cloud consistency](../azure-resource-manager/templates/template-cloud-consistency.md)
 
-<a name="visual-studio"></a>
-
-## Create templates with Visual Studio
-
-For the easiest way to create valid parameterized logic app templates that are mostly ready for deployment, use Visual Studio (free Community edition or greater) and the Azure Logic Apps Tools for Visual Studio. You can then either [create your logic app in Visual Studio](../logic-apps/quickstart-create-logic-apps-with-visual-studio.md) or [find and download an existing logic app from the Azure portal into Visual Studio](../logic-apps/manage-logic-apps-with-visual-studio.md).
-
-By downloading your logic app, you get a template that includes the definitions for your logic app and other resources such as connections. The template also *parameterizes*, or defines parameters for, the values used for deploying your logic app and other resources. You can provide the values for these parameters in a separate parameters file. That way, you can more easily change these values based on your deployment needs. For more information, see these topics:
-
-* [Create logic apps with Visual Studio](../logic-apps/quickstart-create-logic-apps-with-visual-studio.md)
-* [Manage logic apps with Visual Studio](../logic-apps/manage-logic-apps-with-visual-studio.md)
-
 <a name="azure-powershell"></a>
 
 ## Create templates with Azure PowerShell

articles/logic-apps/logic-apps-create-variables-store-values.md

@@ -37,10 +37,9 @@ Variables exist and are global only within the workflow instance that creates th
 
   Before you can add actions for creating and working with variables, your workflow must start with a trigger as the first step in your workflow. For more information, see [Build a workflow with a trigger or action](create-workflow-with-trigger-or-action.md).
 
-The following steps use the Azure portal, but with the appropriate Azure Logic Apps extension, you can also use the following tools to create logic app workflows:
-
-* Consumption workflows: [Visual Studio](quickstart-create-logic-apps-with-visual-studio.md) or [Visual Studio Code](quickstart-create-logic-apps-visual-studio-code.md)
+The following steps use the Azure portal, but with the appropriate Azure Logic Apps extension, you can also use the following tools to build logic app workflows:
 
+* Consumption workflows: [Visual Studio Code](quickstart-create-logic-apps-visual-studio-code.md)
 * Standard workflows: [Visual Studio Code](create-single-tenant-workflows-visual-studio-code.md)
 
 Based on whether you have a Consumption or Standard workflow, follow the corresponding steps:

articles/logic-apps/logic-apps-enterprise-integration-b2b.md

@@ -16,7 +16,7 @@ ms.date: 01/04/2024
 
 When you have an integration account that defines trading partners and agreements, you can create an automated business-to-business (B2B) workflow that exchanges messages between trading partners by using Azure Logic Apps. Your workflow can use connectors that support industry-standard protocols, such as AS2, X12, EDIFACT, and RosettaNet. You can also include operations provided by other [connectors in Azure Logic Apps](/connectors/connector-reference/connector-reference-logicapps-connectors), such as Office 365 Outlook, SQL Server, and Salesforce.
 
-This article shows how to create an example logic app workflow that can receive HTTP requests by using a **Request** trigger, decode message content by using the **AS2 Decode** and **Decode X12** actions, and return a response by using the **Response** action. The example uses the workflow designer in the Azure portal, but you can follow similar steps for the workflow designer in Visual Studio.
+This article shows how to create an example logic app workflow that can receive HTTP requests by using a **Request** trigger, decode message content by using the **AS2 Decode** and **Decode X12** actions, and return a response by using the **Response** action. The example uses the workflow designer in the Azure portal, but you can follow similar steps for the workflow designer in Visual Studio Code.
 
 If you're new to logic apps, review [What is Azure Logic Apps](logic-apps-overview.md)? For more information about B2B enterprise integration, review [B2B enterprise integration workflows with Azure Logic Apps](logic-apps-enterprise-integration-overview.md).