search

MicrosoftDocs / microsoft-365-community

Microsoft 365 community contributed documentation https://docs.microsoft.com/microsoft-365/community/
MIT License
194 stars 167 forks source link

Explain Flow Licensing Scheme for Citizen Developers #14

Open sympmarc opened 5 years ago

sympmarc commented 5 years ago

Article Suggestion

New licensing options for Flow go into effect on 1 Oct 2019. Many people are confused about how this will affect them as citizen developers or makers. An article which explains the impacts to them (and stays valid over time) would be very useful.

Thanks for your contribution! Sharing is caring.

SandyLT commented 5 years ago

Hi Marc, I'm interested in tackling this...

sympmarc commented 5 years ago

Ping. :)

aaronrendell commented 4 years ago

@sympmarc - Is this still 'active'? I'm happy to look at pulling together a 'fact sheet' type article around the most common licencing scenarios.

I was actually going to suggest some 'scenarios' on power app/flow solutions with different features/back ends, to illustrate what licencing would be needed and for whom. - this would also be quite relevant with the news about Dataflex for Teams?

sympmarc commented 4 years ago

A scenario-based article would be really helpful. I know almost everyone I talk to is confused by this, including me. People coming from the D365 side of things can't understand why it's confusing or why we think it's expensive. @chakkaradeep thinks I'm being dense when he explains it to me. :)

aaronrendell commented 4 years ago

NP. I'll take this on, as it was something I was planning on covering in a personal blog.

It would be worth covering Power Apps in this too, as they go hand in hand.

chakkaradeep commented 4 years ago

I will be working on this in the context of Migrating classic workflows to Power Automate next week (when I am back from vacation). There are things to clarify and validate with product teams and hence this will be something Microsoft will be adding to the official docs.

aaronrendell commented 4 years ago

@chakkaradeep sounds great. Would it make sense to split this into two articles? One being 'Migrating from classic SharePoint Designer Workflows to Power Automate' and a 'Scenario' based article on Power App and Power Automate deployments and the licencing implications on those different scenarios, taking into account seeded licencing and premium licencing?

sympmarc commented 4 years ago

@chakkaradeep - your article above is definitely proving useful to folks. Looking forward to your updates.

I'll leave it to the two of you to decide if an article here would be useful. I think scenarios would help make things more "real".