Merge pull request #273008 from ecfan/deployment-slots

Azure Logic Apps: Support deployment slots

Author: v-dirichards

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

@@ -63,6 +63,18 @@ In single-tenant Azure Logic Apps, workflows in the same logic app resource and
 
 * Starting mid-October 2022, new Standard logic app workflows in the Azure portal automatically use Azure Functions v4. Throughout November 2022, existing Standard workflows in the Azure portal are automatically migrating to Azure Functions v4. Unless you deployed your Standard logic apps as NuGet-based projects or pinned your logic apps to a specific bundle version, this upgrade is designed to require no action from you nor have a runtime impact. However, if the exceptions apply to you, or for more information about Azure Functions v4 support, see [Azure Logic Apps Standard now supports Azure Functions v4](https://techcommunity.microsoft.com/t5/integrations-on-azure-blog/azure-logic-apps-standard-now-supports-azure-functions-v4/ba-p/3656072).
 
+## Best practices and recommendations
+
+For optimal designer responsiveness and performance, review and follow these guidelines:
+
+- Use no more than 50 actions per workflow. Exceeding this number of actions raises the possibility for slower designer performance. 
+
+- Consider splitting business logic into multiple workflows where necessary.
+
+- Have no more than 10-15 workflows per logic app resource.
+
+More workflows in your logic app raise the risk of longer load times, which negatively affect performance. If you have mission-critical logic apps that require zero downtime deployments, consider [setting up deployment slots](set-up-deployment-slots.md).
+
 <a name="create-logic-app-resource"></a>
 
 ## Create a Standard logic app resource
@@ -351,16 +363,6 @@ In this example, the workflow runs when the Request trigger receives an inbound
 
       ![Screenshot that shows Outlook email as described in the example](./media/create-single-tenant-workflows-azure-portal/workflow-app-result-email.png)
 
-## Best practices and recommendations
-
-For optimal designer responsiveness and performance, review and follow these guidelines:
-
-- Use no more than 50 actions per workflow. Exceeding this number of actions raises the possibility for slower designer performance. 
-
-- Consider splitting business logic into multiple workflows where necessary.
-
-- Have no more than 10-15 workflows per logic app resource.
-
 <a name="review-run-history"></a>
 
 ## Review workflow run history

articles/logic-apps/logic-apps-limits-and-config.md

@@ -1,21 +1,24 @@
 ---
 title: Limits and configuration reference guide
-description: Reference guide to limits and configuration information for Azure Logic Apps.
+description: Reference guide about the limits and configuration settings for logic app resources and workflows in Azure Logic Apps.
 services: logic-apps
 ms.suite: integration
 ms.reviewer: rohithah, laveeshb, rarayudu, azla
 ms.topic: reference
-ms.date: 03/22/2024
+ms.date: 04/26/2024
 ---
 
 # Limits and configuration reference for Azure Logic Apps
 
+[!INCLUDE [logic-apps-sku-consumption-standard](../../includes/logic-apps-sku-consumption-standard.md)]
+
 > For Power Automate, review [Limits and configuration in Power Automate](/power-automate/limits-and-config).
 
 This reference guide describes the limits and configuration information for Azure Logic Apps and related resources. Based on your scenario, solution requirements, the capabilities that you want, and the environment where you want to run your workflows, you choose whether to create a Consumption logic app workflow that runs in *multitenant* Azure Logic Apps or an integration service environment (ISE). Or, create a Standard logic app workflow that runs in *single-tenant* Azure Logic Apps or an App Service Environment (v3 - Windows plans only).
 
 > [!NOTE]
-> Many limits are the same across the available environments where Azure Logic Apps runs, but differences are noted where they exist. 
+>
+> Many limits are the same across the available environments where Azure Logic Apps runs, but differences are noted where they exist.
 
 The following table briefly summarizes differences between a Consumption logic app and a Standard logic app. You'll also learn how single-tenant Azure Logic Apps compares to multitenant Azure Logic Apps and an ISE for deploying, hosting, and running your logic app workflows.
 
@@ -29,7 +32,7 @@ The following tables list the values for a single workflow definition:
 
 | Name | Limit | Notes |
 | ---- | ----- | ----- |
-| Workflows per region per Azure subscription | - Consumption: 1,000 workflows where each logic app is limited to 1 workflow <br><br>- Standard: Unlimited, based on the selected hosting plan, app activity, size of machine instances, and resource usage, where each logic app can have multiple workflows ||
+| Workflows per region per Azure subscription | - Consumption: 1,000 workflows where each logic app always has only 1 workflow <br><br>- Standard: Unlimited, based on the selected hosting plan, app activity, size of machine instances, and resource usage, where each logic app can have multiple workflows | For optimal performance guidelines around Standard logic app workflows, see [Best practices and recommendations](create-single-tenant-workflows-azure-portal.md#best-practices-and-recommendations). |
 | Workflow - Maximum name length | - Consumption: 80 characters <br><br>- Standard: 32 characters ||
 | Triggers per workflow | - Consumption (designer): 1 trigger <br>- Consumption (JSON): 10 triggers <br><br>- Standard: 1 trigger | - Consumption:  Multiple triggers are possible only when you work on the JSON workflow definition, whether in code view or an Azure Resource Manager (ARM) template, not the designer. <br><br>- Standard: Only one trigger is possible, whether in the designer, code view, or an Azure Resource Manager (ARM) template. |
 | Actions per workflow | 500 actions | To extend this limit, you can use nested workflows as necessary. |

articles/logic-apps/media/set-up-deployment-slots/delete-deployment-slot.png

@@ -0,0 +1,286 @@
+---
+title: Enable deployment slots for zero downtime deployment
+description: Set up deployment slots to enable zero downtime deployment for Standard workflows in Azure Logic Apps.
+services: logic-apps
+ms.suite: integration
+ms.reviewer: estfan, wsilveira, azla
+ms.topic: how-to
+ms.date: 04/26/2024
+
+#Customer intent: As a logic app developer, I want to set up deployment slots on my logic app resource so that I can deploy with zero downtime.
+---
+
+# Set up deployment slots to enable zero downtime deployment in Azure Logic Apps (preview)
+
+[!INCLUDE [logic-apps-sku-standard](../../includes/logic-apps-sku-standard.md)]
+
+> [!NOTE]
+> This capability is in preview and is subject to the 
+> [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
+
+To deploy mission-critical logic apps that are always available and responsive, even during updates or maintenance, you can enable zero downtime deployment by creating and using deployment slots. Zero downtime means that when you deploy new versions of your app, end users shouldn't experience disruption or downtime. Deployment slots are isolated nonproduction environments that host different versions of your app and provide the following benefits:
+
+- Swap a deployment slot with your production slot without interruption. That way, you can update your logic app and workflows without affecting availability or performance.
+
+- Test and validate any changes in a deployment slot before you apply those changes to the production slot.
+
+- Roll back to a previous version, if anything goes wrong with your deployment.
+
+- Reduce the risk of negative performance when you must exceed the [recommended number of workflows per logic app](create-single-tenant-workflows-azure-portal.md#best-practices-and-recommendations).
+
+With deployment slots, you can achieve continuous delivery and improve your applications' quality and reliability. For more information about deployment slots in Azure and because Standard logic app workflows are based on Azure Functions extensibility, see [Azure Functions deployment slots](../azure-functions/functions-deployment-slots.md).
+
+:::image type="content" source="media/set-up-deployment-slots/overview.png" alt-text="Screenshot shows Azure portal, Standard logic app resource, and deployment slots page." lightbox="media/set-up-deployment-slots/overview.png":::
+
+### Known issues and limitations
+
+- Nonproduction slots are created in read-only mode.
+
+- The nonproduction slots dispatcher is turned off, which means that workflows can only run when they're in the production slot.
+
+- Traffic distribution is disabled for deployment slots in Standard logic apps.
+
+- Deployment slots for Standard logic apps don't support the following scenarios:
+
+  - Blue-green deployment
+  - Product verification testing before slot swapping
+  - A/B testing
+
+## Prerequisites
+
+- 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).
+
+- To work in Visual Studio Code with the Azure Logic Apps (Standard) extension, you'll need to meet the prerequisites described in [Create Standard workflows with Visual Studio Code](create-single-tenant-workflows-visual-studio-code.md#prerequisites). You'll also need a Standard logic app project that you want to publish to Azure.
+
+- [Azure Logic Apps Standard Contributor role permissions](logic-apps-securing-a-logic-app.md?tabs=azure-portal#standard-workflows)
+
+- An existing Standard logic app resource in Azure where you want to create your deployment slot and deploy your changes. You can create an empty Standard logic app resource without any workflows. For more information, see [Create example Standard workflow in single-tenant Azure Logic Apps](create-single-tenant-workflows-azure-portal.md).
+
+## Create a deployment slot
+
+The following options are available for you to create a deployment slot:
+
+### [Portal](#tab/portal)
+
+1. In [Azure portal](https://portal.azure.com), open your Standard logic app resource where you want to create a deployment slot.
+
+1. On the resource menu, under **Deployment**, select **Deployment slots (Preview)**.
+
+1. On the toolbar, select **Add**.
+
+1. In the **Add Slot** pane, provide a name, which must be unique and uses only lowercase alphanumeric characters or hyphens (**-**), for your deployment slot.
+
+   > [!NOTE]
+   >
+   > After creation, your deployment slot name uses the following format: <*logic-app-name-deployment-slot-name*>.
+
+1. When you're done, select **Add**.
+
+### [Visual Studio Code](#tab/visual-studio-code)
+
+1. In Visual Studio Code, open the Standard logic app project that you want to deploy.
+
+1. Open the command palette. (Keyboard: Ctrl + Shift + P)
+
+1. From the command list, select **Azure Logic Apps: Create Slot**, and follow the prompts to provide the required information:
+
+   1. Enter and select the name for your Azure subscription.
+
+   1. Enter and select the name for your existing Standard logic app in Azure.
+
+   1. Enter a name, which must be unique and uses only lowercase alphanumeric characters or hyphens (**-**), for your deployment slot.
+
+### [Azure CLI](#tab/azure-cli)
+
+Run the following Azure CLI command:
+
+`az functionapp deployment slot create --name {logic-app-name} --resource-group {resource-group-name} --slot {slot-name}`
+
+To enable a system-assigned managed identity on your Standard logic app deployment slot, run the following Azure CLI command:
+
+`az functionapp identity assign --name {logic-app-name} --resource-group {resource-group-name} --slot {slot-name}`
+
+---
+
+## Confirm deployment slot creation
+
+After you create the deployment slot, confirm that the slot exists on your deployed logic app resource.
+
+1. In the [Azure portal](https://portal.azure.com), open your Standard logic app resource.
+
+1. On the resource menu, under **Deployment**, select **Deployment slots (Preview)**.
+
+1. On the **Deployment slots** page, under **Deployment Slots (Preview)**, find and select your new deployment slot.
+
+   > [!NOTE]
+   >
+   > After creation, your deployment slot name uses the following format: <*logic-app-name-deployment-slot-name*>.
+
+## Deploy logic app changes to a deployment slot
+
+The following options are available for you to deploy logic app changes in a deployment slot:
+
+### [Portal](#tab/portal)
+
+Unavailable at this time. Please follow the steps for Visual Studio Code or Azure CLI to deploy your changes.
+
+### [Visual Studio Code](#tab/visual-studio-code)
+
+1. In Visual Studio Code, open the Standard logic app project that you want to deploy.
+
+1. Open the command palette. (Keyboard: Ctrl + Shift + P)
+
+1. From the command list, select **Azure Logic Apps: Deploy to Slot**, and follow the prompts to provide the required information:
+
+   1. Enter and select the name for your Azure subscription.
+
+   1. Enter and select the name for your existing Standard logic app in Azure.
+
+   1. Select the name for your deployment slot.
+
+1. In the message box that appears, confirm that you want to deploy the current code in your project to the selected slot by selecting **Deploy**. This action overwrites any existing content in the selected slot.
+
+1. After deployment completes, you can update any settings, if necessary, by selecting **Upload settings** in the message box that appears.
+
+### [Azure CLI](#tab/azure-cli)
+
+Run the following Azure CLI command:
+
+`az logicapp deployment source config-zip --name {logic-app-name} --resource-group {resource-group-name} --slot {slot-name} --src {deployment-package-local-path}`
+
+---
+
+## Confirm deployment for your changes
+
+After you deploy your changes, confirm that the changes appear in your deployed logic app resource.
+
+1. In the [Azure portal](https://portal.azure.com), open your Standard logic app resource.
+
+1. On the resource menu, under **Deployment**, select **Deployment slots (Preview)**.
+
+1. On the **Deployment slots** page, under **Deployment Slots (Preview)**, find and select your deployment slot.
+
+1. On the resource menu, select **Overview**. On the **Notifications** tab, check whether any deployment issues exist, for example, errors that might happen during app startup or around slot swapping:
+
+   :::image type="content" source="media/set-up-deployment-slots/deployment-slot-notifications.png" alt-text="Screenshot shows Azure portal, logic app deployment slot resource with Overview page, and selected Notifications tab." lightbox="media/set-up-deployment-slots/deployment-slot-notifications.png":::
+
+1. To verify the changes in your workflow, under **Workflows**, select **Workflows**, and then select a workflow, which appears in read-only view.
+
+## Swap a deployment slot with the production slot
+
+The following options are available for you to swap a deployment slot with the current production slot:
+
+### [Portal](#tab/portal)
+
+1. In [Azure portal](https://portal.azure.com), open your Standard logic app resource where you want to swap slots.
+
+1. On the resource menu, under **Deployment**, select **Deployment slots (Preview)**.
+
+1. On the toolbar, select **Swap**.
+
+1. On the **Swap** pane, under **Source**, select the deployment slot that you want to activate.
+
+1. Under **Target**, select the production slot that you want to replace with the deployment slot.
+
+   > [!NOTE]
+   >
+   > **Perform swap with preview** works only with logic apps that enabled deployment slot settings.
+
+1. Under **Config Changes**, review the configuration changes for the source and target slots.
+
+1. When you're ready, select **Start Swap**.
+
+1. Wait for the operation to successfully complete.
+
+### [Visual Studio Code](#tab/visual-studio-code)
+
+1. In Visual Studio Code, open your Standard logic app project.
+
+1. Open the command palette. (Keyboard: Ctrl + Shift + P)
+
+1. From the command list, select **Azure Logic Apps: Swap Slot**, and follow the prompts to provide the required information:
+
+   1. Enter and select the name for your Azure subscription.
+
+   1. Enter and select the name for your existing Standard logic app in Azure.
+
+   1. Select the deployment slot that you want to make as the active slot.
+
+   1. Select the production slot that you want to swap with the deployment slot.
+
+   1. Wait for the operation to successfully complete.
+
+### [Azure CLI](#tab/azure-cli)
+
+Run the following Azure CLI command:
+
+`az functionapp deployment slot swap --name {logic-app-name} --resource-group {resource-group-name} --slot {slot-name} --target-slot production`
+
+---
+
+## Confirm success for your slot swap
+
+After you swap slots, verify that the changes from your deployment slot now appear in the production slot.
+
+1. In the [Azure portal](https://portal.azure.com), open your Standard logic app resource.
+
+1. On the resource menu, under **Workflows**, select **Workflows**, and then select a workflow to review the changes.
+
+## Delete a deployment slot
+
+The following options are available for you to delete a deployment slot from your Standard logic app resource.
+
+### [Portal](#tab/portal)
+
+1. In the [Azure portal](https://portal.azure.com), open your Standard logic app resource.
+
+1. On the resource menu, under **Deployment**, select **Deployment slots (Preview)**.
+
+1. On the **Deployment slots** page, under **Deployment Slots (Preview)**, select the deployment slot that you want to delete.
+
+1. On the deployment slot resource menu, select **Overview**.
+
+1. On the **Overview** toolbar, select **Delete**.
+
+1. Confirm deletion by entering the deployment slot name, and then select **Delete**.
+
+   :::image type="content" source="media/set-up-deployment-slots/delete-deployment-slot.png" alt-text="Screenshot shows Azure portal, deployment slot resource with Overview page opened, and delete confirmation pane with deployment slot name to delete." lightbox="media/set-up-deployment-slots/delete-deployment-slot.png":::
+
+### [Visual Studio Code](#tab/visual-studio-code)
+
+1. In Visual Studio Code, open your Standard logic app project.
+
+1. Open the command palette. (Keyboard: Ctrl + Shift + P)
+
+1. From the command list, select **Azure Logic Apps: Delete Slot**, and follow the prompts to provide the required information:
+
+   1. Enter and select the name for your Azure subscription.
+
+   1. Enter and select the name for your existing Standard logic app in Azure.
+
+   1. Select the deployment slot that you want to delete.
+
+1. In the message box that appears, confirm that you want to delete selected deployment slot by selecting **Delete**.
+
+### [Azure CLI](#tab/azure-cli)
+
+Run the following Azure CLI command:
+
+`az functionapp deployment slot delete --name {logic-app-name} --resource-group {resource-group-name} --slot {slot-name} --target-slot production`
+
+---
+
+## Confirm deployment slot deletion
+
+After you delete a deployment slot, verify that the slot no longer exists on your deployed Standard logic app resource.
+
+1. In the [Azure portal](https://portal.azure.com), open your Standard logic app resource.
+
+1. On the resource menu, under **Deployment**, select **Deployment slots (Preview)**.
+
+1. On the **Deployment slots** page, under **Deployment Slots (Preview)**, confirm that the deployment slot no longer exists.
+
+## Related content
+
+- [Deployment best practices](../app-service/deploy-best-practices.md)
+- [Azure Functions deployment slots](../azure-functions/functions-deployment-slots.md)