Microsoft has announced a critical change to Power Automate that requires urgent attention.
Power Automate flows with HTTP triggers or Teams Webhook triggers containing logic.azure.com in their URLs are being migrated to new URLs. You can see the new URL in the HTTP URL field of your flow’s trigger when you open the flow in the designer.
The old URLs will stop working on November 30, 2025, causing any flows still using them to fail.
These triggers are commonly used to connect flows with applications, including Dynamics 365, Power Apps, and third-party services.
If you use these triggers, you’ll need to take action to update your flows with the new URL. Early attention is strongly recommended to ensure your business processes operate smoothly after November 30.
How Microsoft is Communicating the Change
You may have already received email notifications if you are the owner of a flow impacted by this URL change.
Additionally, a warning banner will appear on your flow’s detail page and within the designer, providing the new URL and a clear warning message:
“The old trigger URL <trigger URL> will stop working on November 30, 2025. Your tools that use this flow WILL break unless you update them with the new URL.”
However, in many organisations, flows are owned by multiple team members, increasing the risk that these notifications may be overlooked.
We recommend proactively identifying all affected flows rather than relying on these email notifications.
What This Change Means for Your Organisation
The primary impact is that any system, application, or code that calls a Power Automate flow using an old trigger URL will stop working after November 30, 2025.
This disruption could affect business processes across your organisation, from automated notifications and approvals to complex data integrations between systems.
Additionally, the new URLs are significantly longer and may exceed 255 characters, particularly when using Shared Access Signature (SAS) authentication. You may need to verify that your destination systems can handle URLs of this length and adjust their configuration accordingly.
How to Identify Affected Flows
To avoid disruption, you should identify all affected flows in your environments, replace these trigger URLs before November 30, and check that each flow runs correctly.
This will involve some investigation, so we recommend starting early to ensure you have time to thoroughly test your processes and address any unexpected issues.
One approach could be to create a new flow configured to query your other flows and then filter this to find the relevant HTTP flows.
Another method to identify the affected trigger request flows involves accessing the Default Solution in Power Apps, locating the Process table, and filtering the Client Data column using the query “type”:”Request”,”kind”:”Http”.
This will give you a starting point by listing the flows that need reviewing.
Ideally, you will be using environment variables, which can simplify the update process. If you store flow URLs here, you can identify affected ones by accessing the Environment Variable Value table in the Default Solution and filtering for values containing logic.azure.com.
You should also consider any Power Automate flows that are manually triggered when users click a button in an application. These may have been hard-coded, so if your flow uses that method, you’ll need to replace the URL to ensure the flow works after November 30.
For a more thorough search, you could export your entire solution, open it in a code editor like Visual Studio Code, and perform a global search for logic.azure.com.
However, these approaches may be limited if some of your flows aren’t part of a solution. For early types of flows or any created by users that don’t form part of a solution, you may have to use more complex methods to find these.
Once you’ve identified all the old URLs, replace these with the new URLs provided by the Power Automate designer. After updating, the new URLs can be tested to ensure these flows remain triggered correctly.
Risks and Recommended Actions
The most significant risk is that your automated processes will break after November 30, leading to workflow failures and disruption.
We recommend the following actions:
Start Now: Don’t wait until the November deadline. Begin identifying, updating and testing your flows as soon as possible.
Be Thorough: A comprehensive search is necessary to find all instances of the old URLs. Don’t rely solely on email notifications.
Document Your Changes: Keep a record of your updated flows and where they are used. This will help with future maintenance and troubleshooting.
ServerSys Can Help
Need Help? Identifying these flows and managing this change can be complex, especially if your environments have numerous flows and integrations. If you need assistance or have concerns about this Power Automate update, please don’t hesitate to contact us.
Microsoft Resource:
Changes to HTTP or Teams Webhook Trigger Flows
