What does the new Logic Apps Automation SKU actually change?

Think of it as a new Logic Apps offering and management experience, not just a renamed plan. The preview description highlights a redesigned development portal, scaling and management options, real-time monitoring, and features aimed at building agent-style workflows, including AI sandboxes.

Since it’s still a preview, I’d treat those as capabilities to investigate rather than assume every part is ready for a production workload. Check that the specific connectors, deployment model, and operational controls you need are available.

For migration, don’t assume there’s a one-click conversion. Workflow definitions may be reusable, especially if they rely on familiar Logic Apps features, but moving them still calls for testing. Check triggers, connector behavior, identities, configuration, and deployment steps in the new resource.

I’d start with one noncritical workflow and compare its behavior before planning a broader move.

The cost question is still open. The preview pricing model hasn’t been established as a settled basis for planning, so a small test bill isn’t a useful forecast for a busy or scheduled workflow.

Work out your current workload patterns and compare them against the pricing and limits that are actually published before switching for savings. If you depend on a particular networking or hosting feature, confirm its preview availability too.

The AI angle doesn’t automatically make low-code workflows obsolete. Connectors, approvals, and a visual view of how a process runs can still be useful, especially in organizations where using a preapproved connector matters. A coded service may fit better when you need fine-grained control or a specialized runtime.

For now, I’d judge Automation by whether its new tools solve a real workflow problem for you, not just by the AI label.