Hi All,
A lot of the questions I see here come down to the same decision: which way should we build this? A native workflow, DataMesh, Bridge, Power Automate, the API?
I put the options on one page to make that comparison easier. For each one it covers what it does, where it runs, how far it extends, what you get out of the box and the rough build effort.
They aren't the same kind of thing. Some are native features, some are AI capabilities, some are premium data or integration options, and some are external platforms or developer interfaces. The guide groups them as Automate, AI, Data, Integrate and Develop, and those are different jobs, not maturity levels.
The principle I keep coming back to: start with the simplest capability that does the job, and add complexity only when you can name the wall you hit. Someone has to maintain it after go-live, so it helps to pick the option the team can actually fix.
A few notes:
- The availability lines are kept general on purpose. Plans and packaging change, so please confirm your own entitlements.
- It's a starting point, not a rulebook. There are plenty of edge cases where the "heavier" option is right from day one.
I'd really value corrections or additions from this group. If something is wrong or could be put better, tell me and I'll update the guide.
Thanks
Ankesh
