Case Study: Finding the Logging Pattern Behind Rising Azure Cost

Problem

An enterprise Azure environment had rising monthly cost across a mix of application and platform services. The first view of the bill showed spend spread across API management, app hosting, functions, messaging, private endpoints, firewall, and Log Analytics.

That made the problem look broad. In practice, the cost was being amplified by how telemetry was collected, retained, and routed.

Context

A large government agency was delivering a complex Azure-based integration solution under tight timelines.

The environment supported real workloads, so the answer could not be a blunt reduction in monitoring. Logging was needed for support, operations, and security visibility.

The issue was that the volume and retention pattern did not match the actual value of the data being kept. Without resource-level and service-level analysis, the organisation could keep optimising around the edges while missing the main driver.

That decision made sense during active investigation. The problem was that the logging was not reviewed or reduced after the issue was resolved.

This is a common cloud delivery issue. During project pressure, teams enable additional diagnostics to solve immediate problems. That is often necessary. But without a clear process to review and reset logging afterwards, temporary troubleshooting settings can become permanent cost waste.

What was accomplished

Our team reviewed the cost composition, checked the services contributing to the increase, and narrowed the pattern to telemetry volume and retention behaviour.

Key decisions and trade-offs

The trade-off was visibility versus cost. Removing logs would have reduced spend quickly, but it could have created operational risk. Keeping every log at the same level and retention period was also not sensible.

The better approach was to tune what was collected, where it was sent, and how long it was kept.

Result

The analysis showed that approximately 80% of the cost issue was linked to logging and telemetry design. That gave the organisation a clear remediation path and a five-figure annual saving opportunity.

More importantly, it changed the discussion from general cloud cost pressure to a specific engineering decision: keep useful logs, remove low-value noise, and set retention based on real need.

The biggest value was not just the saving. It was proving that the cost was not an unavoidable business expense. It was a configuration and governance issue that could be corrected.

Conclusion

Logging is useful. Unchecked logging can quietly become one of the most expensive parts of a workload.

When a solution is complex, it is easy for high costs to be accepted as normal. This is especially true when third-party teams, delivery partners, or contractors are involved and the internal team does not have full visibility into every configuration decision.

A practical Azure cost optimisation review should look beyond the headline service cost and check the telemetry pattern behind it.