web
You’re offline. This is a read only version of the page.
close
Skip to main content
News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics 365 | Integration, Dataverse... / Upcoming Changes to HT...
Microsoft Dynamics 365 | Integration, Dataverse...
Suggested answer

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

(1) ShareShare
ReportReport
Posted on by Nour Abuzaid 136
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)
  • Nour Abuzaid Profile Picture
    Nour Abuzaid 136 on at
    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

  • Suggested answer
    Adis Profile Picture
    Adis 5,432 Super User 2025 Season 2 on at
    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.
     
    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

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Dynamics 365 Community Calls Return
Join experts in person to explore low code and AI agents at the Power Platform Community Conference sponsored by Microsoft
Responsible AI policies for the Community

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Andrés Arias – Community Spotlight

We are honored to recognize Andrés Arias as our Community Spotlight honoree for…

Congratulations to the August Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Microsoft Dynamics 365 | Integration, Dataverse, and general topics

#1
DAnny3211 Profile Picture

DAnny3211 367

#2
Abhilash Warrier Profile Picture

Abhilash Warrier 137 Super User 2025 Season 2

#3
Martin Dráb Profile Picture

Martin Dráb 82 Most Valuable Professional

Last 30 days Overall leaderboard

Featured topics

Identifying an Org as CDS or Dynamics
Get batch job history log from D365 FO to Power Automate
Gross and Net Weight of Shipments feeding back into Sales Order (from External Source)

Product updates

Dynamics 365 release plans