Flow Studio DevLog: reported for phishing and woes of Cloudflare

This is a quick blog post, but also REALLY IMPORTANT, concerning Flow Studio App (flowstudio.app) - the main, root URL.

What’s happening right now

Right now, if you navigate to the root url flowstudio.app, you’ll get a really scary looking warning page from CloudFlare.

You can prove you are a human, and click Ignore & Proceed. Then you can still use Flow Studio App without any issues. But… most people will hold back and think wait what’s going on.

What is the root cause

flowstudio.app is the root of our website and saas app. There is Javascript code in the Angular web application that says: if you have logged in before, and you return, but your login has expired, then redirect you to re-login (via Microsoft). It happens really fast, so the user must have thought hmm I click flowstudio.app but it immediately redirected me to login with my Microsoft Account. 😱 This must be phishing.

So we got reported, a false report, but still a report. We were reported on 04 September 2025. That’s a whole two weeks ago!

The report is only affects our root page: https://flowstudio.app
It doesn’t affect other pages: https://dev.flowstudio.app or https://powerstudio.app (these are all fine because there’s really nothing wrong with the Angular app).

How to blame CloudFlare without blaming CloudFlare

The company that gives free CDN and DNS routing, and saves me gigabytes of cached data, is also the one that takes away.

Their support, at least on the free or lower-end tiers, are non-existent. I’ve submitted for a review within the week, but so far, I’ve not heard back, and the scary warning remained. Their reputation on reddit around support is awful, so I’m not holding my breath.

Flow Studio’s google ranking has tanked and visitor is now null.
Ouch!

What we are going to do about this

First, we have moved the app to a separate subdomain, previously we have:

https://dev.flowstudio.app (this has always been our dev branch which doesn’t have the warning)
We are now adding https://prod.flowstudio.app which is where the App will live from now on.

Second, we will deploy a static Azure Static Web App for https://flowstudio.app which will link to our various product tiers and offerings. Initially, this will mirror a basic version of the previous Flow Studio home page, but over time we’ll improve the design separately.

Third, for now, CloudFlare still has to manage the various DNS subrecords, but we won’t use CloudFlare to Proxy (and CDN) our https://flowstudio.app home page. Which will allow us to control our landing experience again.

You’ll see some web updates through this weekend. Thank you for your support and please feel free to reach out if you see any unexpected results or issues.

About: The old trigger URL will stop working on November 30, 2025

Starting in August 2025, we’ve begun to see this warning a lot in our Power Automate flows that uses HTTP Request (or Team Webhook) triggers.

“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.”

The old url uses the logic app domain:

https://*.logic.azure.com/workflows/{flow-name}/triggers/manual/paths/invoke

The new URL uses a largely undocumented api.powerplatform.com domain.

https://{environment-name}.environment.api.powerplatform.com/powerautomate/automations/direct/workflows/{flow-name}/triggers/manual/paths/invoke

Why New URL?

The NEW URL looks to be more future proof and ties the invoke URL to the environment and flow name within Power Platform, rather than the underlying logic apps infrastructure.

Microsoft’s documentation is here: Changes to HTTP or Teams Webhook trigger flows

Flow Studio new feature: Flow (Request) Report

To help with updating these URLs, we decide to put in a special View and Report for this in Flow Studio. Here, we are doing 4 things:

• This report shows flows that use the "When an HTTP request is received" trigger. These flows can be triggered externally via HTTP requests, making them suitable for integration scenarios.

• First we do a scan of all the environments and find all your flows that use this trigger. This may take a few minutes depending on the number of environments and flows.

• Then for each flow we will need to check the flow definition to extract the old and new request URL and method.

• We also need to check the flow's run history to see if it has been triggered recently. This will help us identify active flows.

View fullsize

We present this in a quick table for you to browse, but also provide an Export to Excel functionality so you can decide how you want to tackle the list.

Permissions

Because of the API access we need to read definition and trigger callback URL, this is not a scan we can do at the admin level - it has to be the owner of the flows.

You can find this new feature in our dev build:
https://dev.flowstudio.app

Diff Mode in Flow Studio

We are happy to introduce a new feature update in Flow Studio app. “Diff Mode”

• Navigate to Diff on the left hand side.

• Use the top dropdowns to select your environment, flow and (optionally) version. Hit “Load”

• You can use Monaco (VS Code) editor to copy Flow definition differences to the right hand side.

• The left hand side is always read-only.

• Clicking “Save” will save the right hand side flow definition.

This is a feature previously hidden in “Snapshots” and “Diff” flow. But that experience only lets you compare between the flow and its previous versions. The new experience also let you compare a flow between two different environments. So if you have Dev, Test and Prod environments with unmanaged solutions - you may need this to keep your flows in sync.

Do test this out in https://dev.flowstudio.app v1.3.58 for now and give us your feedback. We’ll aim to push this to production build within 1 week.

Thank you for supporting Flow Studio App

Flow Studio Price Update 2025 & Introducing Flow Studio for Teams

Since July 2019, Flow Studio has remained at its previous pricing of $20 per month per person and $200 per year. Over the years, we’ve introduced numerous enhancements, including:

• Flow Snapshots – Easily track and restore previous versions of your flows.

• Export to Zip – Package and share flows efficiently.

• Export runs to Excel

• API Enhancements – Faster, more reliable flow management.

At the same time, Azure costs have steadily increased, impacting our infrastructure expenses. To continue delivering a high-quality experience, we are updating our pricing.

Flow Studio Pro

Plan	Current Price	New Price	Effective Date
Monthly	$20 per month per person	$25 per month per person	End of March 2025
Yearly	$200 per year	$250 per year	End of April 2025

🔹 Existing customers will continue at their current pricing—this update applies only to new sign-ups.

Introducing Flow Studio for Teams

We’re excited to introduce Flow Studio for Teams, designed for business, projects and teams that need better visibility and management of their flows. With this new offering, teams can:

✅ Set up automatic monitoring of critical flows
✅ Receive alerts when flows fail or behave unexpectedly
✅ Store flow run details beyond 30 days
✅ We host, or BYO Storage

Flow Studio for Teams Pricing

Plan	Price	Effective Date
Monthly	$100 per month inc 3 seats	Now
Yearly	$1000 per year inc 3 seats	Now

We appreciate your support and look forward to continuing to improve Flow Studio. If you have any questions or feedback, feel free to reach out!

Flow Studio App v1.2 Updates

February and March was really busy for us here at Flow Studio.

Catherine is now wearing multiple hats and helping on Flow Studio in so many needed areas. You’ll see her a lot from here on.

Learn Flow Studio

First, we launched Learn Flow Studio - this is where we are publishing content, blog and newsletters regarding Flow Studio App. All of our previous documentation is moving here, and we’re not done yet! There are more articles to write.

Flow Studio - what’s changed in v1.2

• Flow Studio App needed a backend cache library update - we took this opportunity to update our IndexedDB library from LocalForage to DexieDB. LocalForage doesn’t seem to be updated for some time, so the change looks necessary. We started this work on December 26, 2023.
  With this change in mind, we reworked the cache layer, giving us much better performance when we have lots of flows and flow runs. This is was quite a big change, the changes stayed in our dev branch for several months.

• We fixed up a lot of labels, help text and links to learn flow studio.

• We fixed Flow Studio migrate - removed operationMetadataId from being detected by the migrate wizard. There’s just too many guids it picked up.

• We combined Flows and Flows (Solutions), so now everyone can see their solution flows in the free tier.

• Made improvements to Full Text Search, when searching flow actions with “Compose This” we will also check for “Compose_This”. We also added RegExp search. Read more about this on learn.

Flow Studio App - roadmap / coming soon

• At a high level, we are looking at moving more scanning to the background, giving users better control over the periodic scanning of the Power Platform, and rely on the IndexedDB cache to provide instant rendering of the Flow Studio App UI.

• We want to start working on improving our user account management, including managing multiple license assignments and delegation.

• We also are looking forward to implementing the Favourites feature.

Check out Flow Studio App