Power Platform has been part of Microsoft 365 for several years now, but many end users are unaware of its existence with SharePoint consulting. In fact, many IT professionals don’t know what Power Platform is either.
For them, Power Platform has something to do with Dynamics 365, and so they ignore it.
Personally, I was aware of the existence of Power Apps, Power Automate (formerly Flow), Power BI and the new kid on the block, Power Virtual Agents. I knew them, but I didn’t trust them.
To tell the truth, when I trained companies and collaborators at all levels of the hierarchy, I explained to them that the components of Power Platform were able to do incredible things, but that it required a certain level of “mastery of the ‘computer tool’, maturity, knowledge, or whatever buzzword you want to use.
While I live and breathe Microsoft 365, for a very long time, I haven’t touched any of these tools. I barely touched Power BI with my fingertips, and still, it was only as a user. Everything seemed inaccessible to me.
When I heard other MVPs talking about the solutions they had created for conferencing from Forms, plus a Power Automate workflow, plus a SharePoint list, plus email, plus more…all of this reminded me seemed too complex for me to use, so for an end user…
Honestly, it’s still kind of the case, but the alignment between Microsoft Teams and Power Platform reduces complexity, makes features easier to use and more accessible to average users, and ultimately gives them more chances to be adopted and bring benefits to businesses.
Let’s start with the Microsoft Teams Approvals app. Some of my co-workers, customers, and general users have been really happy that the Microsoft Teams Approvals app is available to all users. This would finally allow them to start creating message-based workflows in Microsoft Teams. A new era was born!
In fact, Power Automate was originally launched as a connector for Microsoft Teams in mid-2017 (shortly after the launch of Microsoft Teams).
Just 18 months later, the first triggers were launched . Flows could thus be triggered based on an event that occurred on a team’s channel.
In fact, it was in early 2018 that the Flow app (now Power Automate) was introduced to Microsoft Teams , allowing you to make approvals without leaving the app.
I’m not saying this to spoil the party, but more to point out that the concept of creating and working with approvals was not a “mainstream” concept until the Approvals app was offered in late preview. 2020. I rarely hear terms like ‘citizen developer’, ‘business analyst’, ‘workflow’ and the like in discussions with my clients (and their end users). The Approvals app took a powerful feature in Power Automate, simplified it, and packed it into an easy-to-use app.
In a way, the Approvals app can be said to be comparable to the “consumerization of IT” trend of a few years ago.
Once users get a taste of how Approvals work, they’re ready to enter the world of automation.
While they’re sometimes reluctant to install the Power Automate app in Microsoft Teams, they quickly discover that its skills aren’t limited to automating approvals.
What Microsoft has done particularly well with the Power Automate app in Microsoft Teams is its ability to surface applicable templates when creating new flows. This dramatically shortens the learning curve a user has to go through to create other types of workflows.
When the user creates workflows, he learns about the available triggers and actions, which leads him to realize that approvals and other workflows can be done outside of Microsoft Teams. He realizes that workflows can be triggered by incoming emails or by downloading certain files. And here we go.
The user is then ready to create amazing workflows and automations. Does that make it a “citizen developer”? Not necessarily. It is not necessary to put a label on it. It is simply a user who has taken a new step in using Microsoft 365.
As a recently converted Power Automate user (in the sense that I was just using it six months ago, and now I’m addicted), I understand those who feel overwhelmed when it comes to acts to initialize variables, formulate trigger conditions, send HTTP POST commands or use other advanced functions. As I’m beginning to master these functions in the specific context of my activity, I think that an average user can completely ignore these functions for a while since he can do a lot of things without them. It’s when you start working with them that the term ‘citizen developer’ may become more appropriate.