Explaining Power Platform: How do the pieces fit together?
We can't truly embrace what we don't understand. Having a common understanding is critical to determine common best practices for adoption and beyond. The Microsoft Power Platform is a vastly capable technology, but many still struggle to put all of its pieces together in their mind. We'll take a moment to change that here.
Embracing the whole platform is a best practice for adopting and developing Power Platform.
I am very often asked to explain Power Platform and how its component technologies fit together when I present to customers, conference attendees, and colleagues. So my goal with this post is two-fold:
Provide a primer to what Power Platform is and how its pieces fit together so that newcomers can begin to understand this thing
Encourage experienced practitioners to embrace the whole platform as part our shared, community commitment to Best Practices adopting and developing Power Platform
To drive home the second item there, I’ll share below an idea I proposed when writing in a Power BI specific context several months ago:
We get the most value from Power Platform when we truly embrace it as a platform. In other words, while the component parts — Power BI, PowerApps, Flow, Common Data Service, and even Dynamics — are incredible tools in their own right, the more we knit them together, the more valuable they become.
As always, I’m eager for your suggestions, input, and contributions.
