Save draft

ecfan · ecfan · commit 79de7feef22b · 2024-10-29T13:41:55.000-07:00
diff --git a/articles/logic-apps/create-standard-workflows-hybrid-deployment.md b/articles/logic-apps/create-standard-workflows-hybrid-deployment.md
@@ -68,7 +68,9 @@ This how-to guide shows how to create and deploy a Standard logic app workflow u
   > basic Standard workflow before you try deploying to your own infrastructure. This test 
   > run helps isolate any errors that might exist in your Standard workflow project.
 
-## Create your Standard logic app in the Azure portal
+## Create your Standard logic app
+
+### [Portal](#tab/azure-portal)
 
 After you meet the prerequisites, create your Standard logic app for hybrid deployment by following these steps:
 
@@ -136,13 +138,15 @@ After you meet the prerequisites, create your Standard logic app for hybrid depl
 
    For more information about app settings and host settings, see [Edit app settings and host settings](edit-app-settings-host-settings.md).
 
-## Create your Standard logic app in Visual Studio Code
+### [Visual Studio Code](#tab/visual-studio-code)
 
 After you meet the prerequisites, but before you create your Standard logic app for hybrid deployment in Visual Studio Code, confirm that the following conditions are met:
 
 - Your SMB file share server is accessible.
 - Port 445 is open on the computer where you run Visual Studio Code.
 
+#### Create your logic app
+
 1. Run Visual Studio Code as administrator.
 
 1. In Visual Studio Code, on the Activity Bar, select the Azure icon.
@@ -175,6 +179,89 @@ After you meet the prerequisites, but before you create your Standard logic app
 
 1. Build your workflow as usual by adding a trigger and actions. For more information, see [Build a workflow with a trigger and actions](create-workflow-with-trigger-or-action.md).
 
+#### Deploy your logic app
+
+After you finish building your workflow, you can deploy your logic app to your Container Apps connected environment.
+
+1. In the Visual Studio Code **Explorer** window, open the shortcut menu for the workflow node, which is **my-stateful-workflow** in this example, and select **Deploy to logic app**.
+
+1. From the subscription list, select your Azure subscription.
+
+1. From the available logic apps list, select **Create new Logic App (Standard) in Azure**. Provide a globally unique logic app name that uses only lowercase alphanumeric characters or hyphens.
+
+   This example uses **my-logic-app-hybrid**.
+
+1. From the location list that appears, select the same Azure region where you have your connected environment.
+
+   This example uses **East US**.
+
+1. From the hosting plan list, select **Hybrid**.
+
+1. From the resource group list, select **Create new resource group**. Provide a name for your resource group.
+
+   This example uses **Hybrid-RG**.
+
+1. From the connected environment list, select your environment.
+
+1. Provide your previously saved values for the host name, SMB file share path, username, and password for your artifacts storage.
+
+1. Provide the connection string for the SQL database that you set up for runtime storage.
+
+   Visual Studio Code starts the deployment process for your Standard logic app.
+
+1. To monitor deployment status and Azure activity logs, from the **View** menu, select **Output**. In the window that opens, select **Azure**.
+
+After deployment completes, you can go to the Azure portal to view your logic app workflow.
+
+> [!NOTE]
+>
+> Several known issues exist in the portal around Standard logic apps that use the hybrid hosting option. 
+> These logic apps appear with the **Container App** label, which differs from Standard logic apps that 
+> use either the Workflow Service Plan or App Service Environment V3 hosting option. For more information, 
+> see [Known issues and troubleshooting - Azure portal](#known-issues-portal).
+
+---
+
+<a name="change-cpu-memory"></a>
+
+## Change CPU and memory allocation in the Azure portal
+
+To edit the CPU and memory settings for your Standard logic app resource, follow these steps:
+
+1. In the [Azure portal](https://portal.azure.com), open your Standard logic app resource.
+
+1. On the resource menu, under **Settings**, select **Containers**.
+
+1. On the **Containers** page toolbar, select **Edit and deploy**, which opens the **Edit a container** pane.
+
+1. On the **Properties** tab, under **Container resource allocation**, change the following values to fit your scenario:
+
+   | Property | Value | Description |
+   |----------|-------|-------------|
+   | **CPU cores** | - Default: 1 <br>- Minimum: 0.25 <br>- Maximum: 2 | Determines the CPU cores to assign to your container instance. You can increase this value by 0.25 cores up to the maximum value. The total number across all container instances for this logic app is limited to 2 cores. |
+   | **Memory** | - Default: 2 <br>- Minimum: 0.1 <br>- Maximum: 4 | Determines the memory capacity in gibibytes (Gi) to assign to your container instance. You can increase this value by 0.1 Gi up to the maximum value. The total capacity across all container instances for this logic app is limited to 4 Gi. |
+
+1. When you finish, select **Save**.
+
+<a name="change-scaling"></a>
+
+## Change replica scaling in the Azure portal
+
+You can control the automatic scaling for the range of replicas that deploy in response to a trigger event. A *replica* is a new instance of a workflow revision or version. To change the minimum and maximum values for this range, you can modify the scale rules to determine the event types that trigger scaling. For more information, see [Set scaling rules in Azure Container Apps](../container-apps/scale-app.md).
+
+1. In the [Azure portal](https://portal.azure.com), open your Standard logic app resource.
+
+1. On the resource menu, under **Settings**, select **Scale**.
+
+1. On the **Scale** page, under **Scale rule setting**, change the following values to fit your scenario:
+
+   | Property | Value | Description |
+   |----------|-------|-------------|
+   | **Min replicas** | - Default: 1 <br>- Minimum: 0 <br>- Maximum: 1000 | Determines the minimum number of replicas allowed for the revision at any given time. This value overrides scale rules and must be less than the maximum number of replicas. |
+   | **Max replicas** | - Default: 30 <br>- Minimum: 0 <br>- Maximum: 1000 | Determines the maximum number of replicas allowed for the revision at any given time. This value overrides scale rules. |
+
+1. When you finish, select **Save**.
+
 <a name="authenticate-managed-api-connections"></a>
 
 ## Set up authentication for managed API connections
@@ -183,7 +270,7 @@ To authenticate managed API connections in Standard logic app workflows hosted o
 
 ### Create an app registration with Microsoft Entra ID
 
-#### [Portal](#tab/azure-portal)
+#### Azure portal
 
 1. In the [Azure portal](https://portal.azure.com), follow [Quickstart: Register an application with the Microsoft identity platform](/entra/identity-platform/quickstart-register-app) to create an app registration.
 
@@ -205,9 +292,9 @@ To authenticate managed API connections in Standard logic app workflows hosted o
 
       :::image type="content" source="media/create-standard-workflows-hybrid-deployment/app-registration-object-id.png" alt-text="Screenshot shows app registration with selected object ID.":::
 
-1. Now, [add the saved values as environment variables](#add-environment-variables) to your Standard logic app resource.
+1. Now, [add the saved values as environment variables](#add-app-registration-values-environment-variables) to your Standard logic app resource.
 
-#### [Azure CLI](#tab/azure-cli)
+#### Azure CLI
 
 1. To create the app registration, use the [**az ad sp create** command](/cli/azure/ad/sp#az-ad-sp-create).
 
@@ -220,13 +307,11 @@ To authenticate managed API connections in Standard logic app workflows hosted o
    - Tenant ID
    - Client secret
 
-1. Now, [add the saved values as environment variables](#add-environment-variables) to your Standard logic app resource.
-
----
+1. Now, [add the saved values as environment variables](#add-app-registration-values-environment-variables) to your Standard logic app resource.
 
-<a name="add-environment-variables"></a>
+<a name="add-app-registration-values-environment-variables"></a>
 
-### Add environment variable values to your Standard logic app
+### Add app registration values to your Standard logic app
 
 1. In the [Azure portal](https://portal.azure.com), go to your Standard logic app resource.
 
@@ -247,11 +332,13 @@ To authenticate managed API connections in Standard logic app workflows hosted o
 
 1. When you finish, select **Save**.
 
+<a name="store-client-id-secret-for-reference"></a>
+
 ### Store and reference client ID and client secret
 
 You can store the client ID and client secret values in your logic app resource as secrets and then reference those values on the **Environment variables** tab instead.
 
-1. On the resource menu, under **Settings**, select **Secrets**.
+1. In the Azure portal, on the logic app resource menu, under **Settings**, select **Secrets**.
 
 1. On the toolbar, select **Add**.
 
@@ -262,54 +349,13 @@ You can store the client ID and client secret values in your logic app resource
    | **WORKFLOWAPP_AAD_CLIENTID** | <*my-client-ID*> |
    | **WORKFLOWAPP_AAD_CLIENTSECRET** | <*my-client-secret*> |
 
-## Deploy your logic app from Visual Studio Code
-
-After you finish building your workflow, you can deploy your logic app to your Container Apps connected environment.
-
-1. In the **Explorer** window, open the shortcut menu for the workflow node, which is **my-stateful-workflow** in this example, and select **Deploy to logic app**.
-
-1. From the subscription list, select your Azure subscription.
-
-1. From the available logic apps list, select **Create new Logic App (Standard) in Azure**. Provide a globally unique logic app name that uses only lowercase alphanumeric characters or hyphens.
-
-   This example uses **my-logic-app-hybrid**.
-
-1. From the location list that appears, select the same Azure region where you have your connected environment.
-
-   This example uses **East US**.
-
-1. From the hosting plan list, select **Hybrid**.
-
-1. From the resource group list, select **Create new resource group**. Provide a name for your resource group.
-
-   This example uses **Hybrid-RG**.
-
-1. From the connected environment list, select your environment.
-
-1. Provide your previously saved values for the host name, SMB file share path, username, and password for your artifacts storage.
-
-1. Provide the connection string for the SQL database that you set up for runtime storage.
-
-   Visual Studio Code starts the deployment process for your Standard logic app.
-
-1. To monitor deployment status and Azure activity logs, from the **View** menu, select **Output**. In the window that opens, select **Azure**.
-
-After deployment completes, you can go to the Azure portal to view your logic app workflow.
-
-> [!NOTE]
->
-> Several known issues exist in the portal around how you find your Standard logic app, which is created 
-> as a container app in this release. Your Standard logic app is also labeled differently from Standard 
-> logic apps deployed to single-tenant Azure and App Service environment v3. For more information, see 
-> [Known issues and troubleshooting - Azure portal](#known-issues-portal).
-
 ## Known issues and troubleshooting
 
 <a name="known-issues-portal"></a>
 
 ### Azure portal
 
-- Your Standard logic app is deployed as a [Container App resource](/azure/container-apps/overview), but the type appears as **Logic App (Hybrid)**.
+- Your Standard logic app is deployed and appears as a [Container App resource](/azure/container-apps/overview), but the type appears as **Logic App (Hybrid)**.
 
 - Your Standard logic app is listed in **Container Apps** resource list, not the **Logic apps** resource list.
 
