MC1411068 High
Power Automate – Build better forms with integrated Power Apps
Summary AI-generated
Makers can launch interactive canvas Power Apps as user interfaces from Power Automate desktop flows starting July 31, 2026, enabling richer form experiences and improved reliability.
Written by Azure OpenAI (gpt-4.1) from the text of the post below. It can be incomplete or wrong; the original post is authoritative.
Similar posts
Search for more like this- MC1428573 Power Automate - Automate PowerPoint presentations in desktop flows
- MC1429626 Power Automate - Visualize desktop flows with flow chart view
- MC1434599 Power Apps - Use streamlined header and navigation for better viewing
- MC1329308 Power Apps - Use streamlined header and navigation for better viewing
- MC1411132 Power Automate – UI automation repair agent
- MC1287659 Power Apps - Enhanced experience for form filling with AI
Original post from Microsoft
We are announcing the ability to launch interactive Power Apps directly from desktop flows within Power Automate. This feature will reach general availability on July 31, 2026.
How does this affect me?
With integrated Power Apps, makers can now use canvas apps to create modern, interactive form experiences for attended desktop flows.
Key functionality of this feature includes:
This message is for awareness, and no action is required.
How does this affect me?
With integrated Power Apps, makers can now use canvas apps to create modern, interactive form experiences for attended desktop flows.
Key functionality of this feature includes:
- Use canvas apps as the user interface for desktop flows: When the action runs, the selected canvas app opens on the user's machine, providing a fully customizable UI built using the Power Apps designer.
- Pass inputs into the app: Desktop flows can send context, state, and values to prefill the app and guide user interaction.
- Capture outputs back into the flow: Data entered by the user in the app is returned to the desktop flow and can be used to drive subsequent automation steps.
- Trigger subflows from app events: App actions such as button clicks can invoke specific subflows, enabling event-driven patterns instead of strictly sequential execution.
- Works with all desktop flows: This capability is compatible with both Power Fx-enabled and non-Power Fx desktop flows.
- Reduce reliance on UI automation for form interaction: Instead of automating application UI to collect user input, makers can use structured data exchange between the flow and the app. This approach avoids selectors and screen scraping for form scenarios, improving reliability and resilience to UI changes.
This message is for awareness, and no action is required.