The Extension Id for Power Automate in Google Chrome is: gjgfobnenmnljakmhboildkafdkicala The Extension Id for Power Automate in Microsoft Edge is: njjljiblognghfjfpcdpdbpbfcmhgafg I came across a forum post in the Power Automate forums at: which suggested to remove it from the registry. Even after I had uninstalled Power Automate, the browser extension was still on my machine. It was on my machine from the desktop installation of Power Automate. I did not go to the Chrome Web Store or Edge add-ons to install it – IT WAS ALREADY ON MY MACHINE. New Extension added in Google Chrome upon new profile creation Microsoft Power Automate Extension asking to be enabled in Google Chrome Microsoft released a desktop app for Power Automate and I wanted to check it out, so I installed it.Īfter that, every time I created a new profile in Google Chrome and Microsoft Edge, I would be prompted to Enable the extension in the browser. Regardless, I hadn’t done anything else with Power Automate. Way better than the output I was getting from an Azure Logic App. The Power Automate interface on the web provided verbose output as to what was happening. After all was well, I moved the automation routine to an Azure Logic App.Debugged the automation routine in Power Automate on the web.I created the automated routine in Power Automate on the web.But creating the routine directly in an Azure Logic app started to be time consuming as I wasn’t getting the verbose debugging output to let me know what the error was. And the automation was to be run as an Azure Logic app. One of my previous projects were to setup an automation for Microsoft Dynamics 365 (cloud). I had worked a little bit with Power Automate, but not much.

I wanted to see what my customers would be using and how they would be interacting with it. One day, I decided to check out Microsoft Power Automate to see what it’s capabilities were.

Power automate web automation