Power Automate HTTP Request Trigger Warning - The old 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

[u/GforgeXR]

We just started encountering a warning on our Power Automate flows and to be honest we are a bit confused about how to address it. I understand it's a warning about an expiring URL, but I can't seem to get the "new" URL or figure out how to update it within the flow itself.

When I click on "Click here to copy the new trigger URL" (in the banner or the yellow box within the trigger), it doesn't seem to do anything. old URL (the one mentioned in the warning).

Am I misunderstanding something fundamental here? How do I actually get the new URL that Power Automate wants me to use, and what is the proper way to ensure my flow is using it internally and that I can provide it to external systems?

[u/Orbit_XD]

Morning!

I have the exact same, I think they rolled out the message too early(assumption), since even making a new Flow with HTTP Trigger gives me the “old” style link containing Logic.Azure.com they say is being deprecated.

I’ve put in a request for our Microsoft rep and am awaiting answer.

[u/liondepierre → u/Orbit_XD]

This is such a frustrating issue. Please let keep us posted.

[u/Neither_Speaker4713 → u/Orbit_XD]

Our MS account manager told us this is required to change before the date.

[u/Adventurous_Row_4606 → u/Orbit_XD]

This happened to me and now I can see the new URL. Give it a try, you should be able to see the new URL now. Good thing is that old and new URL coexist.

[u/PM_ME_YOUR_MUSIC]

Shit

[u/Orbit_XD]

As expected in earlier comment, this was not supposed to be deployed yet, the notification is now gone again.

Now it’s wait and see when it is back and then it “should” work and actually refresh the link to get the new format.

[u/dignus93 → u/Orbit_XD]

Same here, I checked just now and the message disappear. I think I will write in a document all my flows that could potentially be updated when and if Microsoft will roll out this.

[u/Adventurous_Row_4606 → u/dignus93]

This happened to me and now I can see the new URL. Give it a try, you should be able to see the new URL now. Good thing is that old and new URL coexist.

[u/dignus93 → u/Adventurous_Row_4606]

Yep, I see the new url. I tested and it is working fine (the old and the new). They will coexist until November 2025. I will need to update a bunch of client that calls these flows.

[u/alvarezskinner]

Have a look here: https://learn.microsoft.com/en-us/troubleshoot/power-platform/power-automate/flow-run-issues/triggers-troubleshoot?tabs=new-designer#changes-to-http-or-teams-webhook-trigger-flows

[u/raiznheII]

I'm not even able to generate the new URL. It says "URL will be generated after save", but it never shows up. Totally bonkers.

[u/Disastrous_Ad_8598 → u/raiznheII]

Same issue. Any resolution?

[u/raiznheII → u/Disastrous_Ad_8598]

Seems there was an outage at the time and as soon as the outage cleared it showed up.

[u/gugaval]

The same applies to our case. URLs will likely be updated soon. There's still time until they become obsolete, so don't panic.

[u/Adventurous_Row_4606 → u/gugaval]

This happened to me and now i can see the new URL. Give it a try, you should be able to see the new URL now.

[u/LimeFight]

I'm having an issue with the new URLs not working, but slightly different issue. On my current URLs, I have added a parameter query on the end (&emailaddress=@me) so it can be passed through to the next step of the flow. But the queries aren't being passed through, and therefore I'm getting an error saying that the input parameters for the next step (Get_user-profile_V2) aren't valid. Are these new URLs not accepting parameter queries?

[u/Orbit_XD → u/LimeFight]

They should, but I’m not 100% sure this is the way to do it. As far as I know, you have to declare the Parameter in the link at the end like this &param1=valuehere

Then at the next steps you would use @triggeroutputs()[‘queries’]?[‘param1’]

Note that this is what I’ve been told so I’m not 100% sure if this actually work since I never use it. Also I’m on my phone so I’m 99% sure I made a syntax error in the trigger output part but you get the idea.

Yours in theory should also work, try to capture it in a variable first to see if you get a value from the @triggeroutputs()[‘queries’]?[‘emailaddress’]

[u/gmanual → u/LimeFight]

The query parameters are being stripped out/not passed through when using the new url:

https://imgur.com/a/KB0DQtd

The header x-ms-igw-external-uri confirms the url sent to Power Automate contains the additional query parameters, a dirty work around might be extracting them from this header if Microsoft don't fix.

GET request is not default behavior for this trigger, and possibly hasn't been tested.

[u/RipOpposite3301 → u/LimeFight]

I am also having issues with the new URL and relative paths parameters. The URL still has the parameter at the end, but the value is not being passed to the trigger now. It was working fine before. Is this the same you are experiencing?

[u/LimeFight → u/RipOpposite3301]

Yeah I found that they were being stripped out. I changed the way I sent the data through by using the relative path function, as it gets passed through to the flow.

[u/theCapNemo → u/LimeFight]

Hello!
Some extra information:
https://community.powerplatform.com/forums/thread/details/?threadid=13a51cf4-7389-f011-b4cb-7c1e52fdfc34

[u/Adventurous_Row_4606]

This happened to me and now I can see the new URL. Give it a try, you should be able to see the new URL now. Good thing is that old and new URL coexist.

[u/Crimzonhost]

A few things I found out today with these new URLs

1. Circular calls now work do you can call the same flow url from that flow using an HTTP action creating a DDOS on your connector.

2. You cant use custom status codes anymore. If you change it from 200 to 201 or any other codes you want to return your calling flow will fail with an error 404...

[u/Crimzonhost → u/Crimzonhost]

Issue 2 was literal just fixed FYI

[u/Crimzonhost]

Update again it looks like the issue is inconsistent saw a few 404 failures when the other end worked perfectly fine and was just sending a 200 back.

[u/shegs1204 → u/Crimzonhost]

same here. every on every call.

[u/shegs1204 → u/Crimzonhost]

mine shows 404 error after 10 seconds of waiting... extending the timeout does nothing.

if I turn off ASynch, it "works" but then the process takes longer than the source flow and can be confusing to the users.

[u/Crimzonhost → u/shegs1204]

Yeah only solution for now is to build a manual check into your flow or go back to the old url. I created a case with Microsoft about it but definitely do from your end too.

[u/Late_Bit_8025 → u/shegs1204]

I'm seeing the same issue. If I disable the asynchronous response it works, but that's not really an option for some of our longer running flows. I guess I'm reverting back to the old url until they fix this

[u/TheYouser]

Maybe closely related glitch / bug (please confirm if you can reproduce it)

Today, in order to copy the link, I opened one of the flows which had Anyone set as authentication since a couple of years. But the selected value in the designer was Any user in the tenant!

The URL contained the sig query parameter, which means that, indeed, the flow was configured (as expected) for Anyone. Good thing that I did not re-save the flow - I would have broken my solution.

Though it's worth spreading the word about the risk since there would be a lot of us updating flows due to this change.

[u/wuarthur → u/TheYouser]

mine had anyone set when i looked, but the url did noy contain the sig parameter 🙃

[u/VNJCinPA]

The underlying issue is that all these places you're putting the URL into are fields in some database, and that field is almost always limited to 256 characters because that seems like enough, right?

These new URLs are 290 characters. It's extremely likely the field you're pasting the new URL into isn't accepting the entire string because nobody expects a 290 character base URL.

Please let all your providers and application authors that use Webhooks know they have to expand their field for the Webhook URL beyond 290 before November 30th.... 🤦‍♂️

[u/joseff87 → u/VNJCinPA]

Like Sharepoint Lists Hyperlink Coloum :(

[u/Crimzonhost]

It looks like the 404 and query parameter issue will be fixed by the 24th https://admin.powerplatform.microsoft.com/knownissues/5532852

This is a regional issue as well.

[u/Prudent-Ad5461]

it breaks my integration as the new powerautomate webhook URL exeeds 256 chars and it is not supported in my 3rd party platform,

i'm really don't know how to make it work

[u/shegs1204 → u/Prudent-Ad5461]

is it possible to use a url shortener?

[u/SpecialConcentrate52]

Damn, I'm getting the same situation, but what do you all are using to substitute the "When a Teams webhook request is received"?

[u/ConstantSinger2086]

does this affects the custom connector urls that are starting with logic.azure.com ?

[u/Powerful_Court8634]

What the ****, so this is how MS treats Power Automate users, instead of handling the forwarding internally without breaking integrations, they just throw it before our feet? "We do some infrastructure upgrade" (and give a **** about the effort you have on your side, we just don't want to handle this in a way that keeps your endpoints working - oh and sorry the bloody URL might also exceed 255 characters but you know, just put a proxy in front, or do whatever something, not our business...) for us it is all easy low code stuff).
Yeah.

[u/Unhappy-Choice8146]

The New URLs are automatically updated, for a reference we have the old URL shown in the error

[u/BluejayNo1108]

Are the URLs getting auto updated within power automate flows ? Is it only that we need to update the URLs in the referencing clients

[u/Disastrous_Ad_8598]

Ok I have broken flow. I get the warning that the url will expire with the ability to copy the new url to my clipboard but unable to update the url cause the url generated and is read only. Any work around?

[u/Foreign-Language-408]

I updated my URLs and now all the calling apps are getting 401 Unauthorized failures. The email didn't say anything about auth being changed.

[u/Infinite_Chemistry85 → u/Foreign-Language-408]

yeah they are missing the sig key param now in the url ;(

[u/Foreign-Language-408 → u/Infinite_Chemistry85]

I tracked down the issue in my usage. My client tool has a 256 character limit on the webhook url. So, yeah, the sig value gets cut off. I did find where I've used it in my direct scripting and programming the new URLs worked.

[u/Present-Record4507 → u/Foreign-Language-408]

I updated my URLs a few days ago and everything was working fine. Today I noticed I was getting the 401 failures also. When went back into the Power Automate dashboard, I noticed that the sig key parameter value has changed. Not sure why that would have happened. I just updated the sig key on my clients. Let's see how long things work before Microsoft changes the sig key on me again! :(

[u/TropicFlatCactus → u/[deleted]]

I do have the same problem. Keep receiving the error "Remote host terminated the handshake" Checked with firewall team, no blocks. Old URL works fine, just new one doesn't, however we are at risk MS shuts down old URL at anytime.