If your Dynamics 365 or model-driven Power Apps suddenly lost their corporate colours this year, here is why, and how to fix it properly.
What changed
Microsoft stated that the modern, refreshed look became mandatory for model-driven apps in April 2026, and that classic theming is not honoured with the modern look. Apps that relied on classic themes for branding therefore appear in the default modern style.
The fix is custom theming for model-driven apps, which Microsoft has made generally available. It lets organisations match their branding by customising colours, fonts and header styling, using the Fluent 2 design system.
Related updates in the same release
- App-based conversations in Microsoft 365 Copilot (public preview): key parts of model-driven apps can surface inside Microsoft 365 Copilot, powered by the app's MCP server.
- Generative pages via external tools (generally available): pages can be built with AI coding tools such as GitHub Copilot CLI, now in all public clouds, with localisation for language and regional formats.
- Code app alerts in Power Platform Monitor: rolling out with no setup required.
Why branding matters
Consistent branding isn't vanity. It helps users trust internal tools, reduces confusion between environments, and supports accessibility when colours meet contrast standards.
Recommended steps
- Recreate your theme with custom theming rather than workarounds.
- Check contrast against accessibility guidelines (WCAG AA), because Fluent 2 makes this easier.
- Use different header colours for test and production so users always know where they are.
- Package the theme in a solution so it moves through your ALM pipeline with the app.
Need help modernising Dynamics 365 or model-driven apps? Our Dynamics 365 CRM and Power Platform teams can help.
Source: Microsoft Power Platform Blog — Power Platform monthly feature update (April 2026)



