Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Note
Community interest groups have now moved from Yammer to Microsoft Viva Engage. To join a Viva Engage community and take part in the latest discussions, fill out the Request access to Finance and Operations Viva Engage Community form and choose the community you want to join.
This article lists the features in the platform updates for version 10.0.46 of finance and operations apps. This version uses build number 7.0.7778.8 and is available on the following schedule:
- Preview of release: October 2025
- General availability of release (self-update): November 2025
- General availability of release (auto-update): December 2025
Features included in this release
This section lists the features included in this release when available. We might update this article to add features that are added to the build after it's published.
| Module or feature area | Feature name | More information | Enabled by |
|---|---|---|---|
| System administration | Batch history logging options | A configurable option to skip persisting the INFO and PARAMETERS columns when writing to the batch history table, which provides database storage optimization and improved write performance. Learn more in Batch history logging options. | Feature flight |
Feature enhancements included in this release
This section has a table that lists enhancements included in this release when available. We update this article to include features added to the build after it's published.
| Module or feature area | Feature name | More information | Enabled by |
|---|---|---|---|
| Platform | Change to query timeout settings | The default timeout settings have been updated so that axOnline interactive workloads that previously had a 30‑minute timeout now use a five‑minute timeout. This platform‑level configuration change is designed to improve system responsiveness and overall stability. Applying it globally ensures consistency and helps prevent performance degradation. The phased production rollout is scheduled to begin on January 20, 2026. This change is documented under the Dynamics 365 Finance and Operations 10.0.46 platform updates to maintain transparency and provide clear guidance to customers. The rollout is global and not tied to any specific PU version. |
On by default |
| System administration | Dynamics 365 ERP Model Context Protocol server | In this release the capabilities of the Dynamics 365 ERP MCP server are enhanced by increasing the number of functions the server can perform, and enabling the server to work with extensions and personalization in the environment. For more information, see Use Model Context Protocol for finance and operations apps | System administrator |
| System Administration | DMF Telemetry integrates with Application Insights | We’re enhancing the Monitoring and Telemetry feature by introducing DMF telemetry integration with Application Insights. This capability is currently behind feature flights and the underlying telemetry is available for preview in early April 2026. For more details, see DMF telemetry | Feature Management |
Bug fixes
To see bug fixes in this update, sign in to Microsoft Dynamics Lifecycle Services and view the KB article.
Dynamics 365: 2025 release wave 2 plan
Want to know about upcoming and recently released capabilities in our business apps or platform?
See the Dynamics 365: 2025 release wave 2 plan. This document has all the details you need for planning.
Removed and deprecated platform features
The Removed or deprecated platform features article describes features that are removed or planned for removal in platform updates for finance and operations apps.
- A removed feature isn't available in the product.
- A deprecated feature isn't in active development and might be removed in a future update.
Deprecation notices appear in the Removed or deprecated platform features article 12 months before any feature is removed.
For breaking changes that affect only compilation time, but are binary-compatible with sandbox and production environments, the deprecation time is less than 12 months. These changes are functional updates that must be made to the compiler.