Home / Inspire / Action required: update Power Automate URLs before November 30

Action required: update Power Automate URLs before November 30

Microsoft is updating the URLs used by certain Power Automate flows to improve security and reliability. If your organization uses flows triggered by HTTP requests or Teams Incoming Webhooks, you must update them before November 30, 2025 to avoid service interruptions.

Microsoft has already sent alerts to Power Automate superusers and administrators, and your IT team may have already updated the affected flows. To avoid accidental changes, users who do not manage flows should verify with their IT team before taking any action.

Note: This update does not apply to sovereign cloud environments.

Why is Microsoft making this change?

Microsoft is moving Power Automate HTTP and Teams Webhook triggers from the legacy logic.azure.com domain to api.powerplatform.com. This update improves security, scalability, and consistency across Power Platform services, ensuring better integration and long-term reliability.

Why This Matters for BPA Clients

BPA’s solutions rely heavily on Power Automate for workflow automation and integration. If your flows use HTTP triggers or Teams Incoming Webhooks, they will stop working after November 30, 2025 unless updated. This change is critical to keep BPA processes; such as approvals, notifications, and data synchronization running smoothly.

How to Prepare for This Change

Step 1: Identify affected flows

  1. Sign in to Power Automate.
  2. Go to My flows and Team flows
  3. Use the search/filter bar and search for HTTP or Webhook
  4. Open any results and check the trigger action: if the trigger is When an HTTP request is received or Teams Incoming Webhook, the flow requires an update (unless it has already been updated)

Note: If your organization uses a large number of Power Automate flows, Microsoft provides alternative methods for identifying affected flows here.

Step 2: Update the flows

  1. Open the affected flow in the designer
  2. The trigger now displays a new URL
  3. Copy the new URL and replace the old one wherever it is being used (BPA modules, external systems, Power Apps, or internal integrations)
  4. Save and test the flow to confirm it runs correctly
Key Considerations
  • A warning banner will appear on the flow details page showing the old URL for reference
  • New URLs may exceed 255 characters – check BPA connectors or integrated systems for compatibility
  • If one flow calls another via HTTP, update the calling flow too
  • Child flows using “Run a child flow” do not need updates
Need help?

Full details are available in Microsoft’s official documentation. If you are unsure whether this applies to your BPA environment, please contact your IT team or reach out to the BPA team via the Community portal. We can assist with reviewing your flows and ensuring all BPA integrations remain operational.

×