Logic Apps Legacy Experience Retirement (Dec 2026) - Questions Before Switching

RichWilson-1620 20 Reputation points
2026-10-27T14:58:43.85+00:00

Hi all,

I'm currently using the legacy Logic Apps experience and have received the following message:

"You are using the legacy Logic Apps experience. Support for legacy experience ends in December 2026."

I previously switched to a newer Logic Apps experience but reverted back because I ran into issues.

At the time, the designer experience felt problematic enough that I didn't continue using it. I don't know whether those issues were purely visual or whether they could also have affected workflow development or behaviour, which is one of my concerns.

Before I switch again, I'd like to understand what others have experienced.

A few questions:

  1. Can you still revert back to the legacy experience after switching?
  2. If rollback is currently possible, has Microsoft indicated how long that option will remain available?
  3. Are there any known limitations, missing features, or behavioural differences compared to the legacy experience?
  4. Are there specific actions, connectors, triggers, expressions, scopes, loops, conditions, or other workflow components that are known not to convert cleanly to the new experience?
  5. Have you encountered any cases where workflows behaved differently after moving to the new experience?
  6. Are there any differences in code view, debugging, run history analysis, expressions, parameters, variables, or deployment processes that I should be aware of?

Any feedback, issues encountered, or lessons learned would be appreciated.

Azure Logic Apps
Azure Logic Apps

An Azure service that automates the access and use of data across clouds without writing code.

0 comments
Answer accepted by question author
Jose Benjamin Solis Nolasco 12,941 Reputation points Volunteer Moderator
2026-10-27T22:23:32.39+00:00

Welcome to Microsoft Q&A

Hello @RichWilson-1620 I hope you are doing well,

Most of your questions are reasonable concerns, but I don't believe Microsoft has published definitive answers for all of them.

Based on the information currently available:

  1. Rollback to the legacy experience
    • Microsoft previously provided a way to switch back to the legacy designer, but the long-term availability of rollback has not been guaranteed. Older communications emphasized that the legacy experience would eventually stop receiving updates and support.
  2. How long will rollback remain available?
    • I would recommend assuming that rollback could be removed as the retirement date approaches.

3-6. Feature differences, conversion issues, and behavioral changes

  • I am not aware of any comprehensive Microsoft document that lists workflow components that don't convert cleanly or behave differently after switching.
  • In general, the workflow definition (JSON) remains the source of truth. Most concerns reported by customers historically have been related to the designer experience, rendering, editing, or visualization rather than runtime execution.
  • If you have complex workflows with nested conditions, loops, scopes, custom connectors, or heavily edited code view definitions, I would strongly recommend testing them in a non-production environment before fully adopting the newer experience.

A practical approach would be:

  • Export or source-control your workflow definitions.
  • Test a representative set of your most complex Logic Apps in the new experience.
  • Validate designer rendering, save operations, deployment, run history inspection, and expression editing before committing to the migration.

Useful references:

If my answer helped you resolve your issue, please consider marking it as the correct answer. This helps others in the community find similar solutions.

Was this answer helpful?

1 person found this answer helpful.

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.