Like-for-like comparison
Make vs Power Automate: SaaS workflow or Microsoft estate?
Make is a visual cross-SaaS orchestrator; Power Automate extends into Microsoft governance and desktop RPA. Choose from the environment, not the logo colour.
Decide whether the hard requirement is broad SaaS movement, Microsoft control or desktop automation.
THE SHORT ANSWER
Prefer Make for visual workflows spanning varied SaaS products. Prefer Power Automate when Microsoft identities, data, policies or desktop processes drive the project.
DECISION BOUNDARIES
What actually separates the options
Estate
List the systems that actually hold the work.
RPA
Separate API-capable steps from desktop-only steps.
Governance
Check identities, gateways, DLP and service accounts.
Make suits cross-tool operations; Power Automate suits Microsoft-centred organisations with administrative support.
Avoid making either a standard before the organisation has defined ownership and exception handling.
COST AND CONSTRAINTS
Price is one operating condition
Compare Make usage with the precise Power Automate licence path. UK list prices are a starting point; VAT, capacity and existing entitlements alter the real number.
EVIDENCE
What to test before committing
Pilot one workflow that crosses the hardest boundary: SaaS-to-SaaS, cloud-to-desktop or tenant-to-external service.
SIMPLER ALTERNATIVE
Before adding another account
Use a Microsoft-native feature or a direct integration if orchestration adds no useful control.
A familiar tenant can reduce friction. It can also hide three admin portals.