Power Automate Push Notifications Have Had No Target Since August 31

As of August 31, 2026, the Power Automate app for iOS and Android is deprecated. Microsoft has removed it from the App Store and from Google Play and provides neither updates nor support. For most flows this changes nothing. They run server-side and never needed the app. One action is hit anyway, and it is one that was built into many environments at some point: "Send me a mobile notification".

What exactly goes away

The step "Send me a mobile notification" sends a push message to the Power Automate app on the phone. According to Microsoft, the app no longer receives these messages. Without the app there is no target, and the notification reaches nobody. The flow itself is not changed or deactivated. It runs as before.

That is exactly what makes the case unpleasant. A flow that keeps running does not stand out in operations. Unless you search for it deliberately, you notice the gap only when someone asks why the message about a failed import or an important order never arrived. Such steps are typical in flows that were built years ago "just quickly for me" and later kept running in the team.

The widget on the home screen, which starts a flow at the press of a button, disappears with the app as well. Approvals are not affected. They keep running through Teams and through the Power Automate portal, also in the browser on the phone.

Replacement

Microsoft names two ways to send the notification. One is a message through the Teams connector ("Post message in a chat or channel"). The other is an email through the Outlook connector ("Send an email"). Both reach people without the old app. Both can replace the old step without touching the surrounding logic.

Which one fits better depends on the recipient. A Teams message in a channel is visible to everyone who handles the case, and it is not lost when someone is on vacation. An email suits individuals and recipients outside Teams better. During the switch, take a moment to ask whether the notification is still needed at all. Some of these steps come from a flow's test phase and were never removed again.

How to find affected flows

Internally, the connector is called "flowpush". If a flow is part of a solution, this name appears in the flow JSON of the solution export as soon as the step "Send me a mobile notification" is used. A text search for "flowpush" across the unpacked export finds the places reliably. Flows outside a solution do not appear in the export and must be checked in the portal.

For context, since I build an analysis tool myself with D365 Audit: it detects the use of "flowpush" in flows automatically. The report points out the shutdown, with the name of the flow and the replacement. The only basis is the solution export. No access to the environment is needed.

What I would do now

Search all solutions once for "flowpush". Switch the hits to Teams or email. While you are at it, check who should actually read the message. This is often manageable work. It only gets more expensive if the missing message is first noticed in operations.

Source: Microsoft Learn, "Important changes (deprecations) coming in Power Platform".