355
Hi!
Can you please explain to me the difference between a Dynamics 365 workflow and a Microsoft flow with some examples and links to the documentation?
Is "Dynamics 365 workflow" meant to be/synonym of Custom Workflow Activity written within Visual Studio?
And is a "Microsoft flow" meant to be/synonym of any flow created within Power Automate?
The only thing that Classic Workflows can do that Power Automate can't is the "Real Time". Any other feature of Classic Workflow can be replicated in Power Automate in some way.
Thank you all for the answers.
@Andrew, as far as I understood from the article that you provided, I should use Microsoft flows in most situations and whenever possible, except when:
1) I already have thousands of them on my CRM system (which could end up in a lack of performance)
2) I need particular features which are not available in Power Automate.
Only when 1) and 2) are true I should opt for classic / Dynamics 365 workflows, is it correct?
Hi,
Flow can connect to more than 200+ connector OOB to interact with external system however workflow is restricted to dataverse.
Please mark my answer verified if i were helpful
Its just the manipulation of new wording and Terminology, Your understanding is correct, D365 workflow means old workflows that we used to create from UI and enhance further using Code activity and Microsoft Flow is the flow that we create inside Power Automate.
Hello,
Generally speaking Classic Workflows and Power Automate are 2 tools that can be used to automate something in Dataverse.
Dynamics 365 Workflows can be created using UI without opening the VS but can be extended using "Custom Workflow Activities".
The "Power Automate" used to be called "Flow" and now flow is an instance of automation created within "Power Automate".
You can check this for a reference - dynamicconsultantsgroup.com/.../
#1
Adis
136
Super User 2025 Season 1
#2
Sohail Ahmed
81
#3
Jonas "Jones" Melgaard
77
Super User 2025 Season 1
Share
Report
All responses (
Answers (
