EUR 1.3 million
Approximate spending mitigated through Azure Reserved Instances
Case study

SoftwareOne helped a global manufacturer turn fast-rising Azure spend into a governed, transparent and increasingly value-focused FinOps practice.
A global manufacturer was expanding its use of cloud to support products spanning mechanical engineering, electronics and software. Yet its cloud financial management practices had not kept pace. Departments managed resources independently, cost allocation was limited and Azure spending rose beyond a major Microsoft Enterprise Agreement commitment. SoftwareOne helped the organization establish visibility, ownership and governance across cloud spending. The work combined live reporting, cost allocation, education, tagging standards and commitment-based optimization. It gave executives, finance teams and resource owners a clearer view of consumption and enabled approximately EUR 1.3 million (USD 1.45 million) in reservation savings, with a further EUR 2.5 million forecast through Azure Savings Plans.
Approximate spending mitigated through Azure Reserved Instances
Forecast savings from negotiated three-year Azure Savings Plans
Cost visibility expanded across the organization’s two public cloud environments
The global manufacturer relied heavily on public cloud to support a growing portfolio of mechanical, electronic and software-enabled products. However, its approach to cloud financial management was still at an early stage. Departments managed Azure resources in different ways, engineers could provision services with limited central governance, and cost ownership was difficult to establish.
The organization had also entered a Microsoft Enterprise Agreement with a EUR 250 million commitment. It received a 20% discount against pay-as-you-go rates and an additional 6% discount against three-year Reserved Instance pricing. Encouraged to increase consumption so the commitment would be used, departments accelerated adoption. Within three months, the Azure spending trajectory had exceeded the commitment by 15%.
A two-person internal team was asked to establish FinOps alongside its existing responsibilities. To regain control quickly, the organization selected SoftwareOne for a clear strategy, relevant expertise and a practical sequence of milestones.
SoftwareOne began by helping the organization create a live showback model for Azure costs. Because the customer required the reporting solution to be developed in-house for data privacy, the team used the Azure billing API to ingest current spending data and built a tailored dashboard in Power BI. Costs were initially allocated through Azure subscriptions, giving executives and finance teams a clearer view of departmental spending while helping resource and product owners understand which services were driving costs.
The reporting model later expanded through Databricks to include AWS data. Subscription naming conventions were standardized, and a policy-backed tagging approach helped ensure that cloud resources carried the labels needed for reliable allocation and reporting.
Technology alone would not change spending behavior. SoftwareOne therefore supported interactive FinOps sessions across the organization, explaining shared accountability and the need for engineering, finance, procurement and leadership to collaborate. The team demonstrated the reporting dashboard, gathered feedback and helped create cloud fundamentals training for new joiners. FinOps principles were embedded into that training so employees could understand both how cloud enables the business and how consumption translates into cost.
The main takeaway is to remain persistent when things get tough, understand the interests of cloud providers, executives, engineers and finance teams, and support recommendations with evidence.
FinOps consultant, SoftwareOne
The first major optimization opportunity centered on Azure Reserved Instances. Some resource owners already used reservations, but the approach was not widespread. When Microsoft announced an 11% Euro pricing adjustment from 1 April 2023, the organization had three months to identify stable workloads that could be committed before the change.
SoftwareOne worked with environment and resource owners to assess candidate workloads, confirm their roadmaps and check that each was appropriately sized before any commitment was made. The resulting list focused only on resources considered safe and viable for one- to three-year reservations. The request was placed in the Azure portal on 31 March 2023. The activity mitigated approximately EUR 1.3 million in spending, a figure that continued to grow during the engagement.
In early 2024, the focus moved to Azure Savings Plans for Compute. The flexibility was attractive, but analysis showed that the organization's existing 20% Enterprise Agreement discount on pay-as-you-go rates did not apply to Savings Plans. Committing to the proposed rates could therefore increase costs rather than reduce them. The FinOps team documented the risk and provided evidence to senior leaders, procurement, and Microsoft.
Bring cloud spending, technology decisions and business outcomes together with a practical FinOps operating model.
Let's talkThe analysis changed the Savings Plans discussion from a straightforward purchasing decision into an evidence-led commercial negotiation. The organization wanted the flexibility of Savings Plans because it expected to keep investing in Azure, but it also needed the economics to improve on its existing pay-as-you-go position.
SoftwareOne and the internal FinOps team demonstrated where the proposed rates created risk. With procurement involved, the organization negotiated additional discounts of 8% for one-year Azure Savings Plans and 13% for three-year plans. Once the revised terms were agreed, the FinOps team modeled several commitment-rate options and showed the potential discount against pay-as-you-go rates using a shared-scope approach.
The customer ultimately adopted multiple three-year Savings Plans with a combined commitment of EUR 110 per hour. Forecast savings were close to EUR 2.5 million. Combined with the approximately EUR 1.3 million mitigated through Reserved Instances, the engagement established a clear financial case for FinOps while preserving flexibility for workloads whose resource types may change over time.
The organization gained visibility into where spending was heading, a stronger sense of accountability and a way to release more value from cloud investment for new strategies.
FinOps consultant, SoftwareOne
The impact extended beyond the savings figures. Executives and finance teams could track where costs originated, while engineering and product teams gained clearer ownership of the resources driving them. Standardized reporting, naming and tagging created a stronger basis for showback, cross-cloud analysis and future optimization.
The cultural shift was equally important. The program began with resistance from some engineers and product owners, particularly as the organization moved away from the previous emphasis on accelerating consumption. Through persistent engagement, interactive education, and evidence-based recommendations, FinOps became a recognized part of cloud decision-making. Departments became more willing to explore optimization opportunities and increasingly relied on the FinOps team to support informed choices.
For the manufacturer, FinOps was no longer a response to spiraling spending. It had become a repeatable way to connect cloud consumption with accountability, commercial decisions and business value.
All departments now understand the importance of FinOps, are more open to optimization opportunities and rely on FinOps to help them make informed, beneficial decisions.
FinOps consultant, SoftwareOne

SoftwareOne can help build the visibility, governance and collaborative FinOps practices needed to turn cloud investment into measurable business value.
SoftwareOne can help build the visibility, governance and collaborative FinOps practices needed to turn cloud investment into measurable business value.