These are anonymized, composite scenarios built around recurring patterns we’ve seen across Microsoft Dynamics 365 environments. They illustrate common situations, not a specific customer’s confidential details.
Every Microsoft Dynamics 365 F&SCM environment is different, but the same handful of performance patterns keep showing up across industries and company sizes. Here are six scenarios IT teams tell us about most often, and what changes once SQL, AOS and Batch stop being monitored in isolation.
1. The visibility you lost when you moved to the cloud
“You were on-premise. You knew everything. Now you’re flying blind.”
What happened
A manufacturing company migrates Microsoft Dynamics 365 Finance & Operations from on-premise to the cloud. On-premise, the IT team had direct access to SQL Server: blocked queries, user mapping, AOS memory, index rebuilds. After the move, that access simply isn’t part of what a standard cloud environment exposes, and Microsoft can’t provide the same level of detail on request.
What changed
Once SQL, AOS and Batch metrics were collected into one correlated view on top of the existing Azure environment, the team got back the exact categories of visibility they’d lost, without asking Microsoft to change how the managed service works.
2. The memory crisis nobody saw building
“Your AOS crashed. You found out when Microsoft called.”
What happened
AOS memory climbs gradually across weeks, driven by a mix of batch jobs and user sessions. No single day looks alarming, until usage crosses a threshold Microsoft has to intervene on. The IT team’s first real signal is a call telling them memory allocation had to be increased on their behalf.
What changed
With AOS memory tracked continuously and correlated against batch activity, the same climb becomes visible weeks earlier, so the decision to adjust scheduling or scale resources happens deliberately, not reactively.
3. The slow screen nobody could explain
“You know it’s slow. You just can’t prove where, or why.”
What happened
A specific grid view used daily by a business team gets noticeably slower. The team records a screen capture and sends it to Microsoft support, but without a way to trace the click back to the specific SQL query it triggers, the ticket sits without a clear next step.
What changed
With SQL activity correlated against the timing of the complaint, the exact query behind the slow screen becomes identifiable directly, no manual trace session required.
4. Growing faster than your monitoring can keep up
“Every new acquisition is another environment nobody is watching closely enough.”
What happened
A distribution company grows through acquisitions, onboarding each new business unit onto its existing Microsoft Dynamics 365 environment. Monitoring, where it exists, was scoped for the environment at go-live, not for what it looks like after the fourth or fifth acquisition.
What changed
A continuously updated baseline adjusts to what the environment actually looks like today, so growth in data volume or user count shows up as a trend instead of waiting for a new acquisition to cause a visible problem.
5. One tenant, several go-lives, one view
“One tool. Every environment. One price.”
What happened
A global organization runs several Microsoft Dynamics 365 F&O projects on a single tenant, at different go-live stages. Native tools are scoped per environment, so visibility has to be assembled project by project, with no single view across the whole tenant.
What changed
A monitoring layer licensed per tenant covers every current and future project under one view, so adding a new go-live extends the existing setup instead of requiring a new one.
6. When sixty minutes of history isn't enough
See what Microsoft sees. Before they have to fix it for you.”
What happened
A team investigating a performance issue turns to LCS, only to find the detailed view limited to a narrow rolling window. Anything before that, including the moment the problem started, is already gone, so someone manually exports data to a spreadsheet on a recurring basis just to keep a longer record.
What changed
With SQL, AOS and Batch metrics captured continuously, the same investigation becomes possible after the fact, with a real historical baseline to compare against, and no more manual exports.
