Microsoft regularly updates Microsoft Dynamics 365 and Power Platform to strengthen security, improve performance, and modernise the user experience. As a result, Microsoft has deprecated or removed several Dynamics 365 and Microsoft Power Platform capabilities across 2023 and into early 2024. This article summarises what’s changing, who it affects, and which power platform tools CTOs should review first to reduce risk and avoid disruption.
Model-driven app controls: deprecation begins April 2023
In Microsoft Power Platform, Microsoft is replacing legacy controls with Fluent UI controls to improve usability, accessibility, and dark mode support.
- Impact: From April 2023, you can’t add deprecated controls to new forms; existing controls may continue working until April 2024.
- Action required: Audit current forms across affected power platform apps and plan replacements for any deprecated controls before support ends.
The following model-driven app controls were deprecated in January 2023:
- Auto-complete
- Input mask
- Multimedia player
- Number input
- Option set
- Star rating
These controls are being replaced by Fluent UI alternatives designed for improved accessibility, usability, and dark mode compatibility. Examples of replacement controls include Toggle, Calendar Control V2, and the Power Apps grid control (preview), depending on your scenario. Deprecated controls may continue to function in existing forms and views for a limited time, but they won’t be available for new implementations.
For full details, Read more.
Customer Service workspace legacy layout: deprecated April 2023, unsupported after October 2023
- Impact: The legacy layout is unsupported after October 2023, increasing operational risk for service teams that remain on it.
- Action required: In Microsoft Power Platform Customer Service, migrate to the Enhanced Multisession Layout and validate agent workflows before cut-off.
The Customer Service workspace legacy layout was deprecated in April 2023 and is unsupported after October 2023. The Enhanced Multisession Layout changes how sessions, navigation, and in-session tabs work, including:
- In the new layout, agents manage multiple sessions via tabs across the top, rather than switching sessions via a drop-down.
- Within each session, the new layout uses tabs for case details, timeline, knowledge, and related records, replacing the old single-tab navigation pane approach.
- The new layout moves the navigation bar to the left (app name, app switcher, sitemap), whereas the legacy experience used a top navigation bar.
For full differences and configuration guidance, Read more. To reduce surprises at go-live, confirm any supporting power platform tools still behave as expected in the new session model.
Omnichannel agent-facing app: deprecated April 2023
- Impact: Support continues until June 2024; organisations should plan migration in Microsoft Power Platform to Customer Service workspace to avoid service disruption.
This app supported agents handling omnichannel conversations (chat, SMS, email, and social channels) in a single interface, often alongside bespoke power platform apps. It is being replaced by Customer Service workspace, which offers a comparable agent experience plus enhanced multisession, dark mode, and voice channel capabilities.
For timelines, prerequisites, and migration steps, More information.
Intraday Insights reports: phased retirement (May 2023–April 2024)
- Impact: Support ended on October 31, 2023 (no new features); reports are unavailable after April 30, 2024, including for existing organisations.
- Action required: Migrate reporting in Microsoft Power Platform to Real-Time Analytics (or an agreed alternative) and confirm metric parity for service leadership.
These reports delivered near real-time visibility into agent performance, queue health, and customer experience signals. They are replaced by Real-Time Analytics, which provides broader omnichannel insights with more flexible configuration and reporting options. As you migrate, validate the figures in the power platform tools your service leaders use day to day, so you don’t lose trust in core metrics.
For replacement reporting options and migration guidance, More information.
jQuery 2.1.1 removal: October 2023
Microsoft removed the bundled jQuery 2.1.1 library from Microsoft Power Platform model-driven apps to reduce security risk associated with outdated dependencies.
- Impact: Customisations that depend on jQuery 2.1.1 may fail, affecting forms, web resources, or UI scripts that assumed the older library was present.
- Action required: Audit client-side scripts and refactor dependencies to supported approaches (modern JavaScript or an approved library strategy), then regression test affected power platform apps in a sandbox.
For technical details and supported alternatives, Read more.
Exchange-based cards: deprecated October 2023
- Impact: Existing Exchange-based cards become unavailable; where needed, replace them with custom cards or alternative automations using Power Automate. Treat this as a small but important clean-up across your power platform tools, especially if sellers rely on assistant-driven prompts.
For current configuration options and limitations, Learn more.
Rank Optimization of Insight Cards: deprecated October 2023
Rank Optimization of Insight Cards previously allowed organisations to influence the order of Sales Insights cards shown in the assistant. Insight cards are personalised recommendations to help sellers take next-best actions, such as following up with leads, progressing opportunities, or engaging customers.
Rank Optimization was deprecated on October 1, 2023 and is no longer available. The assistant now uses Microsoft’s default ranking logic, which considers factors such as card type, recency, urgency, and user interactions to prioritise relevance. You can still manage insight cards by enabling/disabling them, configuring role-based availability, and adjusting related Power Automate flows where applicable.
- Impact: Any custom ranking rules previously configured will no longer be applied to insight cards.
- Action required: Disable low-value cards and refine card settings so the remaining insights align to seller workflows and priorities—and so the surrounding power platform tools reinforce those priorities rather than distract from them.
For updated guidance, Read more.
Dynamics 365 for Phones and Tablets: deprecated, with migration required by 2024
- Impact: Users should transition to the Power Apps mobile app (or the relevant modern mobile experience) to maintain supported mobile access.
- Action required: Plan the migration, validate mobile scenarios by role (including key power platform apps), and communicate the change to users with training and support.
This app enabled mobile access to several finance and operations scenarios, including expenses, inventory lookups, asset tasks, invoice approvals, and purchase order approvals. It was deprecated on October 1, 2023 and scheduled for removal from app stores by April 1, 2024. It is replaced by modern mobile experiences aligned to specific workloads, so organisations should validate which replacement experience applies to each role and workspace.
For replacement options and end-of-support details, Learn more.
Dynamics 365 connector: deprecation status and migration path
- Impact: If you still rely on the legacy Dynamics 365 connector, you should plan migration now to reduce integration risk when final shutdown timelines are enforced—especially where Microsoft Power Platform automations sit on critical paths.
- Action required: Migrate integrations to supported connectors (typically the Microsoft Dataverse connector) and revalidate flows, Logic Apps, and other power platform tools end to end.
Effective May 5, 2020, the legacy Dynamics 365 connector used in Power Platform integrations (including flows, Logic Apps, and canvas apps) was deprecated. Microsoft recommends avoiding new connections using the deprecated connector and prioritising supported alternatives. From April 29, 2022, the connector could no longer be used for certain scenarios, so organisations should treat remaining dependencies as high risk. Replace it with the appropriate supported connector for your environment—most commonly the Microsoft Dataverse connector—then test authentication, permissions, and data operations end to end.
Conclusion
Staying current on deprecations is essential for organisations running Dynamics 365 and Power Platform, because unsupported features create operational and security risk. Proactive remediation protects continuity, reduces vulnerability exposure, and keeps your platform eligible for modern capabilities. Audit your tenant for impacted features, prioritise changes by business risk, and execute migrations in controlled waves with regression testing—especially where shared power platform tools and cross-team dependencies hide risk. Microsoft’s modernisation roadmap can improve platform robustness—provided organisations retire deprecated components before end-of-support dates, particularly across Microsoft Power Platform. Establish an internal release-note cadence so these changes are tracked continuously, not discovered at the last minute, and ensure your most business-critical power platform apps are always tested first.
