Share via

Can I replace a legacy *logic.azure.com* workflow url in an existing Logic app with a new power automate url?

David Tahvildaran 1 Reputation point
2025-11-25T16:24:37.1066667+00:00

We have received emails that tools using the workflow/trigger urls of the domain pattern *logic.azure.com * will stop working after November 30, 2025.

I had set up an Azure Logic App that sends alerts to different ms teams channels. The Overview page of that resource has that type of workflow url.

What are the remediation steps to ensure these automated alerts continue to fire? Can I generate a new flow in Power Automate and update the Azure Logic app workflow url? Or do I need to abandon Azure Logic apps entirely and start using Power Automate before the deadline?

A bit more context, the Azure Logic app is wired up to an Action Group and has multiple alerts based on our postgres flex servers that when the alert threshold is surpassed, fires alerts to some microsoft teams channel.

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

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Siddhesh Desai 650 Reputation points Microsoft External Staff Moderator
    2025-11-25T16:47:54.82+00:00

    Hi @David Tahvildaran ,

    Thank you for reaching out to Microsoft Q&A

    The deadline only applies to Power Automate HTTP/Teams webhook triggers using old logic.azure.com endpoints.

    What are the remediation steps to ensure these automated alerts continue to fire?

    Keep the Existing Logic Apps as it is and allow them to continue fire the alerts. you can also validate by sending test alert and check Logic app run history.

    You are not required to generate new Flow, just update the url to the newer one in Power-automate flows.

    If you have any flows (outside Logic Apps) whose trigger URLs contain logic.azure.com, update them:

    Open the flow in Power Automate.

    Copy the new trigger URL from the trigger card.

    Replace the old URL everywhere it’s referenced (scripts, configs, Teams connectors, etc.).

    Use this command: Get-AdminFlowWithMigratingTriggerUrl to find all impacted flows.

    Reference: https://learn.microsoft.com/en-us/power-automate/environment-architecture

    https://learn.microsoft.com/en-us/troubleshoot/power-platform/power-automate/flow-run-issues/triggers-troubleshoot?tabs=new-designer#changes-to-http-or-teams-webhook-trigger-flows-on-logic-apps-environment-architecture

    do I need to abandon Azure Logic apps entirely and start using Power Automate before the deadline?

    No. Logic Apps are not being retired. The November 30, 2025, change only affects Power Automate flows that use HTTP or Teams webhook triggers with URLs containing logic.azure.com. Your Logic App wired to an Azure Monitor Action Group will continue to work as it is.

    0 comments

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.