Announcements
Hi,
Just wanting to confirm my understanding of the licensing changes outlined in: https://techcommunity.microsoft.com/t5/Office-Retirement-Blog/UPDATED-Updates-to-Microsoft-Flow-and-PowerApps-for-Office-365/ba-p/289589
Given that the HTTP connector will be moved to become a Premium connector from February 2019, do I correctly assume that nesting Flows using the approach outlined here (https://flow.microsoft.com/en-us/blog/build-nested-flows/) will now require premium licenses?
Thanks,
David
Hi @aussiejedi,
I couldn't sure if the "HTTP custom actions integrated into Flow outside SharePoint and OneDrive" could be understand to "HTTP connector will be moved to become a Premium connector".
So you couldn't assume that nesting Flows using http will require premium licenses.
Best regards,
Alice
@v-yuazh-msft as far as I now it will require premium. I agree that the SharePoint team statement is not clear, but using the HTTP action will require Premium.
Just got caught up in this myself, tried to add a new HTTP to call a workflow & couldn't do it without upgrading. HTTP now requires premium, legacy flows (built before change) will get extended free until 2020 and then you will be required to have a license for all HTTP connections.
BUT- Microsoft has an idea marked as "Planned" to be able to kick off other workflows without using HTTP. Doesn't say whether that would be on the free tier, but it's possible that in the near future we'll be able to call nested flows without the Premium connector.
https://powerusers.microsoft.com/t5/Flow-Ideas/Flows-trigger-other-flows/idi-p/29002
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Congratulations to our 2026 Super Users!
Congratulations to our 2025 community superstars!
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Haque 58
David_MA 53 Super User 2026 Season 1
Expiscornovus 36 Most Valuable Professional
