Power automate http triggered new URL again change with new URL in few days ago

Question

Power automate http triggered new URL again change with new URL in few days ago

Deepak Namdeo 51

Hi Team,

According to a recent alert, the Power Automate HTTP triggered URL has undergone an update with a new URL, and we are required to configure the new HTTP trigger URL in our SharePoint custom script by November 30, 2025.

Following this alert, we modified our custom script to use a new HTTP trigger URL. However, I noticed that the HTTP trigger URL was changed again past 6 days back and our application stopped working. So we have to re-configure our custom script with a new URL and lose our confidence with this update.

What are the motives behind updating the new trigger URL?

My question is that - Will the new HTTP trigger URL be updated frequently? If that's not the case, then when will it stabilize?

I appreciate any support you can provide on this.

Thanks,

Answer accepted by question author

1 additional answer

Your answer

Answer 1

Steven-N 15,160 Microsoft External Staff Moderator

Hi Deepak Namdeo

Thank you for reaching out to Microsoft Q&A forum

As states in this LINK, Microsoft is migrating HTTP trigger endpoints from the older logic.azure.com domain to the new api.powerplatform.com domain. This change is part of a broader infrastructure upgrade to improve security, scalability, and integration across Power Platform services. During this transition, URLs may appear to change as Microsoft finalizes the migration and ensures backward compatibility.

Regarding your question, as far I know, the new HTTP trigger URL is not expected to change frequently. The recent updates are part of a one-time migration from the older logic.azure.com domain to the new api.powerplatform.com domain for better security, scalability, and alignment with Power Platform services.

That said, in order to minimize disruption and prepare for stabilization, consider the following steps:

Update all flows and scripts to use the new HTTP trigger URL displayed in the Power Automate designer.
Use environment variables or centralized configuration for storing URLs instead of hardcoding them in scripts. This makes future updates easier.
Validate the new URL by triggering the flow and confirming successful execution.
Monitor official announcements from Microsoft regarding Power Automate updates to stay informed about any changes.
Complete migration before November 30, 2025, as old URLs will stop working after this date.

Relevant Documentation:

https://dori-uw-1.kuma-moon.com/en-us/power-automate/oauth-authentication?tabs=new-designer

https://dori-uw-1.kuma-moon.com/en-us/connectors/sharepointonline/

Please feel free to leave a comment below if you require any additional help.

Best regards

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Steven-N 15,160 Reputation points Microsoft External Staff Moderator

2025-10-29T12:03:23.3+00:00

Hi Deepak Namdeo

Just checking in to see if the above information was helpful.

If you have any further updates on this issue, please feel free to post back.

If you think my reply is helpful to you, please remember to mark it as an answer. Warm thanks.
Troy Stone 20 Reputation points

2025-10-31T13:06:33.4433333+00:00

Greetings,

I am with Deepak Namdeo on this. In 2025 we followed the notices very closely informing us that the endpoints would be changing to improve security, scalability, and integration across Power Platform services. Fine.

I have the original logic.azure.com domain trigger URLs and the new api.powerplatform.com domain trigger URLs and now what we have noted as New New Final Final trigger URLs after the unplanned 'surprise' changes.

We made the updates as required well within the window back in September, did exhaustive testing, and everything was working perfectly for about a month and a half then suddenly around the 22nd of October 2025 our triggers Simply Stopped Working.

After some quick troubleshooting we found that the endpoints had been changed… Again.

Same updated domain (api.powerplatform.com) but different URL's. By ‘different’ I mean everything was identical through signature version (sv) But the signature token had changed sv=1.0&sig=ABC123…

Has anyone at Microsoft ever heard of change control? This is ridiculous. We have critical functions relying on these triggers.

Warmest regards.
Steven-N 15,160 Reputation points Microsoft External Staff Moderator

2025-11-03T07:51:59.8233333+00:00

Hi Troy Stone

I completely understand that changes related to the endpoints may impact the functions your business has already set up, and I truly empathize with the challenges this might cause. Please know that our intention behind these adjustments is always to move toward improvement and future growth. While we recognize that the initial transition period may bring certain inconveniences, we sincerely hope you can appreciate the long-term benefits these changes aim to deliver.

Thank you once again for your patience and cooperation as we work together toward a better experience.

Best regards
Troy Stone 20 Reputation points

2025-11-06T16:28:01.82+00:00

Steven - changes related to the endpoints may impact the functions your business has already set up? My point was clearly that we ALREADY made the changes as directed. AND we tested. AND they worked perfectly for a month and a half. Then they CHANGED AGAIN.... Without notice. Same 'new' domain so that was not the reason for the second change.

The second change occurred without notice as best I can tell AND it occurred about 3 weeks into October meaning NOT at the end of November so there are clearly multiple disconnects but way to avoid acknowledging that.

I was 5 of 6 exams into MCSE back in 1999 and then abandoned certs due to a career change (management) so yeah I've been at this a while and I mention that just to say things were not always this way with MS. The company once followed something more closely resembling 'Best Practices' and as far as I can tell that is no longer the case.

Not taking ownership though... now that is something that hasn't changed.

Regards.
Gilmore, Kyle 10 Reputation points

2025-11-14T21:46:45.3666667+00:00

I've seen similar behavior. My url has changed 3 additional times since the first one:
9/9 - first change with new url
10/14 - new url
10/28 - new url
11/11 - new url

After each change it breaks due to an invalid url.

Steven-N Do you know why it is changing so frequently?
Sas P 5 Reputation points

2025-11-20T10:52:13.6466667+00:00

Hi

What I am confused about are the cards that are within a flow and includes a URL for which I cannot find the new URL for. I am not sure if these URIs are flows or not, but they are HTTP POST Requests. I tried to match the ID number after "workflows/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" a flow we have, but couldnt search for any.

Could you point me in the right direction on how to locate the new URI for this legacy URI showing in this card which I have attached? We have several other cards in various flows which call the URL that includes logic.azure.com.

TIA!

Sas
Troy Stone 20 Reputation points

2025-12-11T16:26:19.2233333+00:00

Greetings Sas. I believe this is a different use case. To the best of my knowledge, the Microsoft update applied only to HTTP Request (inbound trigger) URL endpoints. Counting top to bottom, left to right see HTTP (like your screenshot) vs #4 simply called Request. I have many Flows where I utilize endpoints. That is what this Q&A is referring to. I think you are good to go! ;)

Answer 2

Sid Naik 5

@Steven-N I did see the warning couple of months back which said the logic.azure.com urls would expire and now I see my url has changed to environment.api.powerplatform.com**I have not done any changes on my side , the alerts work and the warning is gone .

Are we good ?

Troy Stone 20 Reputation points

2025-11-06T16:35:52.89+00:00

Hello Sid,

Please check your endpoints. Even if the warnings are gone, if you did not migrate i.e. you are still using the logic.azure.com domain and did not migrate to the new domain (api.powerplatform.com) I would count on your HTTP Requests / webhooks failing. I would update the trigger URLs asap. It shouldn't take long. Far better to do that now. Imagine the mayor or a township supervisor revising all addresses in your city and the post office does not have a way to map new addresses to old addresses. Those HTTP Requests / webhooks will be directed to a non-existent address. Your flows will not run and I doubt you will receive an error message.

Best wishes.
Sid Naik 5 Reputation points

2025-11-10T18:43:07.98+00:00

Thank you Troy
Troy Stone 20 Reputation points

2025-12-11T16:52:59.6166667+00:00

Yes sir. You are very welcome.

Share via

Power automate http triggered new URL again change with new URL in few days ago

1 additional answer

Your answer