Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into nfs-30-support-for-blob-storage

Author: paulth1

articles/app-service/configure-ssl-certificate-in-code.md

@@ -17,7 +17,7 @@ ms.custom:
 
 [!INCLUDE [app-service-managed-certificate](./includes/managed-certs/managed-certs-note.md)]
 
-In your application code, you can access both [public key certificates and certificates that contain a private key that you add to Azure App Service.](configure-ssl-certificate.md). Your app code might act as a client and access an external service that requires certificate authentication. It might also need to perform cryptographic tasks. This article shows how to use public or private certificates in your application code.
+In your application code, you can access both [public key certificates and certificates that contain a private key that you add to Azure App Service.](configure-ssl-certificate.md). Your app code might act as a client and access an external service that requires certificate authentication. It might also need to perform cryptographic tasks. This article shows how to use publicly or privately signed certificates in your application code.
 
 This approach to using certificates in your code makes use of the Transport Layer Security (TLS) functionality in App Service, which requires your app to be in the Basic tier or higher. If your app is in the Free or Shared tier, you can [include the certificate file in your app repository](#load-a-certificate-from-a-file).
 
@@ -111,7 +111,7 @@ For languages that don't support or offer insufficient support for the Windows c
 
 ## Load a certificate from a file
 
-If you need to load a certificate file that you upload manually, it's better to upload the certificate by using [File Transfer Protocol Secure (FTPS)](deploy-ftp.md) instead of [Git](deploy-local-git.md), for example. Keep sensitive data like a private certificate out of source control.
+If you need to load a certificate file that you upload manually, it's better to upload the certificate by using [File Transfer Protocol Secure (FTPS)](deploy-ftp.md) instead of [Git](deploy-local-git.md), for example. Keep sensitive data like certificate private keys out of source control.
 
 ASP.NET and ASP.NET Core on Windows must access the certificate store even if you load a certificate from a file. To load a certificate file in a Windows .NET app, load the current user profile with the following command in <a target="_blank" href="https://shell.azure.com" >Cloud Shell</a>:
 
@@ -140,7 +140,7 @@ To see how to load a TLS/SSL certificate from a file in Node.js, PHP, Python, or
 
 The `WEBSITE_LOAD_CERTIFICATES` app setting makes the specified certificates accessible to your Windows or Linux custom containers (including built-in Linux containers) as files. The files are found under the following directories:
 
-| Container platform | Public certificates | Private certificates |
+| Container platform | Public certificate files (no private key) | Certificate files that include a private key |
 | - | - | - |
 | Windows container | `C:\appservice\certificates\public` | `C:\appservice\certificates\private` |
 | Linux container | `/var/ssl/certs` | `/var/ssl/private` |

articles/app-service/overview-hosting-plans.md

@@ -35,7 +35,7 @@ The pricing tier of an App Service plan determines what App Service features you
 | Category | Tiers | Description |
 |:-|:-|:-|
 | Shared compute | Free, Shared | Free and Shared, the two base tiers, run an app on the same Azure VM as other App Service apps, including apps of other customers. These tiers allocate CPU quotas to each app that runs on the shared resources. The resources can't scale out. These tiers are intended for only development and testing purposes. |
-| Dedicated compute | Basic, Standard, Premium, PremiumV2, PremiumV3, PremiumV4 | The Basic, Standard, Premium, PremiumV2, PremiumV3, and PremiumV4 tiers run apps on dedicated Azure VMs. Only apps in the same App Service plan share the same compute resources. The higher the tier, the more VM instances that are available to you for scale-out. |
+| Dedicated compute | Basic, Standard, Premium, PremiumV2, PremiumV3, PremiumV4 | The Basic, Standard, Premium, PremiumV2, PremiumV3, and PremiumV4 tiers run apps on dedicated Azure VMs. Only apps in the same App Service plan share the same compute resources (and those resources aren't shared with other customers). The higher the tier, the more VM instances that are available to you for scale-out. |
 | Isolated | IsolatedV2 | The IsolatedV2 tier runs dedicated Azure VMs on dedicated Azure virtual networks. This tier provides network isolation on top of compute isolation to your apps. It provides the maximum scale-out capabilities. |
 
 Each tier also provides a specific subset of App Service features. These features include custom domains and TLS/SSL certificates, autoscaling, deployment slots, backups, Azure Traffic Manager integration, and more. The higher the tier, the more features that are available. To find out which features are supported in each pricing tier, see the [App Service plan details](https://azure.microsoft.com/pricing/details/app-service/windows/#pricing).

articles/connectors/connectors-create-api-smtp.md

@@ -1,46 +1,46 @@
 ---
-title: Connect to SMTP from Azure Logic Apps
-description: Automate tasks and workflows that send email through your SMTP (Simple Mail Transfer Protocol) account using Azure Logic Apps.
+title: Connect to SMTP from Workflows
+description: Connect to SMTP (Simple Mail Transfer Protocol) accounts from integration workflows in Azure Logic Apps.
 services: logic-apps
 ms.suite: integration
-ms.reviewer: estfan, azla
+ms.reviewers: estfan, azla
 ms.topic: how-to
-ms.date: 02/19/2025
+ms.update-cycle: 1095-days
+ms.date: 03/11/2026
+# Customer intent: As an integration developer who works with Azure Logic Apps, I want to connect my logic app workflows to 
 ---
 
-# Connect to your SMTP account from Azure Logic Apps
+# Connect to your SMTP account from workflows in Azure Logic Apps
 
-[!INCLUDE [logic-apps-sku-consumption](~/reusable-content/ce-skilling/azure/includes/logic-apps-sku-consumption.md)]
+[!INCLUDE [logic-apps-sku-consumption](../logic-apps/includes/logic-apps-sku-consumption.md)]
 
 With Azure Logic Apps and the Simple Mail Transfer Protocol (SMTP) connector, 
 you can create automated tasks and workflows that send email from your SMTP account. 
 You can also have other actions use the output from SMTP actions. For example, 
-after your SMTP sends an email, you can notify your team in Slack with the Slack connector. 
-If you're new to logic apps, review [What is Azure Logic Apps?](../logic-apps/logic-apps-overview.md)
+after your SMTP sends an email, you can notify your team in Slack with the Slack connector.
 
 ## 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/pricing/purchase-options/azure-account?cid=msft_learn).
+* An Azure account and subscription. [Get a free Azure account](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn).
 
 * Your SMTP account and user credentials
 
-  Your credentials authorize your logic app to create 
+  Your credentials authorize your logic app workflow to create 
   a connection and access your SMTP account.
 
-* Basic knowledge about how to create logic apps
+* Basic knowledge about how to create logic app workflows
 
 * The logic app where you want to access your SMTP account. 
-To use an SMTP action, start your logic app with a trigger, 
+To use an SMTP action, start your logic app workflow with any trigger, 
 such as a Salesforce trigger, if you have a Salesforce account.
 
-  For example, you can start your logic app with the 
+  For example, you can start your logic app workflow with the 
   **When a record is created** Salesforce trigger. 
   This trigger fires each time that a new record, 
   such as a lead, is created in Salesforce. 
   You can then follow this trigger with the SMTP 
   **Send Email** action. That way, when the new 
-  record is created, your logic app sends an email 
+  record is created, your logic app workflow sends an email 
   from your SMTP account about the new record.
 
 ## Connector reference
@@ -51,8 +51,7 @@ For more technical details about this connector, such as triggers, actions, and
 
 [!INCLUDE [Create connection general intro](../../includes/connectors-create-connection-general-intro.md)]
 
-1. Sign in to the [Azure portal](https://portal.azure.com), 
-and open your logic app resource and workflow in the designer, if not open already.
+1. In the [Azure portal](https://portal.azure.com), open your logic app resource and workflow in the designer.
 
 1. [Follow these general steps to add the **SMTP** action that you want](/azure/logic-apps/create-workflow-with-trigger-or-action#add-action). 
 
@@ -71,8 +70,8 @@ and open your logic app resource and workflow in the designer, if not open alrea
 
 1. Save your logic app or continue building your logic app's workflow.
 
-## Next steps
+## Related content
 
-* [Managed connectors for Azure Logic Apps](/connectors/connector-reference/connector-reference-logicapps-connectors)
-* [Built-in connectors for Azure Logic Apps](built-in.md)
-* [What are connectors in Azure Logic Apps](introduction.md)
+- [Managed connectors for Azure Logic Apps](/connectors/connector-reference/connector-reference-logicapps-connectors)
+- [Built-in connectors for Azure Logic Apps](built-in.md)
+- [What are connectors in Azure Logic Apps](introduction.md)

articles/logic-apps/export-standard-logic-app-to-visual-studio-code.md

@@ -1,19 +1,20 @@
 ---
-title: Export Standard logic apps to Visual Studio Code
-description: Download your Standard logic app and workflows from the Azure portal into Visual Studio Code.
+title: Export Standard Workflows to Visual Studio Code
+description: Download and export Standard logic app workflows from the Azure portal to Visual Studio Code.
 ms.suite: integration
 services: logic-apps
 author: wsilveiranz
 ms.author: wsilveira
-ms.reviewer: estfan, azla
+ms.reviewers: estfan, azla
 ms.topic: how-to
-ms.date: 02/20/2025
-# As an Azure Logic Apps developer, I want to export my Standard logic app and workflows from the Azure portal into Visual Studio Code.
+ms.update-cycle: 365-days
+ms.date: 03/11/2026
+# As an Azure Logic Apps developer, I want to export my Standard logic app and workflows from the Azure portal to Visual Studio Code.
 ---
 
 # Export Standard logic apps from Azure portal to Visual Studio Code
 
-[!INCLUDE [logic-apps-sku-standard](../../includes/logic-apps-sku-standard.md)]
+[!INCLUDE [logic-apps-sku-standard](includes/logic-apps-sku-standard.md)]
 
 If you work on Standard logic app workflows using the Azure portal, you might find yourself wanting to use Visual Studio Code instead at some point. When you switch to Visual Studio Code and install the Azure Logic Apps (Standard) extension, you get the expanded benefits available only with the extension, for example:
 
@@ -61,7 +62,7 @@ This guide shows how to download your Standard logic app as a zip file package f
 
 1. In the Azure window, on the **Workspace** toolbar, open the **Azure Logic Apps** menu, and select **Create new logic app workspace from package...**.
 
-   :::image type="content" source="media/export-standard-logic-app-to-visual-studio-code/create-workspace-from-package.png" alt-text="Screenshot shows Visual Studio Code, Azure window, and Workspace toolbar with selected button for Azure Logic Apps, and selected option for Create new logic app workspace from package.":::
+   :::image type="content" source="media/export-standard-logic-app-to-visual-studio-code/create-workspace-from-package.png" alt-text="Screenshot shows Visual Studio Code, Azure window, Workspace toolbar with selected button for Azure Logic Apps, and selected option for Create new logic app workspace from package.":::
 
    The **Create New Logic App Workspace from Package** prompt window opens so you can select the zip file package that you want to import.
 
@@ -71,7 +72,9 @@ This guide shows how to download your Standard logic app as a zip file package f
 
    You're now prompted to select the folder where you want to create your workspace.
 
-1. From the prompt list, select **Browse**. Find and select the local repository folder where you want to create your workspace. When you're done, choose **Select**. Follow the additional prompts to continue creating your workspace.
+1. From the prompt list, select **Browse**. Find and select the local repository folder where you want to create your workspace. When you're done, choose **Select**.
+
+1. Follow the subsequent prompts to continue creating your workspace.
 
 1. Enter a name to use for your workspace.
 
@@ -107,6 +110,6 @@ If you have connections that use a managed identity, make sure that you update t
 
 ## Related content
 
-For more information about managing your Standard logic app project in Visual Studio Code, see the following documentation:
+For more information about managing your Standard logic app project in Visual Studio Code, see:
 
 - [Create Standard logic app workflow in single-tenant Azure Logic Apps using Visual Studio Code](/azure/logic-apps/create-single-tenant-workflows-visual-studio-code)

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

@@ -1,17 +1,19 @@
 ---
-title: Exchange EDIFACT messages in B2B workflows
-description: Exchange EDIFACT messages between partners by creating workflows with Azure Logic Apps and Enterprise Integration Pack.
+title: Exchange EDIFACT Messages in B2B Workflows
+description: Exchange EDIFACT messages between partners for B2B workflows in Azure Logic Apps.
 services: logic-apps
 ms.suite: integration
 author: divyaswarnkar
 ms.author: divswa
-ms.reviewer: estfan, azla
+ms.reviewers: estfan, azla
 ms.topic: how-to
-ms.date: 02/10/2025
+ms.update-cycle: 1095-days
+ms.date: 03/11/2026
 ms.custom: sfi-image-nochange
+# Customer intent: As a B2B integration developer who works with Azure Logic Apps, I want to set up message communication between trading partners in enterprise workflows.
 ---
 
-# Exchange EDIFACT messages using workflows in Azure Logic Apps
+# Exchange EDIFACT messages for B2B workflows in Azure Logic Apps
 
 To send and receive EDIFACT messages in workflows that you create using Azure Logic Apps, use the **EDIFACT** connector, which provides operations that support and manage EDIFACT communication.
 
@@ -57,7 +59,7 @@ The **EDIFACT** built-in connector has the following actions, which are similar
 
 ## Prerequisites
 
-* An Azure account and subscription. If you don't have a subscription yet, [sign up for a free Azure account](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn).
+* An Azure account and subscription. [Get a free Azure account](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn).
 
 * An [integration account resource](./enterprise-integration/create-integration-account.md) where you define and store artifacts, such as trading partners, agreements, certificates, and so on, for use in your enterprise integration and B2B workflows. This resource has to meet the following requirements:
 
@@ -254,15 +256,15 @@ The **EDIFACT** managed connector action named **Decode EDIFACT message** action
 
   * Split Interchange as transaction sets - suspend interchange on error.
 
-    The decoding action splits the interchange into transaction sets and parses each transaction set. If one or more transaction sets in the interchange fail validation, the action outputs all the transaction sets in that interchange to `badMessages`.
+    The decoding action splits the interchange into transaction sets and parses each transaction set. If one or more transaction sets in the interchange fail validation, the action outputs the transaction sets in that interchange to `badMessages`.
 
   * Preserve Interchange - suspend transaction sets on error.
 
     The decoding action preserves the interchange and processes the entire batched interchange. The action outputs only those transaction sets that fail validation to `badMessages`, and outputs the remaining transactions sets to `goodMessages`.
 
   * Preserve Interchange - suspend interchange on error.
 
-    The decoding action preserves the interchange and processes the entire batched interchange. If one or more transaction sets in the interchange fail validation, the action outputs all the transaction sets in that interchange to `badMessages`.
+    The decoding action preserves the interchange and processes the entire batched interchange. If one or more transaction sets in the interchange fail validation, the action outputs the transaction sets in that interchange to `badMessages`.
 
 * Generate a technical acknowledgment, functional acknowledgment, or both, if configured.
 
@@ -380,6 +382,6 @@ To handle an EDIFACT document or process an EDIFACT message that has a UN2.5 seg
 
      ![Screenshot showing the Azure portal with an EDIFACT agreement's "sendAgreement" section in the JSON editor, and the "schemaReferences" section is highlighted.](./media/logic-apps-enterprise-integration-edifact/agreement-send-schema-references.png)
 
-## Next steps
+## Related content
 
-* [EDIFACT message settings](logic-apps-enterprise-integration-edifact-message-settings.md)
+- [EDIFACT message settings](logic-apps-enterprise-integration-edifact-message-settings.md)

articles/logic-apps/move-logic-app-resources.md

@@ -1,11 +1,13 @@
 ---
-title: Move logic apps across subscriptions, resource groups, or regions
+title: Move Logic Apps to Other Subscriptions, Resource Groups, or Regions
 description: Migrate logic apps or integration accounts to other Azure subscriptions, resource groups, or locations (regions).
 services: logic-apps
 ms.suite: integration
-ms.reviewer: estfan, azla
+ms.reviewers: estfan, azla
 ms.topic: how-to
-ms.date: 02/19/2025
+ms.update-cycle: 365-days
+ms.date: 03/11/2026
+# Customer intent: As a developer who works with Azure Logic Apps, I want to move or migrate my logic app resources to other Azure resource groups, subscriptions, or regions.
 ---
 
 # Move logic app resources to other Azure resource groups, regions, or subscriptions
@@ -78,7 +80,7 @@ When you want to move a logic app to a different region, your options depend on
 
 * If you created and deployed your logic app by using continuous integration (CI) and continuous delivery (CD) tools, such as Azure Pipelines in Azure DevOps, you can deploy your app to another region by using those tools.
 
-For more information about deployment templates for logic apps, see these topics:
+For more information about deployment templates for logic apps, see these articles:
 
 * [Overview: Automate deployment for Azure Logic Apps by using Azure Resource Manager templates](../logic-apps/logic-apps-azure-resource-manager-templates-overview.md)
 * [Find, open, and download your logic app from the Azure portal into Visual Studio](../logic-apps/manage-logic-apps-with-visual-studio.md)
@@ -99,7 +101,7 @@ The template that you get from Visual Studio includes only the resource definiti
 
 1. In the [Azure portal](https://portal.azure.com), find and open your integration account.
 
-1. On your integration account's menu, under **Settings**, select **Export template**.
+1. On the integration account sidebar, under **Settings**, select **Export template**.
 
 1. On the toolbar, select **Download**, and save the template.