Power Apps: Enable push notifications in custom branded apps
Empower your frontline staff to stay up to date with timely push notifications on your custom apps, ensuring critical information is always delivered. Push notifications are expanding beyond the Power Apps Mobile player to support custom‑branded, white‑label apps (wrapped apps). This feature gives makers a self‑service, simplified way to configure push notifications in wrapped apps. Here is how the feature can be used: Enable notification toggles in the wrap wizard for both Android and iOS platforms. Create a new project in your Firebase console (Google Firebase). Register your apps in Firebase by creating both an Android app and an iOS app under the messaging section. Add platform details by selecting the platform and entering your app’s bundle ID (ensure the package name matches your app’s bundle ID exactly). Download configuration files – Firebase provides a google-services.json file for Android and a google-services.plist file for iOS. Upload configuration files to the notification step in the wrap wizard. Complete the wrap process – the remaining steps will work automatically to generate your APK or IPA file. Set up Power Automate flow to send notifications by creating an HTTP request action that calls the Firebase API. Configure trigger conditions in Power Automate (for example, when a record is created or updated in Dataverse). Extract recipient email address from the triggered record in your Power Automate flow. Include Firebase API credentials by storing the API key as a secret value in Power Automate. Define notification content including title, body, and target topic in your HTTP request. Test notifications using Firebase’s notification composer in the console before deploying to production. Target specific users by sending notifications to their email-based topic or target all app users by selecting the appropriate user segment option. Learn More
The post Power Apps: Enable push notifications in custom branded apps appeared first on M365 Admin.
Published on:
Learn moreRelated posts
Power Apps – Tenant-Level Microsoft 365 Copilot Settings to Enable Dataverse Data Access Announcement
We are announcing that a new tenant‑level Copilot setting to manage Dataverse data availability in Microsoft 365 Copilot will be available in ...
Power Apps – Microsoft 365 Copilot will be available in model-driven apps
We are announcing the ability to use Microsoft 365 Copilot in model-drive apps in Power Apps. This feature will reach general availability on ...
Connecting Power Apps Code App with Microsoft Copilot Studio Agent
As we previously learned how to configure and set up a Code App component in our earlier blog, we will now extend that implementation further....
Editing Canvas Power Apps with GitHub Copilot
IT work is rapidly becoming AI-assisted or even completely (AI) agent-driven. The same development can be seen in the Power Platform. In previ...
Power Apps – Build generative pages using external code generations tools
We are announcing the ability to build and edit generative pages for your model-driven apps directly from code generation tools. This feature ...
Power Platform Fundamentals #4: Understanding Power Fx in Power Apps: Core Functions, Formula Patterns, and Real-Time Business Scenarios: Quick Read Series
1. Business Scenario In modern enterprise applications, business logic is deeply embedded across user interfaces and data processes. This incl...
Decode & Fix : Shared App host initialization has timed out in Microsoft Power Apps
Issue :While working with apps in the Microsoft Power Platform, we encountered a critical issue where the application failed to load pro...
How to patch images from Power Apps to Dataverse
Patching images is a very common use case for Power Apps. Learn how to patch images from an app to Dataverse! The post How to patch images fro...
How to patch images from Power Apps to D365 F&SCM
Patching images is a very common use case for Power Apps. Learn how to patch images from an app to D365 Finance & Supply Chain Management...