Unanswered

Power Automate NEW HTTP Trigger Url's updated 4 days ago with new signature

(0) Share

Report

Posted on by CU19091446-0

I have been remediating the HTTP Trigger urls throughout our Power Automate environment and the third party integrations we use with it. Four days ago, all of the processes I updated to use the new URL started failing 100% of the time. Upon investigation, I found that the URL's SAS signatures have changed, breaking everything. I can clearly see in the logs where the original new url was successful and when it started failing.

First, this sucks quite a bit of time was put into updating our integrations for the new URLs.

Second, can anyone tell me if Micrsoft plans to rotate the signatures on a regular basis? Is this a new "feature" I have to work around or is this a unique bug related to the rollout? If the URL signatures are going to be rotated on a weekly/monthly frequency, HTTP triggers with SAS are going to become unusable.

Categories:

General topics

I have the same question (28)

All responses (8)

Answers (0)

Sort by

RS-22090919-0 4 on at

Like (0)

Report
Copy link

Link copied!

I have a very similar issue within our flows, I updated all of the third party integrations to point to the newly generated URLs on the 15/09/25 and all was working fine until this morning (22/09/25) where all of the third party integrations started showing a 404 not found error being returned from Power Automate. I have tried double checking the URLs and re-adding the triggers in the flows but it does not seem to have any effect. Could really do with some help working this out OR for someone at PA to fix this if it is a bug in the rollout

Was this reply helpful? Yes No
IH-23090336-0 2 on at

Like (0)

Report
Copy link

Link copied!

Any update or solution on this issue?

Was this reply helpful? Yes No
RS-22090919-0 4 on at

Like (0)

Report
Copy link

Link copied!

it is possible that this one is being covered under https://admin.powerplatform.microsoft.com/support/knownissues/5532852

Was this reply helpful? Yes No
DA-20100857-0 2 on at

Like (0)

Report
Copy link

Link copied!

I also would like to know more on the second question from @CU19091446-0 regarding rotation of the signatures on a regular basis.

Was this reply helpful? Yes No
SR-23100907-0 2 on at

Like (0)

Report
Copy link

Link copied!

I have the same problem. The url sig part changed. This caused our system can't work.

Can someone help on this issue ?

Was this reply helpful? Yes No
DH-23101104-0 2 on at

Like (0)

Report
Copy link

Link copied!

Same issue for us: Is it expected that the sig part of the workflow URLs are changing frequently?

1 people found this reply helpful.

Was this reply helpful? Yes No
TJ-28101508-0 2 on at

Like (0)

Report
Copy link

Link copied!

Having the same issue with the Sig portion changing. Any updates?

Was this reply helpful? Yes No
CU30102122-0 4 on at

Like (0)

Report
Copy link

Link copied!
I have contacted MS re this issue, here's thier response:

As stated, We’ve noticed that the sig value is hard‑coded in some callers. This will break when keys rotate or URLs change.

As a workaround, you can follow the below options:

Option 1 (Preferred): Use OAuth so callers send a Bearer token. No sig needed.

Option 2: If you keep using callback URLs, retrieve the current URL dynamically via the List Callback Url API and use it exactly as returned.

Hard‑coding sig is no longer supported. Please update integrations before 30 November 2025 to avoid 401 errors.

tbh I don't think this is realistic, as now we will loose a good feature for calling http requests directly which will affect the performance as well

5 people found this reply helpful.

Was this reply helpful? Yes No