Skip to content

Logic App Standard not cross-platform: NetFxWorker .exe blocks hybrid deployment on macOS ARM and Linux | XSLT Transformations in Logic App Standard fail on macOS/Linux due to hard .exe dependency #1354

@nxtdj

Description

@nxtdj

VSCode Dump

Bug Report: Logic App Standard fails to run cross-platform due to hard .exe dependency

Description

Logic App Standard workloads fail to run on macOS ARM (M1/M2/M3) and Linux containers because of a hard dependency on a .exe binary:

Steps to Reproduce the Bug or Issue


Why This Is Critical

  • The NetFxWorker.exe is downloaded as part of the extension bundle (e.g., 1.117.31).
  • It is required for executing XSLT via Logic App’s XsltAction.
  • This makes XSLT functionality unusable on macOS, Docker, or ARM64 environments — despite Logic App being advertised as cross-platform and hybrid-ready.

Expected Behavior

Logic App Standard should:

  • Provide a cross-platform XSLT engine using .NET (XslCompiledTransform, XsltProcessor, etc.)
  • Avoid hard dependencies on .exe files for workflow execution
  • Allow local development and Docker-based hybrid deployments to fully support XSLT

Steps to Reproduce

  1. Create a Logic App Standard workflow with an XsltAction
  2. Run it on macOS (M1/M2/M3) or Docker using linux/arm64 base
  3. Observe runtime error trying to execute .exe

Request

Please consider the following improvements:

  • ✳️ Replace .exe-based NetFxWorker with a cross-platform implementation for XSLT
  • ✳️ Or, allow injecting a custom worker or runtime that supports XSLT natively in .NET

This issue severely blocks developers and teams using macOS or Linux environments from working with XSLT transformations in Logic App Standard — a key feature in many B2B and data transformation scenarios.

Thanks in advance for your help and attention to this.

Error:

[2025-05-07T10:36:45.272Z] Failed to start Worker Channel.
Process fileName: ~/.azure-functions-core-tools/Functions/ExtensionBundles/Microsoft.Azure.Functions.ExtensionBundle.Workflows/1.117.31/NetFxWorker/Microsoft.Azure.Workflows.Functions.NetFxWorker.exe

[2025-05-07T10:36:45.272Z] System.Diagnostics.Process:
An error occurred trying to start process '.../Microsoft.Azure.Workflows.Functions.NetFxWorker.exe'
with working directory '~/Workspace/LogicAppsXsltTestApp/LAMapTester'. Permission denied.

[2025-05-07T10:36:45.276Z] Failed to start a new language worker for runtime: dotnet-isolated.

[2025-05-07T10:36:45.276Z] System.Diagnostics.Process:
An error occurred trying to start process '.../Microsoft.Azure.Workflows.Functions.NetFxWorker.exe'
with working directory '~/Workspace/LogicAppsXsltTestApp/LAMapTester'. Permission denied.

[2025-05-07T10:36:50.695Z] Host lock lease acquired by instance ID '000000000000000000000000807584C8'.
[2025-05-07T10:37:45.260Z] Starting worker process failed
[2025-05-07T10:37:45.260Z] Microsoft.Azure.WebJobs.Script.Grpc: The operation has timed out.
[2025-05-07T10:37:45.275Z] Failed to start Worker Channel.
Process fileName: /.azure-functions-core-tools/Functions/ExtensionBundles/Microsoft.Azure.Functions.ExtensionBundle.Workflows/1.117.31/NetFxWorker/Microsoft.Azure.Workflows.Functions.NetFxWorker.exe
[2025-05-07T10:37:45.275Z] System.Diagnostics.Process:
An error occurred trying to start process '.../Microsoft.Azure.Workflows.Functions.NetFxWorker.exe'
with working directory '
/Workspace/LogicAppsXsltTestApp/LAMapTester'. Permission denied.

Even Azure Logic App DataMapper Test functionality fails...

Image

Note: This issue builds on a related limitation discussed in earlier reports (e.g., March 2024), but at that time, full hybrid/containerized deployment for Logic App Standard was not yet available. Now that Logic Apps explicitly support hybrid environments and Dockerized execution, the continued dependency on .exe-based NetFxWorker blocks key functionality like XSLT in non-Windows environments and should be re-evaluated accordingly.

https://learn.microsoft.com/en-us/answers/questions/1616228/how-to-fix-netfxworker-issues-on-azure-functions-c

https://learn.microsoft.com/en-us/answers/questions/1616228/how-to-fix-netfxworker-issues-on-azure-functions-c

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions