Upcoming Changes to HTTP/Teams Webhook Trigger URLs – How to Handle Impact?

(5) Share

Report

Posted on by Nour Abuzaid

191

Hi Community,
I recently came across the Microsoft documentation outlining upcoming changes to Power Automate flows that use HTTP or Teams Webhook triggers. Starting August 2025, Microsoft is updating the trigger URLs (currently using logic.azure.com) and will fully retire the old URLs by November 30, 2025.
🔗 Microsoft Docs – Changes to HTTP or Teams Webhook Trigger Flows

Key points:
1-New URL will appear in the HTTP trigger card.
2-The new URL might be longer than 255 characters, especially if using SAS authentication.
3-A warning banner will show in the flow designer with the old URL to be updated.
4-After Nov 30, 2025, the old URL will stop working, and flows will fail.

Categories:

Dynamics 365 general

I have the same question (0)

All responses (5)

Answers (1)

Adis 5,652 Super User 2025 Season 2 on at

Like (0)

Report

Upcoming Changes to HTTP/Teams Webhook Trigger URLs – How to Handle Impact?

Hello @Nour Abuzaid,

have the suggested answers led to a solution, i.e. is your question answered?

Kind regards, Adis

If this helped, please mark it as "Verified" for others facing the same issue

Keep in mind that it is possible to mark more than one answer as verified

Was this reply helpful? Yes No
Verified answer

Sahan Hasitha 2,598 on at

Like (4)

Report

Upcoming Changes to HTTP/Teams Webhook Trigger URLs – How to Handle Impact?

hi

Microsoft has announced upcoming changes to Power Automate flows that use HTTP or Teams Webhook triggers. Starting in August 2025, new trigger URLs will be introduced, and the existing URLs (*.logic.azure.com) will be retired on November 30, 2025. Flows using the old URLs will fail after this date. To avoid disruption, all impacted flows should be reviewed, updated with the new URLs, and tested well in advance. Any external systems or integrations referencing the old URLs will also need to be updated. It is recommended to begin this process early to ensure a smooth transition.

Was this reply helpful? Yes No
TB-14081552-0 2 on at

Like (0)

Report
Upcoming Changes to HTTP/Teams Webhook Trigger URLs – How to Handle Impact?

UPDATED: 5532852 | Power Platform admin center - According to this known issues report:

Queries could be fixed as early as 9/24

Randomly changing the signatures on URLs may not get fixed until 10/15.

Original message:

I started my remediation effort last week and have run into two major issues.

The new URLs don't support queries...yet. According to Microsoft this should be resolved in the first half of October. So, some flows cannot be remediated if they require queries in the URL.

Four days ago, Microsoft rotated the (SAS) signature on at least some of the new flow URLs. I had already remediated about 30 flows when I received notification that some have been failing 100% of the time. I did not see in the documentation about the change that signature rotation is part of the change. I verified by looking at the last successful flow runs and it matches the original new URL and the failures have the url with the updated signature.

What a screwed-up mess and a lot of wasted effort.

Was this reply helpful? Yes No
Nour Abuzaid 191 on at

Like (1)

Report

Upcoming Changes to HTTP/Teams Webhook Trigger URLs – How to Handle Impact?

Hi @Adis,

Thank you for the clarification and the LinkedIn reference. The guidance on PROD deployment/unmanaged flows is very helpful — I’ll make sure to share this with the team.

Kind regards,

Nour

Was this reply helpful? Yes No
Suggested answer

Adis 5,652 Super User 2025 Season 2 on at

Like (2)

Report

Upcoming Changes to HTTP/Teams Webhook Trigger URLs – How to Handle Impact?

Hi,

You may find some additional information in this LinkedIn Posts in the comments. A colleague of mine changed it yesterday. The changes are being rolled out region by region and may not be available at the same time for all regions.

(1) Post | Feed | LinkedIn

Usually it is enough to deploy the solution to your PROD environment. For unmanaged solutions its sufficient to safe the flow.

It only affects flows with the HTTP request trigger.

Kind regards, Adis

If this helped, please mark it as "Verified" for others facing the same issue

Keep in mind that it is possible to mark more than one answer as verified

Was this reply helpful? Yes No