Consultant KB for Microsoft Power Apps: canvas apps, model-driven apps, Power Fx, data and connections, controls and UI, code and extensibility, mobile and offline, ALM and solutions, governance and security, licensing and performance, plus cross-cutting decision guides. Implementation notes, configuration decisions and the gotchas that bite on real projects. Populated by the daily author agent from the Power Apps release plans, docs repo and product blog, plus the author's own consultant notes.
Features Microsoft has announced are going away for Power Apps, grouped by the area they affect. The mirror of the roadmap: what to plan a migration off, not what to adopt. 0 still to take effect · 11 already retired.
From 1 May 2026, every Power Apps mobile deep link must carry the environment ID. Older deep links without it stop working.
Move to Regenerate deep links to include the environment ID parameter.
Microsoft deprecation notice ↗You can no longer start a new canvas app from an image or a Figma file. Apps already created that way are unaffected; it's the entry point that's gone.
Move to Build the screens directly, or use the standard app-from-data start.
Microsoft deprecation notice ↗Cards for Power Apps stopped working on 29 August 2025: existing cards shared in Teams no longer run, and no new ones can be created. Teams-embedded canvas apps or adaptive cards posted from a flow are the way out.
Move to Canvas apps in Teams, or adaptive cards from Power Automate
Microsoft deprecation notice ↗The Ask a virtual agent help bot in the Power Apps maker portal was deprecated on 11 March 2025 and is no longer supported. Makers get authoring help from Copilot in Power Apps instead, with the standard Help pane for everything else.
Move to Copilot in Power Apps, plus the Help (?) pane in the maker portal
Microsoft deprecation notice ↗The option to map a component's input fields via the dropdown on the Advanced tab is gone. Hits anyone who built reusable components the old way — the mapping now has to be done through the component's own input properties.
Move to Map input fields on the component itself rather than on the instance's Advanced tab.
Microsoft deprecation notice ↗From April 2026 makers can no longer switch model-driven apps back to the classic look — everything uses the modern look by default.
Move to Adopt the modern look.
Microsoft deprecation notice ↗The preview Copilot chat in model-driven apps is going in environments that aren't enabled for Dynamics 365 apps. It was preview, so nobody should be depending on it — but people do.
Move to Enable the environment for Dynamics 365 apps, or build an agent in Copilot Studio.
Microsoft deprecation notice ↗The example-based Power Fx formula generator was retired on 19 February 2025. Natural-language-to-Power-Fx replaces it, and it is a different authoring habit rather than a drop-in swap.
Move to Transform natural language to Power Fx formulas
Microsoft deprecation notice ↗Both the Editable Grid and the Power Apps Read-Only Grid controls in model-driven apps are deprecated from March 2026. They keep working for now, but there's no support once removal lands.
Move to Move to the modern grid controls.
Microsoft deprecation notice ↗The classic rich text editor control is gone — environments were auto-upgraded to the modern editor from 18 April 2025. Anything depending on the old toolbar or its markup output needs retesting.
Move to Modern rich text editor
Microsoft deprecation notice ↗The hierarchy control used to render and query hierarchically related rows in model-driven apps was deprecated in October 2024 and removed a year later. Anything built on that parent/child visualisation needs rebuilding.
Move to A custom page, a PCF control, or a view filtered on the hierarchy relationship.
Microsoft deprecation notice ↗Microsoft has stopped maintaining Test Engine's docs and GitHub repo, and it will be removed. Worth knowing before you build an automated test suite around it.
Move to No direct replacement announced — plan for another test approach.
Microsoft deprecation notice ↗