We need to be thinking Power BI when we think Power Platform Adoption Framework

I’ve just published a post on the Power BI User Group blog, Using Power Platform Adoption Framework to help large organizations adopt, manage, and govern Power BI (and more) at scale. In it I wrote that, “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.“

Further, “We intend this to be a framework for adoption of the whole platform… Think about Power BI as you use the framework to roadmap, prioritize candidate workloads for migration, and then actually build. The fusion of great technology that is Power Platform urges us to get beyond thinking about migrating workloads in a 1:1 way.“

We need to use Power Platform Adoption Framework as an opportunity to embrace the whole platform, which means thinking about all the component parts — Power BI, Flow, PowerApps (and Common Data Service!) — when we think about enterprise adoption.

I’d love your thoughts and feedback after you read the complete post on the Power BI User Group blog.