“It’s Slow” is not a diagnosis: How to actually fix Dynamics 365 F&SCM performance issues
This article is sponsored by XPLUS.
In many Dynamics 365 F&SCM projects, performance incidents begin with a familiar statement: “The system is slow.”
The challenge is not visibility. Users clearly feel the impact of slow screens, postings that run past business hours, growing batch queues, and system freezes. The real problem is diagnosis. “It’s slow” describes a symptom - not the cause.
Why performance in D365 is so difficult to explain?
Dynamics 365 F&SCM operates across multiple layers: the SQL database, AOS application servers, and the Batch framework. Performance issues rarely originate in only one of them. Instead, they emerge from interactions between queries, application logic, workload peaks, and configuration changes.
Microsoft tools such as Lifecyle Services (LCS) and Application Insights provide valuable telemetry and infrastructure insights. However, they were not designed for deep performance engineering. They show resource consumption and high-level trends, but they do not always correlate SQL behavior, application load, and batch execution into one consistent, analyzable view.
As a result, teams often see indicators without understanding causality. CPU increases, but the triggering query remains unclear. A batch job slows down, but no one can confirm whether a recent deployment introduced regression. A fix is applied, yet there is no measurable proof that performance has improved.
This is where reactive firefighting replaces structured optimization.
What do performance problems look like in practice?
Consider a few common scenarios. After a One Version update, users report that a previously stable process now runs slower. Without historical baselines and before/after metrics, it is nearly impossible to prove whether execution plans changed, query duration increased, or workload patterns shifted. Optimization becomes assumption-driven rather than evidence-based.
In another case, intermittent system freezes occur during business peaks. The root cause may lie in long-running transactions or blocking chains at the SQL level. But unless lock duration and query behavior are monitored continuously, the blocking session often disappears before analysis even begins.
Batch performance issues present similar complexity. Growing queues may indicate resource contention, inefficient SQL triggered by batch logic, or overlapping workloads introduced through configuration changes. Without correlated visibility into job duration, retry rates, AOS utilization, and database behavior, teams are left troubleshooting in isolation.
Even slow screens during high transaction periods are rarely caused by a single factor. Frequently executed queries, subtle plan regressions, or I/O spikes aligned with business peaks can collectively degrade user experience. Performance must be analyzed in context - not as isolated technical metrics.
Moving toward a measurable optimization cycle
Effective performance management requires a structured approach. Instead of reacting to complaints, organizations need a repeatable optimization cycle: detect anomalies, analyze technical impact, identify root cause across layers, apply corrective changes, and verify improvements using measurable KPIs.
Verification is critical. Without comparing results to historical baselines, even well-designed fixes remain assumptions. Performance engineering becomes credible only when every change can be validated with data.
This shift from reacting to symptoms to controlling system behavior over time, transforms performance from an operational burden into a managed discipline.
Why correlation changes the outcome?
Isolated metrics rarely provide clarity. Real insight into D365 F&SCM system performance emerges when SQL activity, AOS resource usage, and Batch behavior are viewed together and analyzed over time. When teams can correlate technical metrics with actual business workload, they gain the ability to explain not just what happened, but why it happened.
Interactive dashboards, historical trends, and drill-down capabilities into detailed performance data make root-cause analysis faster and more objective. Instead of debating opinions, teams can rely on evidence.
This is the difference between monitoring and performance engineering.
At XPLUS, we work directly with performance testing, optimization, and production monitoring in Dynamics 365 F&SCM environments. Based on this experience, we developed Performance Monitoring, a solution that collects metrics from SQL, AOS, and Batch, stores them securely in Azure Log Analytics within the customer’s tenant, and visualizes correlated insights in interactive dashboards. The goal is simple: enable measurable optimization and eliminate guesswork.
Because in the end, “it’s slow” should never be the only thing you know.
…
Photo by Pixabay
FREE Membership Required to View Full Content:
Joining MSDynamicsWorld.com gives you free, unlimited access to news, analysis, white papers, case studies, product brochures, and more. You can also receive periodic email newsletters with the latest relevant articles and content updates.
Learn more about us here