Action Required: Power Automate HTTP Trigger URLs Moving to api.powerplatform.com

This article explains the impact of an upcoming Microsoft infrastructure change that affects Power Automate flows using HTTP triggers. Starting November 30, 2025, all HTTP trigger URLs will transition from the legacy logic.azure.com domain to the new api.powerplatform.com domain.

Overview of Change

Microsoft is upgrading the infrastructure behind Power Automate by migrating HTTP trigger URLs from the legacy logic.azure.com domain to the new api.powerplatform.com domain. 

The cutover date is November 30, 2025. After this date, any flows still using the old logic.azure.com URLs will fail to trigger, potentially disrupting business processes that rely on these automations. 

Microsoft has already begun rolling out the new URLs, which are visible in the HTTP trigger card within the flow designer. Flow owners are being notified via email and in-product banners, but proactive review and remediation are strongly recommended to avoid broken flows.

Check out Microsoft's documentation on this matter for more information. 

Affected Areas

1. Power Automate Flows Using HTTP Triggers

Any flow using the “When an HTTP request is received” trigger will be affected. These flows rely on a specific URL endpoint to receive external calls. After the cutover, any flows still referencing the old logic.azure.com domain will fail to trigger, breaking integrations and automations that depend on them.

2. OnePlan Power Automate Connector

The OnePlan connector includes multiple triggers and actions that may internally reference HTTP endpoints. Specifically:

• The connector creates events in OnePlan that include HTTP trigger URLs.

These URLs may be used in custom JavaScript, embedded in external systems, or referenced in third-party integrations. Any instance where the old URL format is used, whether in code, documentation, or configuration will be impacted.

Required Actions

To ensure a smooth transition and avoid disruptions, organizations should take the following steps:

1. Identify Impacted Flows
   Audit all Power Automate flows using the “When an HTTP request is received” trigger, especially those integrated with the OnePlan connector. Look for any references to the old logic.azure.com domain.
    
2. Resave Flows to Generate New URLs
   Open each impacted flow and resave it. This will regenerate the HTTP trigger using the new api.powerplatform.com domain. For flows using the OnePlan connector, this action will also create a new event in OnePlan with the updated URL.
    
3. Update References Where Applicable
   Search for and update any external references to the old URL, including:
   • Custom JavaScript
   • Third-party integrations
   • Documentation or configuration files
4. Validate New URLs
   Test the new URLs to ensure they work as expected. Some systems may be sensitive to URL length or format, so validation is critical.
    
5. Optional: Migrate to a New Environment
   Some customers may prefer to create a new environment and migrate their flows ahead of the cutover. This approach allows for early generation of new URLs and may help avoid last-minute disruptions.