Hello Jesse,
When using Azure Logic Apps, local functions (inline code) run in a sandboxed, in-process environment, which can limit support for certain libraries like Azure.Core
. Even if it's listed in the assemblies, it may not work as expected at runtime.
Regarding your question: Yes, the Isolated Process model in Azure Functions offers more flexibility and better support for complex dependencies like Azure.Core
. Logic Apps use an in-process model for inline code, which has limitations.
If your code needs Azure.Core
or other advanced libraries, the best approach is to move it into an Azure Function App (Isolated) and call it from your Logic App using an HTTP action.
For your reference, please review the following documentations for further clarifications:
- Create and run .NET code from Standard workflows in Azure Logic Apps
- Develop C# class library functions using Azure Functions
I hope this addresses your query. Please let me know if you need any further assistance or clarification.