Forum Discussion

Simal00's avatar
Simal00
Occasional Reader
Jul 15, 2026

Azure Logic Apps Workflow Templates (Preview): Issues with Updates, Expressions, and Designer UI.

 

 

Hi Azure Logic Apps team, if someone from the team is monitoring this community, I would like to report a few issues I have encountered with the Logic Apps Workflow Templates (Preview) feature. These issues are impacting the user experience and require attention.

 

Workflow Template name update issue

I created a workflow template that was working correctly. However, when I try to edit the template and change its name, the update either fails or the new name is not saved. Other changes appear to work, but renaming the template is consistently problematic.

Expression update issue with Base64 output

When using the expression:

 

             base64(body('Create_CSV_table'))

 

            each time the email action is updated, the expression automatically changes back to:

 

           body('Create_CSV_table')

 

           This causes an Internal Server Error and requires manually fixing the expression every time the workflow is updated. This becomes very frustrating when                 managing multiple workflows.

 

Logic Apps designer responsiveness issue

The Logic Apps designer page is not fully responsive across different screen sizes. On my laptop screen, the Add Expression option disappears and is only visible when using a larger monitor. The designer should support different screen resolutions and provide a consistent user experience.

 

Thank you for looking into these issues. Logic Apps Workflow Templates is a very useful feature, and addressing these problems would greatly improve usability for developers and users.

 

accessibility
community

1 Reply

  • Jamony's avatar
    Jamony
    MCT
    Jul 15, 2026

    Good report—these look like two product issues plus one documented designer behavior.

     

    For the name, Microsoft’s template documentation says the JSON workflow name can be renamed only once. If you’re changing it after setup, the failure may be expected; the Profile display name is separate. If the Profile name will not save, capture the correlation or activity ID and open an Azure support request.

     

    For base64(...), the expression reference warns that Designer may hide the function and show only its argument. Check Code view after saving. If base64(...) remains in JSON, runtime behavior is preserved. Editing the argument in Designer can remove the function and its effect, so keep the workflow under source control and make the change through Code view or deployment until resolved.

     

    The missing Add Expression control at smaller resolutions looks like a preview UI defect. Browser zoom is only a workaround. Report browser version, resolution, zoom, Logic App SKU and region, timestamp, and screenshots through Azure Portal > Help + support; Community Lounge is not the product support queue.

     

    https://learn.microsoft.com/en-us/azure/logic-apps/expression-functions-reference#base64