Microsoft retires older Teams app controls in favour of modern ones
Reviewed by Helen Jones
Microsoft has deprecated Fluent UI (v8) controls, also called hero controls, for canvas apps that run inside Microsoft Teams and for custom pages inside model-driven apps. Modern controls built on the Fluent 2 design system replace them. Official Learn guidance, updated in July 2026 and called out in the July/August Power Platform feature update, explains how the upgrade works, which properties carry over, and where behaviour differs. Some hero settings, including certain colour and theming options, do not map one-to-one. Classic controls remain supported in broader canvas scenarios for organisations that keep their own design systems. The active investment path for Teams-embedded and custom-page UIs is modern controls.
Until now, many internal apps embedded in Teams or dropped into model-driven custom pages still used the older Fluent hero control set because that was what Studio offered and what tutorials showed. Those screens could look fine while the rest of Microsoft 365 quietly moved to Fluent 2. What changed is not a sudden break of every canvas app, but a clear signal about where polish, accessibility, and performance work will land next. If your app sits in Teams or on a custom page and still uses hero controls, leaving it alone means you keep an older look and miss the fixes Microsoft is shipping only on the modern set. The upgrade is documented, but theming and a few properties will need a human pass after conversion.
Analysis
Treat this as a targeted check, not a rebuild of every SharePoint canvas app you own. Open any app that runs in Teams or as a model-driven custom page, see whether it still uses Fluent UI v8/hero controls, run Microsoft’s upgrade path once, then click through forms, buttons, and theme colours on phone and desktop before you call it done.
Source note
Pulse published by Collab365 Spaces, reviewed by Helen Jones on . Cite as "Microsoft retires older Teams app controls in favour of modern ones", Collab365 Spaces. 2 sources referenced.