Save draft

Author: ecfan

articles/logic-apps/create-standard-workflows-hybrid-deployment.md

@@ -120,14 +120,20 @@ After you meet the prerequisites, create your Standard logic app for hybrid depl
 
 1. In the Azure portal, on the logic app menu, under **Workflows**, you can add, edit, and manage workflows as usual.
 
-   Standard logic apps that you create with the hybrid deployment model support multiple workflow *revisions* or versions. Each time that you save changes to your workflow, Azure creates a new workflow revision.
-
-   > [!TIP]
+   > [!NOTE]
+   >
+   > A Standard logic app with the hybrid hosting option automatically creates a new *revision*, 
+   > or a version of the logic app resource, whenever you save changes to a child workflow.
+   >
+   > This revision might take a little time to activate, which means that after you save 
+   > any changes, you might want to wait several moments before you test your workflow.
+   >
+   > If your changes still haven't appeared in the workflow, you can check whether the revision exists:
    >
-   > After you save your workflow, wait for 1-2 minutes before you test your workflow.
-   > If your changes still don't appear in your workflow run, on the container app menu, 
-   > under **Revisions**, select **Revisions and replicas** to check whether the revision 
-   > was created and appears on the list.
+   > 1. On the resource menu, under **Revisions**, and select **Revisions and replicas**.
+   >
+   > 1. On the **Revisions and replicas** page, on the **Active revisions** tab, check whether 
+   >    a new revision appears on the list.
 
    For more information, see the following resources:
 
@@ -245,9 +251,9 @@ To edit the CPU and memory settings for your Standard logic app resource, follow
 
 <a name="change-scaling"></a>
 
-## Change replica scaling in the Azure portal
+## Change replica scaling in 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).
+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 container app 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.
 
@@ -262,6 +268,12 @@ You can control the automatic scaling for the range of replicas that deploy in r
 
 1. When you finish, select **Save**.
 
+<a name="inbound-traffic"></a>
+
+## Control inbound traffic to your logic app in Azure portal
+
+
+
 <a name="authenticate-managed-api-connections"></a>
 
 ## Set up authentication for managed API connections

articles/logic-apps/set-up-standard-workflows-hybrid-deployment-requirements.md

@@ -19,22 +19,22 @@ ms.date: 10/14/2024
 > This capability is in preview, incurs charges for usage, and is subject to the
 > [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
 
-Azure Logic Apps supports scenarios where you need to use your own managed infrastructure to deploy and host Standard logic app workflows by offering a hybrid deployment model. This model provides the capabilities for hosting integration solutions in partially connected environments that require local processing, storage, and network access. Standard logic app workflows are powered by the Azure Logic Apps runtime that is hosted on premises as an Azure Container Apps extension.
+Azure Logic Apps supports scenarios where you need to use and manage your own infrastructure to deploy and host Standard logic app workflows by offering a hybrid hosting option. This hybrid deployment model provides the capabilities for hosting integration solutions in partially connected environments that require local processing, storage, and network access. Standard logic app workflows are powered by the Azure Logic Apps runtime that is hosted on premises as an Azure Container Apps extension.
 
 The following architectural overview shows where Standard logic app workflows are hosted and run in the hybrid model. The partially connected environment includes the following resources for hosting and working with your Standard logic apps, which deploy as Azure Container Apps resources:
 
-- Azure Arc-enabled Kubernetes clusters, Azure Arc-enabled Kubernetes clusters on Azure Stack *hyperconverged infrastructure* (HCI)
+- Azure Arc-enabled Azure Kubernetes Service (AKS) clusters
 - A SQL database to locally store workflow run history, inputs, and outputs for processing
 - A Server Message Block (SMB) file share to locally store artifacts used by your workflows
 
 :::image type="content" source="media/set-up-standard-workflows-hybrid-deployment-requirements/architecture-overview.png" alt-text="Diagram with architectural overview for where Standard logic apps are hosted in a partially connected environment." border="false":::
 
+For hosting, you can also set up and use [Azure Arc-enabled Kubernetes clusters on Azure Stack *hyperconverged* infrastructure (HCI)](/azure-stack/hci/overview) or [Azure Arc-enabled Kubernetes clusters on Windows Server](/aks/hybrid/kubernetes-walkthrough-powershell).
+
 For more information, see the following documentation:
 
 - [What is Azure Kubernetes Service?](/azure/aks/what-is-aks)
 - [Core concepts for Azure Kubernetes Service (AKS)](/azure/aks/concepts-clusters-workloads)
-- [Azure Arc-enabled Azure Kubernetes Service (AKS) clusters](/azure/azure-arc/kubernetes/overview)
-- [Azure Arc-enabled Kubernetes clusters on Azure Stack hyperconverged infrastructure (HCI)](/azure-stack/hci/overview)
 - [Custom locations for Azure Arc-enabled Kubernetes clusters](/azure/azure-arc/platform/conceptual-custom-locations)
 - [What is Azure Container Apps?](../container-apps/overview.md)
 - [Azure Container Apps on Azure Arc](../container-apps/azure-arc-overview.md)
@@ -43,7 +43,11 @@ This how-to guide shows how to set up the necessary on-premises resources in you
 
 ## Limitations
 
-- Hybrid deployment is currently available and supported only for Azure Arc-enabled Azure Kubernetes Service (AKS) clusters and Azure Arc-enabled Kubernetes clusters on Azure Stack HCI.
+- Hybrid deployment is currently available and supported only for the following Azure Arc-enabled Kubernetes clusters:
+
+  - Azure Arc-enabled Kubernetes clusters
+  - Azure Arc-enabled Kubernetes clusters on Azure Stack HCI
+  - Azure Arc-enabled Kubernetes clusters on Windows Server
 
 ## Prerequisites
 
@@ -64,12 +68,14 @@ Your Kubernetes cluster requires inbound and outbound connectivity with the [SQL
 > [!NOTE]
 >
 > You can also create a [Kubernetes cluster on Azure Stack HCI infrastructure](/azure-stack/hci/overview) 
-> and apply the steps in this how-to guide to connect your cluster to Azure Arc and to set up your 
-> connected environment. For more information about Azure Stack HCI, see the following resources:
+> or [Kubernetes cluster on Windows Server](/aks/hybrid/overview) and apply the steps in this how-to guide 
+> to connect your cluster to Azure Arc and set up your connected environment. For more information 
+> about Azure Stack HCI and AKS on Windows Server, see the following resources:
 >
 > - [About Azure Stack HCI](/azure-stack/hci/deploy/deployment-introduction)
 > - [Deployment prerequisites for Azure Stack HCI](/azure-stack/hci/deploy/deployment-prerequisites)
 > - [Create Kubernetes clusters on Azure Stack HCI using Azure CLI](/azure/aks/hybrid/aks-create-clusters-cli)
+> - [Set up an Azure Kubernetes Service host on Azure Stack HCI and Windows Server and deploy a workload cluster using PowerShell](/aks/hybrid/kubernetes-walkthrough-powershell)
 
 1. Set the following environment variables for the Kubernetes cluster that you want to create: