Power Automate mobile app retirement: what to check

Check which mobile workflows need attention after the Power Automate app retirement, with replacement options and a practical migration checklist for teams.

Harllens George | 2026-09-14

Historical Microsoft Power Automate mobile flow editor with recurrence, weather and message actions.
The retired Microsoft Power Automate mobile editor, shown in Microsoft's historical documentation. This is not the replacement experience. Image source. Microsoft and contributors. Original image, displayed proportionally. CC BY 4.0.

Microsoft ended support for the standalone Power Automate iOS/Android app on August 31, 2026, announcing store removal and no further updates. Existing cloud flows are unaffected. Mobile app notice.

Sources checked September 12, 2026. A source-based checklist, not a customer-tenant migration test.

Match the replacement to the action

App push notifications and the run-flow widget are affected; the widget has no direct equivalent. Evaluate these alternatives from Microsoft's deprecation guidance:

Mobile action Replacement to evaluate
Respond to an approval Teams Approvals
View or manage flows Portal in a mobile browser
Run an instant flow Portal or Power Apps mobile
Receive a notification Teams message or email added by the owner

An administrator may have disabled Teams Approvals. Check access before writing instructions. Teams guidance. For Power Apps, account for sharing, the user's device and shortcuts. Mobile guide.

Three migration checks

  1. Inventory the actual journey. Ask users how they start work and notice problems. Record workflow owner, mobile action, notification recipient and the decision each alert supports. Include undocumented shortcuts.
  2. Test a safe replacement. Use synthetic inputs and an agreed destination. Test as the intended user, not only the maker. Verify final run status, delivered message or approval response, stored business output and duplicate messages.
  3. Hand over the new entry point. Record the result, user instructions, support contact and recovery step. Keep a rollback record before changing production. Give someone ownership of the replacement alert; avoid an unattended noisy channel.

Mistakes to avoid

A successful run does not prove that a person received the information they need. Test that handoff, including whether the replacement destination opens on their device.

Check whether the portal is sufficient before building an app just to replace a button. The checklist provides acceptance criteria, not evidence that your environment is ready.

Related guide

File Exporter PCF for Power Apps is a separate Canvas integration example, not a replacement for the retired app.