Upcoming Changes to HTTP and Teams Webhook Triggers in Power Automate
September 3, 2025
By Blake Scarlavai
Microsoft has announced important updates that will affect Power Automate flows using HTTP triggers or Teams Webhook triggers. If your flows currently rely on trigger URLs containing logic.azure.com, action will be required to keep them running.
As of August 2025, flows will begin transitioning to new trigger URLs. By November 30, 2025, the old URLs will stop working entirely—meaning any flows that haven’t been updated will fail.
Watch our Youtube video here.
What’s Changing
New trigger URL
The HTTP trigger card in your flow’s designer will now display an updated URL. This new URL must be used for your flows to function correctly.
Longer URLs
The updated URLs may exceed 255 characters, particularly when Shared Access Signature (SAS) authentication is configured. You’ll need to verify that your destination systems can handle longer URLs.
Warning banner
A banner will appear in your flow details page or designer. This will show both the old and new URLs, with a reminder that the old URL will stop working after November 30, 2025.
⚠️ The banner will include a button to copy your new trigger URL. Make sure to update all references before the deadline.
Required Actions
To avoid disruption, follow these steps:
1. Update URL references
Locate every app or system (web apps, Power Apps, Environment Variables, etc.) that references the old trigger URL.
Replace it with the new trigger URL from your flow’s designer.
If you have Flows with HTTP triggers, there is a good chance you have Environment Variables that reference the old URL, use this query to identify those Environment Variables that need to be updated in each environment – https://orgname.crm.dynamics.com/api/data/v9.2/environmentvariablevalues?$select=value&$expand=EnvironmentVariableDefinitionId($select=displayname)&$filter=contains(value,%27logic.azure.com%27)
2. Validate the new URL
Test the new URL by triggering the flow and confirming that it executes successfully.
If you’re using SAS authentication, double-check that your system supports URLs longer than 255 characters.
3. Check relative path parameters
If your trigger URL includes a relative path parameter, make sure there’s no leading slash (/).
Beginning slashes can cause double slash errors. Adjust the relative path and test to confirm it works.
For more details, refer to Microsoft’s official guidance: