What has changed?
Microsoft’s own documentation now distinguishes two cloud flow “environment architectures”: an older LogicApps-based one, and a newer SelfHostMultiTenant runtime. That is the cleanest technical signal that cloud flows are no longer just “Power Automate on top of Logic Apps”.
Why this matters to builders
If cloud flows stop inheriting platform changes from Logic Apps, you should expect differences to accumulate over time: connector behavior, retry semantics, triggers/webhooks, performance characteristics, and eventually developer tooling/ALM patterns.
Evidence checklist
1) Runtime architecture split Verified
Microsoft documents that environments are being upgraded to a new SelfHost Multitenant architecture, with a debug flag environmentFlowHostingType showing either SelfHostMultiTenant or LogicApps.
- New features like express mode require SelfHost Multitenant.
- The old architecture is explicitly labeled
LogicApps.
Source: Power Automate environments move to new architecture
2) Endpoint + trigger URL migration Verified
Microsoft warns that flows with HTTP/Teams webhook triggers using logic.azure.com will move to a new URL, and the old URLs stop working on Nov 30, 2025.
- Affects only flows in the Logic Apps environment architecture.
- Explicitly tied to an “infrastructure upgrade” to “improve execution speed and provide new features”.
- Microsoft Q&A discussion (accepted answer) describes a migration to the
api.powerplatform.comdomain.
3) Release-cadence divergence Observed
The “Service Updates for Power Automate” page shows its latest listed update as 2508.2 (Aug 2025), and is last updated 2025‑09‑02.
- That does not prove “no changes shipped”, but it does show “no public service-update transparency” since Aug 2025.
- Meanwhile, Azure Logic Apps Standard continues its own versioned releases (see sources below).
Timeline
environmentFlowHostingType flag.logic.azure.com trigger URLs stop working for affected HTTP/Teams webhook flows.Community pulse (selected quotes)
“Maybe all resources have been moved onto AI / Agents dev.”
“Yes, Microsoft is prioritizing Agent Flows in the UI. But you can still use Power Automate flows instead if you want.”
“It is January and we are still being spammed by these emails.”
Interpretation and speculation
What's happening Evidence
- Cloud flows are being “pulled inward” under Power Platform (SelfHost runtime, non-
logic.azure.comURLs, Power Platform admin tooling). - Logic Apps Standard stays Azure-native (repo-based releases, Azure-first positioning, agent/workflow improvements landing there independently).
- Parity is no longer a safe assumption: even if some components remain shared, divergent constraints and release vehicles will create drift.
Where this might be heading Speculation
- Power Automate maker UX becomes “agent-first” (Workflows/Flow Builder, prompt-to-flow, guardrails, governance).
- Cloud flows become a backend capability powering Copilot Studio “agent flows” and other products, with less emphasis on manual authoring.
- Logic Apps keeps the pro-dev lane: IaC/GitOps, Azure-native integration patterns, advanced workflow hosting models.
Read more perspectives(.plus)
What next for Power Automate?
Cloud flows as a “legacy feature” in the agentic AI era, and why the lack of a roadmap is itself a data point.
Open articleCan Workflows replace Power Automate?
A test drive of Microsoft’s Flow Builder/Workflows in Microsoft 365 Copilot (Frontier), with builder errors, governance gaps, logic pitfalls, and licensing messiness.
Open article