Microsoft Azure is a cloud computing platform and infrastructure for building, deploying, and managing applications and services through a global network of Microsoft-managed datacenters.
$29
per month
Microsoft Power Automate
Score 8.3 out of 10
N/A
Microsoft Power Automate is an advanced automation platform offering a range of features, including AI-powered automation, robotic process automation (RPA), business process automation (BPA), digital process automation (DPA), and process/task mining. The platform aims to empower organizations to securely automate their operations at scale by leveraging low-code and AI technologies.
$15
per month per user
Pricing
Microsoft Azure
Microsoft Power Automate
Editions & Modules
Developer
$29
per month
Standard
$100
per month
Professional Direct
$1000
per month
Basic
Free
per month
Power Automate Premium
$15
per month per user
Power Automate Process
$150
per month per bot
Hosted RPA add-on
$215
per month per bot
Process Mining add-on
$5,000
per month per tenant
Offerings
Pricing Offerings
Microsoft Azure
Microsoft Power Automate
Free Trial
Yes
Yes
Free/Freemium Version
Yes
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
The free tier lets users have access to a variety of services free for 12 months with limited usage after making an Azure account.
Because Microsoft Azure has more integrations and possibilities. Also most of the biggest companies are using it, so it gives the security and the back up to trust and work with confidence.
Evaluated both AWS and GCP for a similar set of use cases to realize that AWS required additional third-party add ons to be purchased for load balancing vs. Azure's out-of-the-box capabilities offered for free. GCP on the surface was lower cost but the cost of running …
AWS and [Microsoft] Azure are in a class by themselves, no matter how you look at them or what sub-area or service you focus on. No other cloud provide can match the breadth and ability of these two. Nobody else has the market share either (for a reason). That being said, …
Azure is particularly well suited for enterprise environments with existing Microsoft investments, those that require robust compliance features, and organizations that need hybrid cloud capabilities that bridge on-premises and cloud infrastructure. In my opinion, Azure is less appropriate for cost-sensitive startups or small businesses without dedicated cloud expertise and scenarios requiring edge computing use cases with limited connectivity. Azure offers comprehensive solutions for most business needs but can feel like there is a higher learning curve than other cloud-based providers, depending on the product and use case.
Very useful RPA tools for automating processes with minimal coding and drag-and-drop functionality, with a wide variety of triggers, including scheduled time-based triggers and activity-based triggers, such as modifying a file/list in SharePoint to run a Power Automate flow. Very easy-to-use UI with native integration with every Microsoft product, and a very low automation failure rate for deployed workflows.
Microsoft Azure is highly scalable and flexible. You can quickly scale up or down additional resources and computing power.
You have no longer upfront investments for hardware. You only pay for the use of your computing power, storage space, or services.
The uptime that can be achieved and guaranteed is very important for our company. This includes the rapid maintenance for security updates that are mostly carried out by Microsoft.
The wide range of capabilities of services that are possible in Microsoft Azure. You can practically put or create anything in Microsoft Azure.
The cost of resources is difficult to determine, technical documentation is frequently out of date, and documentation and mapping capabilities are lacking.
The documentation needs to be improved, and some advanced configuration options require research and experimentation.
Microsoft's licensing scheme is too complex for the average user, and Azure SQL syntax is too different from traditional SQL.
Moving to Azure was and still is an organizational strategy and not simply changing vendors. Our product roadmap revolved around Azure as we are in the business of humanitarian relief and Azure and Microsoft play an important part in quickly and efficiently serving all of the world. Migration and investment in Azure should be considered as an overall strategy of an organization and communicated companywide.
The tool is very useful when used with its various native connectors, taking great advantage of the integration between the components and systems of the Office365 universe. However, its cost is still high, and automation using more advanced components containing AI resources becomes unfeasible for some companies. Due to the financial crisis that many companies are currently experiencing, investment in automation systems or tools is taking a back seat.
As Microsoft Azure is [doing a] really good with PaaS. The need of a market is to have [a] combo of PaaS and IaaS. While AWS is making [an] exceptionally well blend of both of them, Azure needs to work more on DevOps and Automation stuff. Apart from that, I would recommend Azure as a great platform for cloud services as scale.
Power Automate features a clean and intuitive user interface that allows users to create, manage, and monitor workflows easily. The UI is designed to be accessible to both technical and non-technical users, with drag-and-drop functionality for building workflows. Power Automate supports integration with a wide range of Microsoft and third-party applications. This flexibility in integration allows users to automate workflows across various systems, enhancing overall productivity and efficiency.
We were running Windows Server and Active Directory, so [Microsoft] Azure was a seamless transition. We ran into a few, if any support issues, however, the availability of Microsoft Azure's support team was more than willing and able to guide us through the process. They even proposed solutions to issues we had not even thought of!
both Community support and Microsoft official support typically respond to (and resolve) reported issues in a VERY expedient manner, usually going above and beyond for education and bugfixing. I have been thoroughly impressed with the level of support I had been provided in the past.
after reviewing the main features of Power Automate, the Microsoft trainer focused on some of our real life use cases implementation, from simple to more advanced.
although it was productive, it is more difficult to stay focused and in a 7 hours a day online training (including screen share issues and the fact that the trainer just can't precisely show the exact location of your mistake)
As I have mentioned before the issue with my Oracle Mismatch Version issues that have put a delay on moving one of my platforms will justify my 7 rating.
Overall, our experience implementing Microsoft Power Automate has been positive, with a relatively low barrier to entry and a fast time-to-value—especially because it integrates natively with Microsoft 365, which we were already using extensively. With Respect to migration, I had a very good experience where existing workflows were reviewed and simplified. Unnecessary steps were removed. Business rules were reimplemented using Power Automate logic. We migrated Approval workflows, email-based notifications, SharePoint-centric processes, and simple integrations.
As I continue to evaluate the "big three" cloud providers for our clients, I make the following distinctions, though this gap continues to close. AWS is more granular, and inherently powerful in the configuration options compared to [Microsoft] Azure. It is a "developer" platform for cloud. However, Azure PowerShell is helping close this gap. Google Cloud is the leading containerization platform, largely thanks to it building kubernetes from the ground up. Azure containerization is getting better at having the same storage/deployment options.
Microsoft Power Automate is worlds ahead of Zapier in so many ways. The looping, DOM access, and flow controls are much better. I feel that accessing different data within previous connectors used in a flow is much easier in Microsoft Power Automate as well. The custom connector creation process is a lot more pleasant in Microsoft Power Automate. The DateTime data type is handles MUCH better in Microsoft Power Automate, which is reason enough to use it.
Microsoft's professional services provide hands-on support throughout the implementation lifecycle of Power Automate.This includes initial setup, configuration, integration with existing systems, testing, and deployment. They ensure that workflows are correctly designed, optimized for performance, and aligned with security best practices.
For about 2 years we didn't have to do anything with our production VMs, the system ran without a hitch, which meant our engineers could focus on features rather than infrastructure.
DNS management was very easy in Azure, which made it easy to upgrade our cluster with zero downtime.
Azure Web UI was easy to work with and navigate, which meant our senior engineers and DevOps team could work with Azure without formal training.
You can automate a lot of process very easy like automatic mails for status updates and such. This will save a lot of time and is more accurate, faster and up-to-date than a user can be.
Task approval is centralized and automatic reminders save us a lot of time.
The ROI is good if you have a lot of use cases and things to automate
