Dynamics 365 & Power Platform: What Developers Should Watch in 2025 Release Wave 2

Avatar photoByAdil

I’ve been digging through the 2025 Release Wave 2 plans and some preview articles, and I wanted to share what I found from a developer and maker perspective.

While most announcements highlight Copilot and AI, there are several changes that will directly affect developers — especially around solution management, extensibility, and integration patterns.

Here’s a summary of the Wave 2 features that stood out to me, and why they matter in real projects.

Why This Matters

  • Dynamics development is shifting as Copilot and agents become part of solution design.
  • ALM pipelines may need adjustments for new solution components.
  • Some older approaches, like DOM-based customizations, are at risk with UI updates.

This release is as relevant for developers as it is for business users.

Key Features to Note

1. Model Context Protocol (MCP) in Sales Copilot

Wave 2 brings MCP integration (the same protocol used by GitHub Copilot agents) into Dynamics Sales.

Impact: Developers can extend Copilot flows by packaging MCP “skills” as extensions. Security testing and permission handling will be essential.

2. Copilot Studio and Multi-Agent Support

Makers can now build multiple Copilot agents that integrate with Dataverse, Microsoft Graph, and Azure AI.

Impact: These agents will appear as new solution components, meaning ALM pipelines must handle export, import, and versioning.

3. Asynchronous Dual-Write

Dual-write now supports asynchronous processing between FinOps and Dataverse.

Impact: Integrations need to account for eventual consistency. Developers should test error handling, retries, and data reconciliation.

4. Natural Language ERP Queries

End users can query ERP data using natural language directly from Dynamics.

Impact: Developers must ensure that security roles are properly enforced, so sensitive data isn’t exposed through free-text queries.

5. UX and Navigation Refresh

Wave 2 introduces a more streamlined header and command bar redesign. Some buttons will move into overflow menus.

Impact: Ribbon customizations and JavaScript that rely on unsupported DOM selectors may break. It’s best to validate all custom buttons and switch to supported APIs.

6. Copilot Form Fill Assist and Smart Paste

Copilot can map data from files, images, or clipboard content into Dataverse fields.

Impact: Developers may need to customize mapping rules, add validation, or create plugins to enrich the data before saving.

Areas to Watch

  • How well solution upgrades handle Copilot agent components in ALM.
  • The reliability of asynchronous dual-write in production environments.
  • The effect of UI changes on ribbon customizations.
  • Licensing considerations for advanced Copilot features.

How to Prepare

  • Test pipelines with new solution components like agents.
  • Build and deploy a sample agent in Copilot Studio, then try exporting and importing via DevOps.
  • Simulate asynchronous integration delays between FinOps and Dataverse.
  • Review JavaScript customizations and remove unsupported DOM dependencies.
  • Work closely with makers — they’ll build more with Copilot Studio, and developers will need to provide governance.

Final Thoughts

Wave 2 is moving developers toward new responsibilities:

  • Less focus on form customizations.
  • More focus on governance, extensibility, and resilient integrations.

This is what I found while researching Wave 2.

Similar Posts