Skip to content

Commit c87a715

Browse files
author
ecfan
committed
Updates for preview refresh
1 parent 63bd0de commit c87a715

File tree

2 files changed

+6
-9
lines changed

2 files changed

+6
-9
lines changed

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

Lines changed: 2 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.service: azure-logic-apps
66
ms.suite: integration
77
ms.reviewer: estfan, azla
88
ms.topic: how-to
9-
ms.date: 10/28/2024
9+
ms.date: 02/28/2025
1010
# Customer intent: As a developer, I want to create a Standard logic app workflow that can run on customer-managed infrastructure, which can include on-premises systems, private clouds, and public clouds.
1111
---
1212

@@ -29,12 +29,7 @@ This how-to guide shows how to create and deploy a Standard logic app workflow u
2929

3030
- Hybrid deployment for Standard logic apps is available and supported only in the [same regions as Azure Container Apps on Azure Arc-enabled AKS](../container-apps/azure-arc-overview.md#public-preview-limitations).
3131

32-
- The following capabilities currently aren't available in this preview release:
33-
34-
- Managed identity authentication
35-
- SAP access through the SAP built-in connector
36-
- C# custom code with .NET Framework and the built-in action named **Call local function in this logic app**
37-
- XSLT 1.0 for custom code
32+
- Managed identity authentication for managed API connectors currently isn't available in this preview release.
3833

3934
Azure Arc-enabled Kubernetes clusters currently don't support managed identity authentication for managed API connections. Instead, you must create your own app registration using Microsoft Entra ID. For more information, [follow these steps later in this guide](#authenticate-managed-api-connections).
4035

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

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.service: azure-logic-apps
66
ms.suite: integration
77
ms.reviewer: estfan, azla
88
ms.topic: how-to
9-
ms.date: 11/04/2024
9+
ms.date: 02/28/2025
1010
# Customer intent: As a developer, I need to set up the requirements to host and run Standard logic app workflows on infrastructure that my organization owns, which can include on-premises systems, private clouds, and public clouds.
1111
---
1212

@@ -53,7 +53,9 @@ With the hybrid option, you're responsible for the following items:
5353
- Your SQL Server license
5454
- A billing charge of $0.18 USD per vCPU/hour to support Standard logic app workloads
5555

56-
In this billing model, you pay only for what you need and scale resources for dynamic workloads without having to buy for peak usage. For workflows that use Azure-hosted connector operations, such as Microsoft Teams or Microsoft Office 365, [existing Standard (single-tenant) pricing](https://azure.microsoft.com/pricing/details/logic-apps/#pricing) applies to these operation executions.
56+
In this billing model, you pay only for what you need and scale resources for dynamic workloads without having to buy for peak usage. The CPU allocation that you select at logic app creation affects your billing rate.
57+
58+
For workflows that use Azure-hosted connector operations, such as Microsoft Teams or Microsoft Office 365, see [existing Standard (single-tenant) pricing](https://azure.microsoft.com/pricing/details/logic-apps/#pricing), which applies to these operation executions.
5759

5860
## Limitations
5961

0 commit comments

Comments
 (0)